Troubleshooting

Common problems and how to fix them.

The panel shows 404 or 'Permission denied' after an update

Version 0.2.0-beta.2 reset /opt/laravelify to a mode nginx cannot read. Fix it once, then update again:

sudo chmod 755 /opt/laravelify

Releases from 0.2.0-beta.3 keep the permissions.

A Nuxt or SvelteKit site fails with 'module is not defined in ES module scope'

The PM2 file was named ecosystem.config.js, which breaks in projects with "type": "module". Update to 0.2.0-beta.5 or later: the file is now ecosystem.config.cjs, and old files are renamed on the next update.

Next.js: next build did not create .next/standalone/server.js

Add output: "standalone" to your next.config and deploy again.

SvelteKit: Could not detect a supported production environment

Install @sveltejs/adapter-node and use it in your SvelteKit config instead of adapter-auto.

The installer stops at 'repo.packagist.org could not be fully loaded'

A warning, not an error: Composer could not reach Packagist and used its cache. If the install stops there, the server usually cannot reach IPv6 addresses. Prefer IPv4 and run the installer again:

sudo bash -c 'grep -q "^precedence ::ffff:0:0/96" /etc/gai.conf || echo "precedence ::ffff:0:0/96  100" >> /etc/gai.conf'

The panel or a site shows a Cloudflare 502 or 1033 error

The tunnel is not connected or the public hostname is missing.

sudo systemctl status cloudflared 'laravelify-tunnel-*'

In Cloudflare, check the tunnel is Healthy and the hostname points to http://localhost:80.

A deploy fails at git fetch with 'Authentication failed'

The GitHub App is not installed on that repository, or the personal token expired or lacks Contents: read. Open Sources, check the repository is listed, then deploy again.

A deploy stays 'queued'

The queue worker is not running:

sudo supervisorctl status laravelify-queue
sudo supervisorctl restart laravelify-queue

Monitoring shows no requests

Click Turn on tracking on the website’s Monitoring tab, then visit the site. If it still shows nothing, check the scheduler runs (sudo supervisorctl status laravelify-scheduler) and that /var/log/laravelify/{slug}.metrics.log grows when you visit the site.

Next.js: 'Script not found: .next/standalone/server.js'

Add output: 'standalone' to next.config and deploy again. Before the first successful build there is nothing for PM2 to start; that is expected.

Next.js sites are down after the server restarts

PM2 restores apps on boot through the pm2-root service. Set it up (and move any apps started by older versions into root’s PM2) with:

sudo bash /opt/laravelify/scripts/host-apply.sh pm2-boot all

systemctl status pm2-root should then show it enabled. Updating the panel runs this for you.

Laravel uses old .env values

A cached config ignores .env. Saving the Environment tab clears it; from the terminal run php artisan config:clear.

I lost my authenticator

See Reset two-factor from the server.

Where to look

Log	Path
Panel	/opt/laravelify/storage/logs/laravel.log
Deploy queue	/opt/laravelify/storage/logs/panel-queue.log
Scheduler	/opt/laravelify/storage/logs/panel-scheduler.log
A site’s nginx	/var/log/nginx/laravelify-{slug}.error.log

Still stuck? Open an issue with the error message and these logs (remove secrets first).