AWS Provisioned Servers Are Disappearing
To ensure Forge works correctly with AWS, please review these requirements.DigitalOcean Droplet Limit Exceeded
This error is returned by DigitalOcean when you have reached a limit on how many droplets you can create. You can ask DigitalOcean to increase your droplet limit by contacting their support. Once they have increased your limit, you may create servers in Forge.Expanding Server Disk Space
When you increase your server’s disk size through your VPS provider, the additional space is not automatically available to your Ubuntu filesystem. You will need to expand the operating system’s filesystem to use the newly allocated space.We strongly recommend creating a backup or snapshot of your server through your VPS provider before proceeding with disk expansion operations. While these commands are generally safe, disk operations carry inherent risks.
Checking Current Disk Usage
First, check your current disk usage to identify which partition needs expansion:/
).
Expanding the Filesystem
Most Forge servers use standard partitions without LVM (Logical Volume Manager). If your system uses LVM, the disk expansion process is different and requires additional steps using thepvresize
and lvextend
commands.
For standard, non-LVM systems, follow these steps:
-
First, check your partition table:
-
If the partition needs to be expanded, use the
growpart
command: -
Resize the filesystem:
Verifying the Expansion
After completing the expansion, verify that the additional space is available:Troubleshooting
“No space left on device” Error If you encounter an error likemkdir: cannot create directory '/tmp/growpart.xxxx': No space left on device
, your root filesystem is completely full, preventing even basic commands from running. You will need to free up some temporary space first:
Consider setting up disk usage monitoring to receive alerts before your disk space runs critically low, giving you time to expand the disk proactively.
Operating System Release Upgrades
When connecting to your server via SSH, you may encounter messages likeNew release '24.04.1 LTS' available
or be instructed to run do-release-upgrade
. However, we strongly advise against performing operating system release upgrades on Forge-managed servers.
Upgrading your server’s operating system version can break Forge’s ability to manage your server and may cause application downtime.
- Overwrite critical configuration files
- Change system service behaviors
- Break compatibility with installed PHP versions, databases, and other services
- Prevent Forge from properly managing your server
- Cause unexpected application errors or downtime
Recommended Approach
Instead of upgrading, we recommend provisioning a new server with your desired Ubuntu version through Forge, then migrating your sites to the new server. This approach ensures full Forge compatibility and reduces the risk of unexpected issues that can arise from in-place upgrades.For teams that prefer a fully managed solution, Laravel Cloud eliminates operating system concerns entirely. While Forge provides maximum control and flexibility over your infrastructure, Laravel Cloud’s fully-managed approach means you never need to think about server maintenance or OS versions.
Restarting PHP FPM
When configuring your server, Forge configures FPM so that it can be restarted without using your server’s “sudo” password. To do so, you should issue the following command. Of course, you should adjust the PHP version to match the version of PHP installed on your machine:flock
is used to prevent concurrent php-fpm reloads. Without a lock, simultaneous restart attempts could lead to race conditions, brief service interruptions, or inconsistent process states.Resetting The forge
User Sudo Password
Forge does not store your server’s forge
user sudo password and is therefore unable to reset it for you. To reset the forge
user sudo password, you’ll need to contact your server provider and regain SSH access to your server as the root
user.
Once you are connected to your server as the root
user, you should run the passwd forge
command to redefine the forge
user sudo password.
Digital Ocean
If your servers are managed by DigitalOcean, the following steps should assist you in resetting theforge
user’s sudo password using Digital Ocean’s dashboard.
-
First, on DigitalOcean’s dashboard, click on the server name. Then, within the “Access” tab, click on “Reset Root Password”. Usually, this operation restarts the server and sends the new
root
user’s sudo password to your DigitalOcean account’s associated email address. -
Next, still on the “Access” tab, click on “Launch Droplet Console” to gain access to your server terminal as the
root
user. During this step, you will be asked to redefine theroot
user’s sudo password. -
Finally, execute the
passwd forge
terminal command as theroot
user to redefine theforge
user’s sudo password.
Server Disconnected
There are several reasons why your server may have a “disconnected” status. We encourage you to check these common solutions before contacting support:- Verify that the server is powered on via your server provider’s dashboard. If the server is powered off, you should restart it using your provider’s dashboard.
- Verify that the public IP address of the server is known to Forge (the public IP address may change between reboots of the actual VPS).
- Verify that the Forge generated public key for the server is included in the
/root/.ssh/authorized_keys
and/home/forge/.ssh/authorized_keys
files. This key is available via the “Settings” tab of your server’s Forge management panel. - If your server is behind a firewall, make sure you have allowed Forge’s IP addresses to access the server.
- If you removed Port 22 from the server’s firewall rules, you will need to contact your server provider and ask them to restore the rule. Removing this rule prevents Forge from accessing your server via SSH.
- Remove any private keys or other lines that do not contain a valid public key from the
/root/.ssh/authorized_keys
and/home/forge/.ssh/authorized_keys
files.
root
user and share the output with Forge support:
If Forge is not able to connect to your server, you will not be able to manage it through the Forge dashboard until connectivity is restored.
”Too Many Open Files” Error
If you are receiving an error stating that your server has “too many open files”, you likely need to increase the maximum amount of file descriptors that your operating system is configured to allow at a given time. This may be particularly true if your server will be handling a very large number of incoming web requests. First, ensure the maximum number of “open files” is correctly configured based on the size of your server. Usually, the maximum number of open files allowed by the operating system should be about 100 files for every 1MB of RAM. For example, if your server has 4GB memory, the maximum number of open files can safely be set to409600
.
You can determine how many files your operating system currently allows to be opened at once by running the sysctl fs.file-max
command. You can configure the existing setting by adding or modifying the following line in /etc/sysctl.conf
:
/etc/security/limits.conf
file and adding the following lines:
/etc/security/limits.conf
file:
nginx
user to /etc/security/limits.conf
:
/etc/nginx/nginx.conf
file:
Upgrading Composer
The latest version of Composer is installed by Forge when a new server is provisioned. However, as your server ages, you may wish to upgrade the installed version of Composer. You may do so using the following command:Servers are provisioned with a Scheduled job that updates Composer. You should delete and recreate the existing job via the server’s “Scheduled Jobs” tab after upgrading Composer.
Upgrading Meilisearch
If you would like to install the latest Meilisearch binaries on your server, please follow the official Meilisearch upgrade guide. On most Forge servers, the Meilisearch binary is installed at/usr/local/bin/meilisearch
and the database is stored at /var/lib/meilisearch
.
Upgrading Nginx
The latest version of Nginx is installed by Forge when a new server is provisioned. However, as your server ages, you may wish to upgrade the installed version of Nginx. You may do so using the following commands:You should upgrade the Nginx version on your server at your own risk. Upgrading the version of Nginx installed on your server may cause downtime or conflict with other installed software.