User: “I’m trying to log in to my Ghost admin panel (/ghost), but after entering my credentials, the button spins and eventually shows a red banner at the top saying: ‘There was a problem on the server.’ I haven’t changed any settings recently. Is this a database issue or a bug in the latest version?”

This error is a generic “catch-all” message, but in 90% of self-hosted Ghost installations, it is caused by one of three things: Broken Mail Configuration, Nginx Proxy Timeouts, or Database Connection Issues.

1. The Primary Culprit: Device Verification (SMTP)

Ghost recently introduced a “Staff Device Verification” feature. If you log in from a new IP or browser, Ghost tries to send a verification email. If your SMTP/Mail settings are not configured correctly, the request will hang and eventually fail with a server error.

How to fix it: If you don’t need email right now and just want to get back into your dashboard, you can disable this check via your config file:

Open your config.production.json file.

Add or update the following security block:
/var/www/ghost/config.production.json

"security": {
  "staffDeviceVerification": false
}

Restart Ghost: ghost restart.

2. Nginx Proxy Issues

If you are using Nginx as a reverse proxy, it might be timing out before Ghost can process the login request (especially if the server is trying and failing to send that email mentioned above).

How to fix it: Ensure your Nginx configuration includes the correct headers to pass the original request info to Ghost:

Nginx

location / {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header Host $host;
    proxy_pass http://127.0.0.1:2368;
}

3. Check the “Real” Error in Logs

Because “There was a problem on the server” is vague, you should look at the actual error log to see the specific code (like ECONNREFUSED or Access denied for user).

Run this command in your Ghost directory:

ghost log

If you see EmailError: Your mail server settings (Mailgun/SMTP) are wrong.

If you see 504 Gateway Timeout: Nginx is losing connection to Ghost.

If you see InternalServerError: Usually related to a database crash or a full disk.

Summary Checklist

Disk Space: Check if your server is out of space (df -h). Ghost can’t create session files if the disk is 100% full.

Permissions: Ensure the ghost user owns the files: sudo chown -R ghost:ghost /var/www/ghost.

Node Version: Ensure you are using a supported version of Node.js.