Deploy Symfony on VPS: complete guide 2024

Shared hosting locks you into the server's PHP version, disables extensions deemed 'unsafe', and forbids persistent background processes. Symfony 7 requires PHP 8.2 as a minimum — a constraint many shared hosts still don't meet. On a VPS, you choose PHP 8.3 from day one, configure OPcache precisely, and install ext-redis, ext-intl or ext-amqp as needed.

Asynchronous workers (Symfony Messenger) require a persistent background process managed by Supervisor or systemd. On shared hosting, this is simply impossible. On a VPS, it starts with one command and restarts automatically after a crash — essential for any Symfony app handling transactional emails, push notifications or file imports.

Operating system: Ubuntu 24.04 LTS or Debian 12. Both distributions benefit from the ondrej/php repository and long-term support compatible with Symfony maintenance cycles.

PHP: 8.3 recommended (minimum 8.2 for Symfony 7). Required extensions: php8.3-cli, php8.3-fpm, php8.3-mbstring, php8.3-xml, php8.3-curl, php8.3-zip, php8.3-intl, php8.3-opcache. Add php8.3-redis for Redis, php8.3-pgsql for PostgreSQL.

Composer: version 2.x required.

Database: MySQL 8.0+ or PostgreSQL 16+.

Minimum RAM:
- 1 GB: development or light app without queues
- 2 GB: production with Symfony Messenger and one Redis transport
- 4 GB: multiple workers, Redis, high-frequency sessions

Ports to open: 80 (HTTP), 443 (HTTPS), 22 (SSH). Close everything else.

Create /etc/nginx/sites-available/symfony-app with this minimal server block, then enable it with a symlink to sites-enabled/.

server {
    listen 80;
    server_name your-domain.com;
    root /var/www/symfony-app/current/public;
    index index.php;

    location / {
        try_files $uri /index.php$is_args$args;
    }

    location ~ \.php$ {
        fastcgi_pass unix:/run/php/php8.3-fpm.sock;
        fastcgi_split_path_info ^(.+\.php)(/.*)$;
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
        fastcgi_param DOCUMENT_ROOT $realpath_root;
    }

    location ~ /\.ht {
        deny all;
    }
}

Enable the site and test before reloading nginx:
ln -s /etc/nginx/sites-available/symfony-app /etc/nginx/sites-enabled/ && nginx -t && systemctl reload nginx

For HTTPS, use Certbot: certbot --nginx -d your-domain.com.

Symfony reads .env, then .env.local, then .env.prod.local. In production, all sensitive values must be in .env.local — never committed to git.

Essential production variables:

APP_ENV=prod
APP_DEBUG=false
APP_SECRET=<64-chars-hex-random>
DATABASE_URL="mysql://dbuser:[email protected]:3306/symfony_prod"
MAILER_DSN=smtp://user:[email protected]:587
MESSENGER_TRANSPORT_DSN=redis://127.0.0.1:6379/messages

Generate APP_SECRET randomly: openssl rand -hex 32. Never reuse the project's default value.

APP_DEBUG=false is critical: in debug mode, Symfony exposes full stack traces, template variables and SQL queries in the browser — a severe information leak in production.

Symfony Messenger defers heavy tasks (email sending, PDF generation, webhooks) to a queue processed asynchronously. On a VPS, Supervisor ensures the worker runs continuously and restarts after a crash.

Install Supervisor:
apt install -y supervisor

Create /etc/supervisor/conf.d/symfony-messenger.conf:

[program:symfony-messenger]
command=/var/www/symfony-app/current/bin/console messenger:consume async --time-limit=3600
user=deploy
autostart=true
autorestart=true
startretries=3
redirect_stderr=true
stdout_logfile=/var/log/supervisor/symfony-messenger.log

Activate and start the worker:
supervisorctl reread && supervisorctl update && supervisorctl start symfony-messenger

Monitor status: supervisorctl status symfony-messenger

1. The environment variable "APP_SECRET" is not set.
APP_SECRET is missing from .env.local on the server. Check that the file exists in {{deploy_path}}/shared/ and contains this variable. Deployer creates a symlink to this shared file for each release — if the symlink is broken, Symfony won't read .env.local.

2. Silent 500 error — empty logs
With APP_DEBUG=false, Symfony shows nothing in the browser and writes to var/log/prod.log. Read this file in real time: tail -f /var/www/symfony-app/current/var/log/prod.log. A permission denied error on var/cache/ or var/log/ is the most common cause — fix with chown -R deploy:www-data var/.

3. Connection refused on the database
DATABASE_URL points to 127.0.0.1 but MySQL listens on localhost (Unix socket) — or vice versa. Test directly: mysql -u dbuser -p -h 127.0.0.1 symfony_db.

4. There are no commands defined in the "cache" namespace
This misleading message often means Symfony can't write to var/cache/. Fix: chmod -R 775 var/cache var/log && chown -R deploy:www-data var/.

If you prefer to skip hours of manual configuration, the symfony-stack template in the ServOrbit Marketplace automatically installs and configures the entire stack described in this guide: PHP 8.3-FPM, Composer, Symfony-optimized nginx, Redis, Supervisor and correct permissions. The VPS is ready in under 5 minutes, with immediate root SSH access to customize your deployment.

The template also configures essential environment variables through a guided form at order time — randomly generated APP_SECRET, DATABASE_URL pre-filled with MySQL credentials created for your instance.

You keep full control: the VPS is yours, there's no lock-in, and you can use Deployer PHP exactly as described above from your first SSH connection.