Deploy your Bitnami Multicraft Stack on Google Cloud Platform now! Launch Now

Bitnami Multicraft for Google Cloud Platform

NOTE: This application can only be deployed through the Bitnami Launchpad for Google and it is not available in the GCP Marketplace for the moment.


Multicraft is a complete Minecraft server hosting solution and control panel. It supports unlimited servers on a single panel, integrates with the most popular billing systems and has a powerful API.

License information

The Bitnami Multicraft stack comes with a Free license for use on one server. The Free version provides a full set of features for up to 10 players on a single machine. To learn more about Multicraft plans and licensing visit the Multicraft website.

First steps with the Bitnami Multicraft Stack

Welcome to your new Bitnami application running on Google Cloud Platform! Here are a few questions (and answers!) you might need when first starting with your application.

What credentials do I need?

You need two sets of credentials:

  • The application credentials that allow you to log in to your new Bitnami application. These credentials consist of a username and password.
  • The server credentials that allow you to log in to your Google Cloud Platform server using an SSH client and execute commands on the server using the command line. These credentials consist of an SSH username and key.

What is the administrator username set for me to log in to the application for the first time?

Username: user

What SSH username should I use for secure shell access to my application?

SSH username: bitnami

What are the default ports?

A port is an endpoint of communication in an operating system that identifies a specific process or a type of service. Bitnami stacks include several services or servers that require a port.

IMPORTANT: Making this application's network ports public is a significant security risk. You are strongly advised to only allow access to those ports from trusted networks. If, for development purposes, you need to access from outside of a trusted network, please do not allow access to those ports via a public IP address. Instead, use a secure channel such as a VPN or an SSH tunnel. Follow these instructions to remotely connect safely and reliably.

Port 22 is the default port for SSH connections.

Bitnami opens some ports for the main servers. These are the ports opened by default: 80, 443, 25565.

How to start or stop the services?

Each Bitnami stack includes a control script that lets you easily stop, start and restart services. The script is located at /opt/bitnami/ Call it without any service name arguments to start all services:

$ sudo /opt/bitnami/ start

Or use it to restart a single service, such as Apache only, by passing the service name as argument:

$ sudo /opt/bitnami/ restart apache

Use this script to stop all services:

$ sudo /opt/bitnami/ stop

Restart the services by running the script without any arguments:

$ sudo /opt/bitnami/ restart

Obtain a list of available services and operations by running the script without any arguments:

$ sudo /opt/bitnami/

How to change the default administrator password?

For security, it is recommended that you change the default administrator password as soon as possible. Follow the steps below:

  • Log in to the application as an administrator.

  • Select the "Users -> My Profile" menu item.

  • Enter the old password, then the new password twice.

  • Click "Save" to save your changes.

    Password change

How to configure outbound email settings?

Google Cloud Platform doesn't allow SMTP traffic through default ports: 25, 465, 587. Check Google cloud documentation to learn how to use a VPN to bypass these restrictions or use a different port for sending emails from your application.

To manually configure the email settings for Multicraft, follow these steps:

  • Edit the /opt/bitnami/apps/multicraft/htdocs/protected/config/internal/application.php file and look for the uncommented transportOptions section.

  • Update this to reflect your SMTP server details. For instance, for a Gmail configuration, it would look something like this. Replace USERNAME and PASSWORD with your Gmail account username and password respectively.

     'transportOptions' => array(
         'host' => '',
         'username' => '',
         'password' => 'PASSWORD',
         'port' => '587',
         'encryption' => 'tls',
  • Make sure that the transportType variable is set to "smtp".

After this, Multicraft should be configured to send emails. You can also visit the Multicraft administration panel to update your mail preferences.

To configure the application to use other third-party SMTP services for outgoing email, such as SendGrid or Mandrill, refer to the FAQ.

NOTE: If you are using Gmail as the outbound email server and have experienced issues trying to send emails correctly, check the How to troubleshoot Gmail SMTP issues to learn the causes of these issues and how to solve them.

How to create a full backup of Multicraft?


The Bitnami Multicraft Stack is self-contained and the simplest option for performing a backup is to copy or compress the Bitnami stack installation directory. To do so in a safe manner, you will need to stop all servers, so this method may not be appropriate if you have people accessing the application continuously.

Follow these steps:

  • Change to the directory in which you wish to save your backup:

      $ cd /your/directory
  • Stop all servers:

      $ sudo /opt/bitnami/ stop
  • Create a compressed file with the stack contents:

      $ sudo tar -pczvf application-backup.tar.gz /opt/bitnami
  • Restart all servers:

      $ sudo /opt/bitnami/ start

You should now download or transfer the application-backup.tar.gz file to a safe location.


Follow these steps:

  • Change to the directory containing your backup:

      $ cd /your/directory
  • Stop all servers:

      $ sudo /opt/bitnami/ stop
  • Move the current stack to a different location:

      $ sudo mv /opt/bitnami /tmp/bitnami-backup
  • Uncompress the backup file to the original directoryv

      $ sudo tar -pxzvf application-backup.tar.gz -C /
  • Start all servers:

      $ sudo /opt/bitnami/ start

If you want to create only a database backup, refer to these instructions for MySQL and PostgreSQL.

How to upgrade Multicraft?

Upgrading Multicraft on Linux

It is strongly recommended to create a backup before starting the update process. If you have important data, create and try to restore a backup to ensure that everything works properly.

In order to upgrade Multicraft, you must follow these steps:

  • Stop all Multicraft services:

      $ sudo /opt/bitnami/ stop
  • Download the latest available Multicraft version from to a temporary directory and unpack it. In this case, we'll suppose that Multicraft files were unpacked to /tmp/multicraft.
  • Copy the new binaries and configure their ownership:

      $ sudo rsync -a /tmp/multicraft/bin/ /opt/bitnami/apps/multicraft/bin/
      $ sudo chown -R multicraft:multicraft /opt/bitnami/apps/multicraft/bin/
      $ sudo chown root:multicraft /opt/bitnami/apps/multicraft/bin/useragent
      $ sudo chmod 4550 /opt/bitnami/apps/multicraft/bin/useragent
  • Copy the new front-end files with proper ownership:

      $ sudo rsync -a /tmp/multicraft/panel/ /opt/bitnami/apps/multicraft/htdocs/
      $ sudo chown -R bitnami:daemon /opt/bitnami/apps/multicraft/htdocs/
      $ sudo chown -R daemon:daemon /opt/bitnami/apps/multicraft/htdocs/assets/
      $ sudo chown -R daemon:daemon /opt/bitnami/apps/multicraft/htdocs/protected/
  • Start all Multicraft services:

      $ sudo /opt/bitnami/ start
  • Run the install.php script by browsing to http://SERVER-IP/install.php. When running the wizard, you must ensure the used database is *bitnami_multicraft_panel for the Panel, and bitnami_multicraft_daemon for the Daemon.
  • Once the wizard finishes, delete the install.php file:

      $ sudo rm /opt/bitnami/apps/multicraft/htdocs/install.php

After this, you will have successfully upgraded Multicraft to the latest available version.

You can find more information on Multicraft's upgrade procedure in the official Multicraft documentation.

How to create an SSL certificate?

OpenSSL is required to create an SSL certificate. A certificate request can then be sent to a certificate authority (CA) to get it signed into a certificate, or if you have your own certificate authority, you may sign it yourself, or you can use a self-signed certificate (because you just want a test certificate or because you are setting up your own CA).

Follow the steps below:

  • Generate a new private key:

     $ sudo openssl genrsa -out /opt/bitnami/apache2/conf/server.key 2048
  • Create a certificate:

     $ sudo openssl req -new -key /opt/bitnami/apache2/conf/server.key -out /opt/bitnami/apache2/conf/cert.csr
    IMPORTANT: Enter the server domain name when the above command asks for the "Common Name".
  • Send cert.csr to the certificate authority. When the certificate authority completes their checks (and probably received payment from you), they will hand over your new certificate to you.

  • Until the certificate is received, create a temporary self-signed certificate:

     $ sudo openssl x509 -in /opt/bitnami/apache2/conf/cert.csr -out /opt/bitnami/apache2/conf/server.crt -req -signkey /opt/bitnami/apache2/conf/server.key -days 365
  • Back up your private key in a safe location after generating a password-protected version as follows:

     $ sudo openssl rsa -des3 -in /opt/bitnami/apache2/conf/server.key -out privkey.pem

    Note that if you use this encrypted key in the Apache configuration file, it will be necessary to enter the password manually every time Apache starts. Regenerate the key without password protection from this file as follows:

     $ sudo openssl rsa -in privkey.pem -out /opt/bitnami/apache2/conf/server.key

Find more information about certificates at

How to enable HTTPS support with SSL certificates?

TIP: If you wish to use a Let's Encrypt certificate, you will find specific instructions for enabling HTTPS support with Let's Encrypt SSL certificates in our Let's Encrypt guide.
NOTE: The steps below assume that you are using a custom domain name and that you have already configured the custom domain name to point to your cloud server.

Bitnami images come with SSL support already pre-configured and with a dummy certificate in place. Although this dummy certificate is fine for testing and development purposes, you will usually want to use a valid SSL certificate for production use. You can either generate this on your own (explained here) or you can purchase one from a commercial certificate authority.

Once you obtain the certificate and certificate key files, you will need to update your server to use them. Follow these steps to activate SSL support:

  • Use the table below to identify the correct locations for your certificate and configuration files.

    Variable Value
    Current application URL https://[custom-domain]/
      Example: or
    Apache configuration file /opt/bitnami/apache2/conf/bitnami/bitnami.conf
    Certificate file /opt/bitnami/apache2/conf/server.crt
    Certificate key file /opt/bitnami/apache2/conf/server.key
    CA certificate bundle file (if present) /opt/bitnami/apache2/conf/server-ca.crt
  • Copy your SSL certificate and certificate key file to the specified locations.

    NOTE: If you use different names for your certificate and key files, you should reconfigure the SSLCertificateFile and SSLCertificateKeyFile directives in the corresponding Apache configuration file to reflect the correct file names.
  • If your certificate authority has also provided you with a PEM-encoded Certificate Authority (CA) bundle, you must copy it to the correct location in the previous table. Then, modify the Apache configuration file to include the following line below the SSLCertificateKeyFile directive. Choose the correct directive based on your scenario and Apache version:

    Variable Value
    Apache configuration file /opt/bitnami/apache2/conf/bitnami/bitnami.conf
    Directive to include (Apache v2.4.8+) SSLCACertificateFile "/opt/bitnami/apache2/conf/server-ca.crt"
    Directive to include (Apache < v2.4.8) SSLCertificateChainFile "/opt/bitnami/apache2/conf/server-ca.crt"
    NOTE: If you use a different name for your CA certificate bundle, you should reconfigure the SSLCertificateChainFile or SSLCACertificateFile directives in the corresponding Apache configuration file to reflect the correct file name.
  • Once you have copied all the server certificate files, you may make them readable by the root user only with the following commands:

     $ sudo chown root:root /opt/bitnami/apache2/conf/server*
     $ sudo chmod 600 /opt/bitnami/apache2/conf/server*
  • Open port 443 in the server firewall. Refer to the FAQ for more information.

  • Restart the Apache server.

You should now be able to access your application using an HTTPS URL.

How to force HTTPS redirection with Apache?

Add the following lines in the default Apache virtual host configuration file at /opt/bitnami/apache2/conf/bitnami/bitnami.conf, inside the default VirtualHost directive, so that it looks like this:

<VirtualHost _default_:80>
  DocumentRoot "/opt/bitnami/apache2/htdocs"
  RewriteEngine On
  RewriteCond %{HTTPS} !=on
  RewriteRule ^/(.*) https://%{SERVER_NAME}/$1 [R,L]

After modifying the Apache configuration files:

  • Open port 443 in the server firewall. Refer to the FAQ for more information.

  • Restart Apache to apply the changes.

How to debug Apache errors?

Once Apache starts, it will create two log files at /opt/bitnami/apache2/logs/access_log and /opt/bitnami/apache2/logs/error_log respectively.

  • The access_log file is used to track client requests. When a client requests a document from the server, Apache records several parameters associated with the request in this file, such as: the IP address of the client, the document requested, the HTTP status code, and the current time.

  • The error_log file is used to record important events. This file includes error messages, startup messages, and any other significant events in the life cycle of the server. This is the first place to look when you run into a problem when using Apache.

If no error is found, you will see a message similar to:

Syntax OK

How to connect instances hosted in separate virtual networks or VPCs?

The Google Cloud Platform makes it possible to connect instances hosted in separate Virtual Private Clouds (VPCs), even if those instances belong to different projects or are hosted in different regions. This feature, known as VPC Network Peering, can result in better security (as services do not need to be exposed on public IP addresses) and performance (due to use of private, rather than public, networks and IP addresses).

Learn more about VPC Network Peering.

How to find the MariaDB database credentials?

How to connect to the MariaDB database?

You can connect to the MariaDB database from the same computer where it is installed with the mysql client tool.

$ mysql -u root -p

You will be prompted to enter the root user password. This is the same as the application password.

How to debug errors in your database?

Please note that depending on the version you have installed, you may find the MariaDB files at /opt/bitnami/mysql

The main log file is created at /opt/bitnami/mariadb/data/mysqld.log on the MySQL database server host.

How to reset the MariaDB root password?

Please note that depending on the version you have installed, you may find the MariaDB files at /opt/bitnami/mysql

If you don't remember your MariaDB root password, you can follow the steps below to reset it to a new value:

  • Create a file in /home/bitnami/mysql-init with the content shown below (replace NEW_PASSWORD with the password you wish to use):

     UPDATE mysql.user SET Password=PASSWORD('NEW_PASSWORD') WHERE User='root';
  • Stop the MariaDB server:

     $ sudo /opt/bitnami/ stop mariadb
  • Start MariaDB with the following command:

     $ sudo /opt/bitnami/mariadb/bin/mysqld_safe --defaults-file=/opt/bitnami/mariadb/my.cnf --pid-file=/opt/bitnami/mariadb/data/ --init-file=/home/bitnami/mysql-init 2> /dev/null &
  • Restart the MariaDB server:

     $ sudo /opt/bitnami/ restart mariadb
  • Remove the init script

     $ rm /home/bitnami/mysql-init

How to change the MariaDB root password?

You can modify the MariaDB password using the following command at the shell prompt:

$ /opt/bitnami/mariadb/bin/mysqladmin -p -u root password NEW_PASSWORD

How to access phpMyAdmin?

For security reasons, phpMyAdmin is accessible only when using as the hostname. To access it from a remote system, you must create an SSH tunnel that routes requests to the Web server from This implies that you must be able to connect to your server over SSH in order to access these applications remotely.

IMPORTANT: Before following the steps below, ensure that your Web and database servers are running.
NOTE: The steps below suggest using port 8888 for the SSH tunnel. If this port is already in use by another application on your local machine, replace it with any other port number greater than 1024 and modify the steps below accordingly. Similarly, if you have enabled Varnish, your stack's Web server might be running on port 81. In this case, modify the steps below to use port 81 instead of port 80 for the tunnel endpoint.

Accessing phpMyAdmin on Windows

Watch the following video to learn how to easily access phpMyAdmin on Windows through an SSH tunnel:

TIP: Refer to these instructions to learn how to obtain your private key.

In order to access phpMyAdmin via SSH tunnel you need an SSH client. In the instructions below we have selected PuTTY, a free SSH client for Windows and UNIX platforms. The first step is having PuTTY configured. Please, check how to configure it in the section how to connect to the server through SSH using an SSH client on Windows.

Once you have your SSH client correctly configured and you tested that you can successfully access to your instance via SSH, you need to create an SSH tunnel in order to access phpMyAdmin. For doing so, follow these steps:

  • In the "Connection -> SSH -> Tunnels" section, add a new forwarded port by introducing the following values:

    • Source port: 8888
    • Destination: localhost:80

    This will create a secure tunnel by forwarding a port (the "destination port") on the remote server to a port (the "source port") on the local host ( or localhost).

  • Click the "Add" button to add the secure tunnel configuration to the session. (You'll see the added port in the list of "Forwarded ports").

    PuTTY configuration

  • In the "Session" section, save your changes by clicking the "Save" button.
  • Click the "Open" button to open an SSH session to the server. The SSH session will now include a secure SSH tunnel between the two specified ports.
  • Access the phpMyAdmin console through the secure SSH tunnel you created, by browsing to
  • Log in to phpMyAdmin by using the following credentials:

    • Username: root
    • Password: application password. (Refer to our FAQ to learn how to find your application credentials).

Here is an example of what you should see:

Access phpMyAdmin

If you are unable to access phpMyAdmin, verify that the SSH tunnel was created by checking the PuTTY event log (accessible via the "Event Log" menu):

PuTTY configuration

Accessing phpMyAdmin on Linux and Mac OS X

To access the application using your Web browser, create an SSH tunnel, as described below.

  • Open a new terminal window on your local system (for example, using "Finder -> Applications -> Utilities -> Terminal" in Mac OS X or the Dash in Ubuntu).
  • Make sure that you have your SSH credentials (.pem key file) in hand.
  • Run the following command to configure the SSH tunnel. Remember to replace KEYFILE with the path to your private key and SERVER-IP with the public IP address or hostname of your server:

       $ ssh -N -L 8888: -i KEYFILE bitnami@SERVER-IP
NOTE: If successful, the above command will create an SSH tunnel but will not display any output on the server console.
  • Access the phpMyAdmin console through the secure SSH tunnel you created, by browsing to
  • Log in to phpMyAdmin by using the following credentials:

    • Username: root
    • Password: application password. (Refer to our FAQ to learn how to find your application credentials).

Here is an example of what you should see:

Access phpMyAdmin

How to modify PHP settings for Apache?

The PHP configuration file allows you to configure the modules enabled, the email settings or the size of the upload files. It is located at /opt/bitnami/php/etc/php.ini.

For example, to modify the default upload limit for PHP, update the PHP configuration file following these instructions.

After modifying the PHP configuration file, restart both Apache and PHP-FPM for the changes to take effect:

$ sudo /opt/bitnami/ restart apache
$ sudo /opt/bitnami/ restart php-fpm

How to modify the allowed limit for uploaded files in Apache?

Modify the following options in the /opt/bitnami/php/etc/php.ini file to increase the allowed size for uploads:

; Maximum size of POST data that PHP will accept.
post_max_size = 16M

; Maximum allowed size for uploaded files.
upload_max_filesize = 16M

Restart PHP-FPM and Apache for the changes to take effect.

$ sudo /opt/bitnami/ restart apache
$ sudo /opt/bitnami/ restart php-fpm    

How to upload files to the server with SFTP?

Although you can use any SFTP/SCP client to transfer files to your server, the link below explains how to configure FileZilla (Windows, Linux and Mac OS X), WinSCP (Windows) and Cyberduck (Mac OS X). It is required to use your server's private SSH key to configure the SFTP client properly. Choose your preferred application and follow the steps in the link below to connect to the server through SFTP.

How to upload files to the server

Troubleshooting Multicraft

How to debug errors in Multicraft?

The Multicraft log file is at /opt/bitnami/apps/multicraft/logs/multicraft.log.

How to connect to the Multicraft panel's built-in FTP?

Multicraft includes a built-in FTP server, so you don't need to allow remote FTP connections and worry about security. The FTP server allows you to access the Minecraft server's files and manage them, including backing them up.

Follow these steps:

  • Log in to the application as an administrator.
  • Select the "Servers" menu item and then select the server you wish to access.
  • On the server detail page, select the "Advanced -> Users" menu item.
  • Grant "full" access to the user account(s) you wish to use for FTP.

    FTP configuration

Once the user account(s) have been correctly configured, you can connect to the FTP server using either a third-party FTP client or the one built in to Multicraft. To use the built-in FTP client, follow these steps:

  • Log in to the application as a user with full FTP access.
  • Select the "Servers" menu item and then select the server you wish to access.
  • On the server detail page, select the "Files -> FTP File Access" menu item.
  • Enter the credentials for the user account to gain FTP access.

    FTP configuration

Here is an example of what the browser-based FTP client looks like:

FTP configuration

How to connect to the FTP server remotely?

For security reasons, the Multicraft FTP server is configured to only be accessible locally and not from remote hosts. For this reason, it is only possible to access the FTP server using the Multicraft server manager. If you want to be enable remote access to the FTP server from an FTP client (such as FileZilla, for instance), follow these steps to enable it:

  • Log in to the application as an administrator.
  • Select the "Servers" menu item and then select the server you wish to access.
  • On the server detail page, select the "Advanced -> Users" menu item.
  • Grant "full" access to the user account(s) you wish to use for FTP.

    FTP configuration

  • Open the /opt/bitnami/apps/multicraft/multicraft.conf configuration file.
  • Look for the ftp section.
  • Change the ftpIp value to and the ftpExternalIP value to your server's IP address.
  • Restart Multicraft:

     $ sudo /opt/bitnami/ restart multicraft_daemon

You should now be able to run your favorite FTP client, and connect with the following details:

  • Host: Your server's IP.
  • Port: The port for your server. By default, this is port 8021 on cloud deployments, virtual machines and non-privileged/non-root Unix native installations, and port 21 on Windows native installations and other Unix installations.
  • Username: The FTP username, as listed in the "Advanced -> Users" screen. Note that the FTP username may not be the same as the login username.
  • Password: The password corresponding to the FTP user name.

    FTP configuration

How to connect to a Multicraft server in Minecraft?

Once you have all your servers created, you will be able to play Minecraft with your previously created Multicraft servers. Ensure all the ports are open and accessible and follow these steps:

  • Find your server IP and port in the Multicraft Server Manager by clicking the "Servers -> Manage Servers" menu item. If the IP is, enter the IP of your instance/server (for instance,

    Minecraft configuration

  • Open the client and click "Play".

  • In the main Multicraft game menu screen, click "Multiplayer".

    Minecraft configuration

  • Select "Add Server" or "Direct Connect".

  • Add your server address and join the server.

    Minecraft configuration

  • Enjoy your game!

How to create a Minecraft server in Multicraft?

The main purpose of Multicraft is to manage multiple Minecraft servers. The free version of Multicraft allows you to have one server with 10 players.

By default, Multicraft does not include the Minecraft or CraftBukkit server file, but it includes a tool to download them, as described below.

  • Log in to the application as an administrator.
  • Select the "Settings -> Update Minecraft" menu item.
  • In the "File" field on the resulting page, select your preferred Minecraft server. By default, "Default Minecraft Server" is selected, which is the same multiplayer server file you can download from Mojang's Minecraft website.
  • Set the "Type" field to "JAR and Config" and the "Action" field to "Update".
  • Click the "Go" button, and wait until the process finishes.

    Server creation

You should see something like "minecraft_server.jar: Update successful" or "minecraft_server.jar: Up to date".

Server creation

After downloading the server files, you can create a new server as described below:

  • Log in to the application as an administrator.
  • Select the "Servers -> Create Server" menu item.
  • Enter the server details. If no port is specified, a default port value will be selected starting from the first available port at 25565.

    Server creation

  • Click the "Create" button.
  • You will now be redirected to the Minecraft server's configuration page. The port and IP should now be assigned if they weren't in the previous step. Ensure that the specified port is open and accessible in your firewall, network or your cloud provider's network configuration.
  • In the "JAR File" field of the server configuration page, select the file downloaded previously.
  • Modify other configuration options if needed. Then, click the "Save" button.
  • If necessary, click the "Accept EULA" button to accept Multicraft's End-User License Agreement.

    Server creation

  • Click the "Start" button to start the server.

    Server creation

Your server will now start and its status will change to "Online".

Server creation

Multicraft has a list of how-to guides on their websites. You can check them out at


Bitnami Documentation