How to Install Mastodon on a Vultr Cloud Server

Introduction

Mastodon is an open-source decentralized social network that fronts full data control, and ease of use as its key features. In this article you’ll install and secure Mastodon on a Ubuntu 22.04 Vultr Cloud Server.

Prerequisites

Before you begin, be sure to:

• Deploy a Ubuntu 22.04 server on Vultr with at least:
  • 4GB RAM
  • 2VCPus
• Create a new domain A record pointing to the server.
• Update the server.
• Use SSH to access the server with a non-root sudo user account.

Setup the Mastodon Database

Mastodon requires a PostgreSQL database to store files and application data. You can either install PostgreSQL on your server, or deploy a Vultr managed database for PostgreSQL to avoid any bottlenecks in your production environment. For this article, use a Vultr managed database for PostgreSQL.

• Deploy a Vultr Managed Database for PostgreSQL.

1. Install the PostgreSQL client package.

     $ sudo apt install postgresql-client
   

2. Login to your PostgreSQL database server. Replace the following example values with your actual Vultr database details.

     $ psql -h example.vultrdb.com -p 5432 -U vultradmin postgres

   If installed on the same server, run the following command to login.

     $ sudo -u postgres -i psql
   

3. Create the Mastodon database.

     CREATE DATABASE mastodondb;
   

4. Create a new database user.

     CREATE USER mastodon_user;
   

5. Assign the user a strong password.

     ALTER USER mastodon_user WITH ENCRYPTED PASSWORD 'strong-password';
   

6. Grant the user database creation privileges.

     ALTER USER mastodon_user createdb;
   

7. Grant the user ownership privileges to the mastodon database.

     ALTER DATABASE mastodondb OWNER TO mastodon_user;
   

8. Exit the PostgreSQL console.

     \q

Install Postfix and setup SMTP Relay

To send emails from your Mastodon server, you need to install Postfix and setup SMTP relay on the server. If you have an existing mail server, configure it to act as your SMTP relay host. Also, you can use a free email service provider such as Sendinblue, Mailjet or Mailchimp to act as the relay host. For this article, create a Sendinblue account to act as the SMTP relay host then setup Postfix as described below.

1. Login to your Sendinblue account.

2. Click your account in the top right corner and select Senders & IP from the list.

3. Click Domains within the senders, domains and dedicated IPs section.

4. Click Add a domain, and enter your domain in thedomain name field, then click save to generate DNS records.

5. If you host domain DNS on Vultr, access the DNS panel, and create the records to authenticate your account.

6. When added, click Verify & authenticate to approve your domain.

7. Navigate back to Senders & IP, select Senders, and click Add a sender.

8. Assign your sender account a name, for example Mastodon on Vultr, then enter the email address to assign the Mastodon sender address in the From email field. For example, noreply@mastodon.example.com, and click save your sender details.

9. Navigate to Transactional on the main menu bar.

10. Within the configuration section, copy your Login and encrypted password in the SMTP Settings field.

11. Click the Configuration example with Postfix tab, select and copy the generated code snippet.

    

12. Access your Vultr server SSH session.

13. Update the server.

     $ sudo apt update
    

14. Install Postfix and the libsasl2-modules package.

     $ sudo apt install postfix libsasl2-modules -y

    When prompted for the mail configuration type, keep Internet Site selected, and press enter to proceed. Enter your domain name in the System mail name field and press enter to install Postfix.

15. Using a text editor such as nano, edit the main Postfix configuration file.

     $ sudo nano /etc/postfix/main.cf
    

16. Paste your Sendinblue Postfix code at the end of the file. For example:

     smtp_sasl_auth_enable = yes
     smtp_sasl_password_maps = static:user:password
     smtp_sasl_security_options = noanonymous
     smtp_tls_security_level = may
     header_size_limit = 4096000
     relayhost = smtp-relay.sendinblue.com:587
    

17. Find the following line.

     relayhost =
    

18. Comment it by adding # at the start of the line to avoid configuration errors as below.

     #relayhost =

    Save and close the file.

19. Create the sasl_passwd file in the Postfix directory as below.

     $ sudo touch /etc/postfix/sasl_passwd
    

20. Edit the file.

     $ sudo nano /etc/postfix/sasl_passwd
    

21. Add the following contents. Replace example-user:password with the details you copied earlier on step 10.

     [smtp-relay.sendinblue.com]:587  example-user:password

    Save and close the file.

22. Create a corresponding hash db file using postmap.

     $ sudo postmap /etc/postfix/sasl_passwd
    

23. Restart Postfix to save settings.

     $ sudo systemctl restart postfix
    

24. To test that your SMTP settings work, install the mailx package, and send a test email to your active email address as below.

    Install mailx

     $ sudo apt install bsd-mailx

    Send the test email. Replace hello@example.com with your active email address.

     $ echo "Hello, your SMTP configuration Works." | mailx -r noreply@mastodon.example.com -s Testing SMTP hello@example.com

    If your SMTP settings are correct, you should receive an email from noreply@mastodon.yourdomain.com

Download and Prepare Mastodon

1. Install Nginx to work as the main web server application.

     $ sudo apt install nginx -y
   

2. Mastodon requires NodeJS version 16, run its repository installer.

     $ curl -sL https://deb.nodesource.com/setup_16.x | sudo bash -
   

3. Install NodeJS

     $ sudo apt install nodejs
   

4. Install Ruby, Ruby, Redis® Server and all necessary Mastodon dependencies.

     $ sudo apt install git gem ruby ruby-dev build-essential bundler npm libidn11-dev libjemalloc-dev libpq-dev rbenv redis-server pngquant jhead jpegoptim gifsicle imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file g++ libprotobuf-dev protobuf-compiler pkg-config gcc autoconf libgdbm-dev -y
   

5. Using npm, install the yarn package.

     $ sudo npm install --global yarn
   

6. Clone the Mastodon GitHub repository.

     $ git clone https://github.com/mastodon/mastodon.git
   

7. Move the created mastodon directory to a more central directory like /var/www/.

     $ sudo mv mastodon/ /var/www/
   

8. Create a new Mastodon user with no login access on the server.

     $ sudo adduser mastodon-user --system --group --disabled-login
   

9. Grant the user ownership privileges to the mastodon directory.

     $ sudo chown -R mastodon-user:mastodon-user /var/www/mastodon/
   

10. Navigate to the mastodon directory.

     $ cd /var/www/mastodon/
    

11. Visit the Mastodon GitHub releases page and keep note of the latest version, then, install it as the mastodon user as below.

     $ sudo -u mastodon-user git checkout <version>

For example, to install version v4.0.2, run the following command.

     $ sudo -u mastodon-user git checkout v4.0.2

Install and Configure Mastodon

1. Verify that you’re operating in the mastodon directory.

     $ pwd
   

2. Install the Ruby dependency manager bundler.

     $ sudo gem install bundler
   

3. Install Mastodon dependency packages.

     $ sudo -u mastodon-user bundle config deployment 'true'
   
     $ sudo -u mastodon-user bundle config without 'development test'
   
     $ sudo -u mastodon-user bundle install -j$(getconf _NPROCESSORS_ONLN)
   

4. Start the Mastodon installation wizard.

     $ sudo -u mastodon-user RAILS_ENV=production bundle exec rake mastodon:setup

   You should receive the following output:

     Your instance is identified by its domain name. Changing it afterward will break things.
     Domain name: 

   Reply to each of the prompts and press enter as follows:

   *Domain name: Enter your Mastodon domain name. This article uses mastodon.example.com. *Enable single user mode: N to allow multiple user registrations, enter Y for personal use. *Are you using Docker to run Mastodon: N *PostgreSQL host: Enter your Vultr managed database for PostgreSQL host URL, or 127.0.0.1 if you installed PostgreSQL locally on the server. *PostgreSQL port: The Vultr managed database for PostgreSQL port. Keep 5432 for local PostgreSQL. *PostgreSQL database: Enter the Mastodon database you created earlier. *PostgreSQL user: Mastodon database user. *PostgreSQL user password: The Mastodon database user password. *Redis® host: 127.0.0.1 Redis® port: 6379 *Redis® password: Press enter as the local Redis® instance has no password. *Do you want to store uploaded files on the cloud? Enter Yes to fill in your Vultr Object Storage details, No to store all Mastodon files directly on your server storage. *Do you want to send emails from localhost? Enter Yes to use the Postfix configuration. *E-mail address to send e-mails from”: noreply@mastodon.example.com depending on the sender address you set in the Postfix sasl_passwd configuration. *Send a test e-mail with this configuration right now? Enter Yes to send a test message to your email address.

   • Send test e-mail to: Enter your active email address to receive the test email.
   • This configuration will be written to .env.production Save configuration?: Yes to save all changes to the environment file.
   • The final step is compiling CSS/JS assets. This may take a while and consume a lot of RAM. Compile the assets now?: Yes to start installing Mastodon.
   • Do you want to create an admin user straight away?: Yes to setup the Mastodon administrator.
   • Username: Enter your desired administrator username, admin by default.
   • E-mail: Enter your active email address.

When installation is complete, an auto generated password displays for your administrator account, select and copy it to your clipboard.

Security

Mastodon listens on the local host port 3000 and 4000, to secure your production server, verify that these ports are not accessible through the public interface. Instead, allow the HTTP port 80, and HTTPS port 443 on your firewall to access Mastodon through your domain name by setting up the Nginx reverse proxy as described in this section.

1. Verify that Uncomplicated Firewall (UFW) is running on your Ubuntu server.

     $ sudo ufw status

   If inactive, allow the SSH port 22, and start the firewall.

     $ sudo ufw allow 22/tcp && sudo ufw enable
   

2. Show the firewall table, and verify that Mastodon ports 3000,4000 are not allowed through the firewall.

     $ sudo ufw status
   

3. Allow the HTTP port 80.

     $ sudo ufw allow 80/tcp
   

4. Allow the HTTPS port 443.

     $ sudo ufw allow 443/tcp
   

5. Restart the firewall to load changes.

     $ sudo ufw reload

Optional: Configure the Vultr Firewall

To tighten your Mastodon production server security, configure the Vultr Firewall to operate on top of your existing server firewall as below.

1. Access your Vultr account.

2. On the Products panel, find and click Firewall panel on the navigation menu.

3. Click Add Firewall Group, assign your group a unique description, for example production server rules to create the firewall group.

4. On the Manage Firewall Group panel, navigate to the Inbound IPV4 Rules section.

5. Click the + Add Firewall Rule Action to allow SSH access as your first rule. To tighten server security, edit the rule, and select MyIP as the source.

6. Click the Protocol drop down, and select HTTP from the common applications list, then, click the + Action button to add the firewall rule.

7. Select HTTPS from the Protocol drop down, keep Anywhere as the source, and click the + Action button to save rule.

   

8. Click Linked Instances on the left navigation list, select your Mastodon server from the list, and click the + Add Linked Instance button to apply changes.

To tighten your server security with more firewall rules, please visit the Vultr Firewall documentation.

Generate SSL Certificates

To secure Mastodon, you need to serve all application requests over HTTPS instead of plain HTTP. To enable HTTPS, generate free SSL certificates from a trusted authority like Let’s Encrypt as described in this section.

1. Install the snapd daemon.

     $ sudo apt install snapd
   

2. Install the Certbot Let’s Encrypt application.

     $ sudo snap install --classic certbot
   

3. Activate the system-wide certbot command.

     $ sudo ln -s /snap/bin/certbot /usr/bin/certbot
   

4. Temporarily stop Nginx to avoid conflicts on port 80.

     $ sudo systemctl stop nginx
   

5. Generate a free SSL Certificate. Replace mastodon.example.com with the domain name pointed to your server.

     $ sudo certbot certonly --standalone -d mastodon.example.com -m hello@example.com --agree-tos

   When successful, the SSL certificate files are present in the /etc/letsencrypt/live/ directory.

6. Restart Nginx

     $ sudo systemctl restart nginx
   

7. Test that the certificate auto renews upon expiry.

     $ sudo certbot renew --dry-run

Setup Nginx as a Reverse Proxy

1. Navigate to the Mastodon files directory.

     $ cd /var/www/mastodon/
   

2. Copy the Mastodon Nginx configuration template to the Nginx conf.d directory.

     $ sudo cp dist/nginx.conf /etc/nginx/conf.d/mastodon.conf
   

3. Edit the new Mastodon Nginx configuration file.

     $ sudo nano /etc/nginx/conf.d/mastodon.conf
   

4. Find the following lines in both server { blocks.

     server_name example.com;
     root /home/mastodon/live/public;
   

5. Change the server_name directive to your domain name, and root to your Mastodon directory as below.

     server_name mastodon.example.com;
     root /var/www/mastodon/;
   

6. Find the following two lines within the listen 443 server block.

     # ssl_certificate     /etc/letsencrypt/live/example.com/fullchain.pem;
     # ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;
   

7. Uncomment them by removing the # key, then, change example.com to your domain as below.

     ssl_certificate     /etc/letsencrypt/live/mastodon.example.com/fullchain.pem;
     ssl_certificate_key /etc/letsencrypt/live/mastodon.example.com/privkey.pem;

   Save and close the file.

   For the setting to be successful, verify that your domain is present in the /etc/letsencrypt/live/ directory, else, request for an SSL certificate without the Nginx plugin to avoid Nginx errors.

8. Test your Nginx configuration for errors.

     $ sudo nginx -t

   If the command returns any error, please verify that you made the correct configuration changes as described above.

9. Restart Nginx for changes to take effect.

     $ sudo systemctl restart nginx

Setup Mastodon as a System Service

To install and start Mastodon as a system service, edit the system template files using the sed stream editor, and setup the services as below.

1. Verify that the Mastodon system template files are available.

     $ ls /var/www/mastodon/dist/
   

2. Change the default user entry in all service template files to your Mastodon user account as below.

     $ sudo sed -i '7s/mastodon/mastodon-user/' /var/www/mastodon/dist/mastodon*.service
   

3. Change the working directory in all files from /home/mastodon/live to your Mastodon directory /var/www/mastodon/.

     $ sudo sed -i 's/home\/mastodon\/live/var\/www\/mastodon/g' /var/www/mastodon/dist/mastodon*.service
   

4. Change the bundle directory in all files from /home/mastodon/.rbenv/shims/bundle to /usr/local/bin/bundle.

     $ sudo sed -i 's/home\/mastodon\/.rbenv\/shims/usr\/local\/bin/g' /var/www/mastodon/dist/mastodon*.service
   

5. Copy all service files to the /etc/systemd/system/ directory.

     $ sudo cp /var/www/mastodon/dist/mastodon*.service /etc/systemd/system/
   

6. Reload the systemd daemon to enable the files.

     $ sudo systemctl daemon-reload
   

7. Enable each of the 3 Mastodon services to start at boot time.

     $ sudo systemctl enable mastodon-web
   
     $ sudo systemctl enable mastodon-sidekiq
   
     $ sudo systemctl enable mastodon-streaming
   

8. Start all Mastodon services.

     $ sudo systemctl start mastodon-web
   
     $ sudo systemctl start mastodon-sidekiq
   
     $ sudo systemctl start mastodon-streaming
   

9. Verify that all services are up and running.

     $ sudo systemctl status mastodon-web
   
     $ sudo systemctl status mastodon-sidekiq
   
     $ sudo systemctl status mastodon-streaming
   

10. Verify that Mastodon is listening on port 3000.

     $ sudo ss -lnpt | grep 3000

    Output:

     LISTEN    0         1024             127.0.0.1:3000             0.0.0.0:*        users:(("ruby2.7",pid=76286,fd=5),("ruby2.7",pid=76282,fd=5),("ruby2.7",pid=76216,fd=5))

Test

1. Using a web browser like Google Chrome, visit your Mastodon server domain.

     https://mastodon.example.com
   

2. To test that new users can register on your Mastodon server, click Create account.

3. Fill-in your user details, and enter your non-administrator email to sign up.

4. Check your email inbox, and click the Verify email address button to approve your new user registration.

   

5. Log out the user, then, Log in using the administrator username and password you created during installation.

6. Start managing your Mastodon server.

Troubleshooting Common Issues

During and after installation of Mastodon on your server, you may receive any of the following errors, if you encounter any of them, fix them using the recommendations below.

1. Mastodon unable to send mails

   Verify that you setup Postfix correctly, and you are able to send emails through your relay host. To investigate why emails are not sent from your Mastodon server, visit the following URL while logged in with the administrator account.

      https://mastodon.example.com/sidekiq/retries

   Depending on your results, view the Postfix mail log and check for any reported errors.

     $ sudo cat /var/log/mail.log
   

2. An error occurred while installing charlock_holmes (0.7.7), and Bundler cannot continue

   You may receive this error while installing Mastodon, to clear it, please install all required dependencies using the following command.

3. Database connection could not be established with this configuration, try again. connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL:

   You may receive this error if you are running PostgreSQL on your server, to clear it, please enter 127.0.0.1 as your database host.

4. Mastodon Runtime Error

   If the Mastodon returns any runtime errors, please check the systemd journals for errors.

     sudo journalctl -eu mastodon-web
   
     sudo journalctl -eu mastodon-streaming
   
     sudo journalctl -eu mastodon-sidekiq
   

5. Mastodon not loading

   Verify that Nginx is up and running.

     $ sudo systemctl status nginx

   Verify that all Mastodon services are active and running.

     $ sudo systemctl status mastodon-web
   
     $ sudo systemctl status mastodon-sidekiq
   
     $ sudo systemctl status mastodon-streaming

Backup Mastodon

To keep ahead of any potential server or application failures, it’s important to backup the following Mastodon data:.

• Mastodon PostgreSQL database
• Environment.env.production file
• User and system files
• Local Redis® database

1. In your home directory, create a new Mastodon backup files directory.

     $ mkdir ~/mastodon-backup
   

2. Backup the Mastodon PostgreSQL database using pg_dump.

     $ pg_dump -F t -h example.vultrdb.com -p 5432 -U vultradmin -d matodondb -f ~/mastodon-backup/database.tar

   For local PostgreSQL.

     $ sudo -u postgres -i pg_dump -F t mastodondb > ~/mastodon-backup/database.tar
   

3. Make a full backup of the Mastodon directory.

     $ cp -r /var/www/mastodon/ ~/mastodon-backup/mastodon-files
   

4. Back up the Redis® database.

     $ cp /var/lib/redis/dump.rdb ~/mastodon-backup/mastodon-redis.rdb
   

5. To easily back up all necessary Mastodon files, and replace any existing files in your target directory, create a new backup.sh file.

     $ nano backup.sh

   Add the following contents to the file.

     #!/bin/sh/
   
     echo " Hello, This Vultr Script will help you backup your local Mastodon PostgreSQL Database, Files and Redis® Database"
   
     echo "Please enter the target directory where you'd like to create the backup files directory"
   
     read directory
   
     echo "The mastodon-backup directory will be stored in: $directory"
   
     mkdir $directory/mastodon-backup
   
     echo "Please enter your local Mastodon PostgreSQL database name"
   
     read dbname
   
     echo "!!!!Backing up the PostgreSQL database $dbname!!!!"
   
     sudo -u postgres -i pg_dump -F t mastodondb > $directory/mastodon-backup/mastodon-database.tar
   
     echo "!!!!Backing up the Mastodon Redis® Database!!!!"
   
     cp /var/lib/redis/dump.rdb $directory/mastodon-backup/mastodon-redisdb.rdb
   
     echo "!!!!Making a Full Backup of the Mastodon files directory!!!!"
   
     cp -r /var/www/mastodon $directory/mastodon-backup/mastodon-files
   
     echo " Done! Backup Successful"

   Save and close the file.

   Run the script.

         $ bash backup.sh

Upgrade Mastodon

Before upgrading Mastodon, please make a full backup to recover your instance in case your upgrade breaks.

1. Navigate to the Mastodon directory.

     $ cd /var/www/mastodon/
   

2. Fetch new Mastodon release tags.

     $ sudo -u mastodon-user git fetch --tags
   

3. Upgrade to the latest version. For example, to upgrade to v4.0.2, run the following command.

     $ sudo -u mastodon-user git checkout v4.0.2
   

4. Migrate the database.

     $ sudo -u mastodon-user RAILS_ENV=production bundle exec rake db:migrate
   

5. Compile Mastodon assets.

     $ sudo -u mastodon-user bundle install -j$(getconf _NPROCESSORS_ONLN)
   
     $ sudo -u mastodon-user RAILS_ENV=production bundle exec rails assets:precompile
   

6. When successful, migrate the database again.

     $ sudo -u mastodon-user RAILS_ENV=production bundle exec rake db:migrate
   

7. Restart the web process.

     $ sudo systemctl restart mastodon-web
   

8. Restart the streaming API.

     $ sudo systemctl restart mastodon-streaming
   

9. Restart background workers.

     $ sudo systemctl restart mastodon-sidekiq

Conclusion

You have installed Mastodon on a Vultr Cloud server, for more configuration options, please visit the official Mastodon documentation.