Drupal logo
Preview of the Vultr management interface for Drupal on a mobile device.
Drupal logo|trans
Preview of the Vultr server deploy page control panel for Drupal on a web browser.

Why Use Drupal?

The official release of Drupal, also known as Drupal core, is a powerful content management system that was started in the early 2000s. It can be used for content management, blogging, forums, and even entire websites. Start adding your own content in moments by launching your Drupal app on Vultr.

Open Source, Community Driven

Drupal is fully open-source and has a strong developer community. Developers are constantly releasing new modules, themes, and other add-ons.

The core functionality can be extended by installing modules, which over 30,000 are available. Many of these are community built. Don't like the standard "look" for Drupal websites? Install one of the thousands of custom themes built for it. The possibilities are endless.

Drupal Details

To view the publicly accessible instance, visit https://use.your.ip/. See our instructions to bypass the HTTPS warning for self-signed SSL/TLS certificates if a Commercial or Let's Encrypt SSL/TLS certificate is not going to be installed (instructions for both options are below).

Configuration and Administration

Once the instance has finished booting and installing the required software, navigate to https://use.your.ip/install.php to complete the Drupal installation process. The installer will prompt for login credentials and database settings, which are as follows:
* User: userInstall User
* Password: Install Password
* Database Name: drDatabase Name
* Database User: drupalDatabase User
* Database Password: Database Password

Security Considerations

It is strongly recommended to update the trusted_host_patterns in /var/www/html/sites/default/default.settings.php after installation. See Trusted Host Settings in Drupal's documentation.

Cockpit Control Panel

Cockpit control panel is accessible via https://use.your.ip:9080/:
* Credentials are the same as provided on the Server Information page
If you use the Vultr Firewall, make sure to allow access to port 9080.

Cockpit can be disabled by connecting as the root user and running:
# systemctl disable --now cockpit.socket


PHPMyAdmin is accessible via https://use.your.ip/mysqladmin/:
* Username for both security modal and logging in: pmauserPHPMyAdmin Username
* Password for security modal: PHPMyAdmin htaccess modal Password
* Password for logging in to PHPMyAdmin: PHPMyAdmin Password

HTTPS: SSL/TLS Certificates

To access the server with a domain name, instead of use.your.ip, it is possible to register a domain name from a domain registrar, and either follow the registrar's documentation on updating DNS records, or utilize Vultr's DNS.

Once DNS has finished propagating, and the registered domain name resolves to use.your.ip, connect to the server via console or SSH as the root user.

Let's Encrypt via Certbot

Certbot is installed by default on Vultr's Drupal Marketplace app. If you need to update or reinstall, please see the recommended installation steps at eff.org.

Requesting a Certificate

The below example shows installing multi-domain certificate for the bare or root domain of example.com as well as the fully-qualified domain name (FQDN) of www.example.com. The email provided is used for registering an account with Let's Encrypt and is not sent to Vultr:
# certbot --nginx --redirect -d www.example.com -d example.com -m admin@example.com --agree-tos --no-eff-email
Upon successfully requesting certificates, a message should be shown that includes text similar to the following:

Successfully deployed certificate for www.example.com to /etc/nginx/conf.d/drupal_https.conf
Congratulations! You have successfully enabled HTTPS on https://www.example.com

(Optional) To update the Cockpit Control Panel to use the same certificate, a script is available to be invoked via:
# /opt/vultr/cockpit-certificate.sh

Revoking a Certificate

In case a certificate issued by Let's Encrypt via certbot is to be revoked, or otherwise needs to be uninstalled, these steps should be followed:
1. Back up current web server configuration files:
# cp -r /etc/nginx /root/nginx
2. Revoke the certificate:
# certbot delete
3. Restore default web server configuration:
# /opt/vultr/fix-vhost.sh

Commercial SSL/TLS Certificate

If a commercial certificate is desired instead of the free Let's Encrypt certificate, install the public certificate as /etc/nginx/ssl/server.crt and the private key as /etc/nginx/ssl/server.key. Refer to the certificate vendor's documentation for any further details. Once these files are in place, reboot the server to ensure all services are using the correct certificate: # reboot

Disabling HTTPS

While strongly discouraged, it is possible to disable HTTPS access by running the following:
# mv /etc/nginx/conf.d/drupal_https.conf /root/; reboot

SQL Database Access

To access the MariaDB (MySQL) database server, connect as the root user via console or SSH and run:
# mysql -u root

The root password is located in the configuration file /root/.my.cnf.

Logs for the database server can be viewed with:
# journalctl -eu mariadb.service

Helper Scripts

After connecting as the root user via console or SSH as the root user, the following scripts can be invoked to assist in configuration tasks.

Reset NGINX Server Configuration

To reset the NGINX web server configuration to its original settings, use:
# /opt/vultr/fix-vhost.sh

Check Software Versions

Our support team may request OS and Drupal version information, which can be obtained via:
# /opt/vultr/version.sh

Files and Folders of Interest

  • php.ini : /etc/php/8.2/fpm/php.ini
  • NGINX virtual host configuration : /etc/nginx/conf.d/
  • NGINX virtual host SSL files (unless Certbot has been utilized to generate Let's Encrypt certificates) : /etc/nginx/ssl/

Support Information

Support Contact

Support URL

Maintainer Contact

Report Application

Report an application with malicious intent or harmful content.

Thank you for your report!

Our Team has received your report and will respond accordingly as possible.