Foundry VTT can be self-hosted on Ubuntu Server. The setup is straightforward: download the Node.js application, install it as a service, configure the firewall, and use Let’s Encrypt for the SSL certificate. The minimum requirements are 2 GB of RAM, 2 vCPUs, and 20 GB of storage.
Table of contents
- The minimum requirements
- The installation
- The systemd service
- The firewall
- The SSL certificate
- The backup
- FAQ
The minimum requirements
The minimum requirements:
- CPU: 2 vCPUs. Foundry VTT is mostly single-threaded, so the clock speed matters more than the core count.
- RAM: 2 GB. The bigger the world, the more memory.
- Storage: 20 GB. The world data, the assets, the modules.
- Network: 5-10 Mbps. The bandwidth needed for the players to connect.
The installation
The installation:
- Install Node.js:
sudo apt install nodejs. - Download Foundry VTT: from the official website, the Linux Node.js version.
- Unzip the application:
unzip foundryvtt-X.X.X.zip. - Move the application to
/opt/foundryvtt:sudo mv foundryvtt-X.X.X /opt/foundryvtt. - Make the application executable:
sudo chmod +x /opt/foundryvtt/resources/app/main.js. - Test the application:
node /opt/foundryvtt/resources/app/main.js.
The systemd service
The systemd service:
- Create the service file:
/etc/systemd/system/foundryvtt.service. - The service file specifies the user, the working directory, the command, and the restart policy.
- Reload systemd:
sudo systemctl daemon-reload. - Enable the service:
sudo systemctl enable foundryvtt. - Start the service:
sudo systemctl start foundryvtt. - Check the status:
sudo systemctl status foundryvtt.
The firewall
The firewall:
- Open the port 30000 (the default Foundry VTT port) in the firewall.
- On the cloud, open the port in the security group.
- On the local network, open the port in the router’s firewall.
- The team that wants to use a different port can change it in the Foundry VTT configuration.
The SSL certificate
The SSL certificate:
- Use Let’s Encrypt (via certbot) to get a free SSL certificate.
- Configure the reverse proxy (NGINX, Caddy) to terminate the SSL and forward the traffic to Foundry VTT.
- The team that uses a subdomain (e.g., foundry.example.com) should set up the DNS record before requesting the certificate.
The backup
The backup:
- The world data is the most important. Back it up at least once a day.
- The backup can be a snapshot of the VM, a snapshot of the world directory, or a copy of the world directory to S3.
- The restore should be tested at least once a quarter.
FAQ
Can I host Foundry VTT on Ubuntu Server?
Yes. The minimum requirements are 2 GB of RAM, 2 vCPUs, and 20 GB of storage. The setup is straightforward: download the application, install it as a systemd service, configure the firewall, and use Let’s Encrypt for the SSL certificate.
What are the minimum requirements for Foundry VTT?
2 vCPUs, 2 GB RAM, 20 GB storage, 5-10 Mbps network. Foundry VTT is mostly single-threaded, so the clock speed matters more than the core count.
What port does Foundry VTT use?
The default is 30000. The team can change it in the configuration.
How do I run Foundry VTT as a systemd service?
Create a service file at /etc/systemd/system/foundryvtt.service. The service file specifies the user, the working directory, the command, and the restart policy. Reload systemd and enable the service.
How do I get an SSL certificate for Foundry VTT?
Use Let’s Encrypt (via certbot) to get a free SSL certificate. Configure a reverse proxy (NGINX, Caddy) to terminate the SSL and forward the traffic to Foundry VTT.
How do I back up Foundry VTT?
Back up the world data at least once a day. The backup can be a snapshot of the VM, a snapshot of the world directory, or a copy of the world directory to S3. Test the restore at least once a quarter.
If you are sizing a game server for a new project, the RunxBuild hosting calculator is the place to model the line items. The instances, the memory, the storage, the bandwidth - each one is a separate number, and the team’s mental model for the platform is the sum of those numbers. The RunxBuild dashboard is where the team sees the actual game server in one place.