Unix socket issue since v5 upgrade

Bugs
1

Issue Summary
Before upgrading my production site to v5, I’m trying to upgrade a low-traffic personal site. The upgrade seemed to complete successfully but now my site is inaccessible and I’m getting 502 Bad Gateway errors from nginx. There’s nothing in the Ghost error log and running systemctl status shows Ghost as ‘Active (running)’.

I have Ghost set to use a Unix socket in my config.production.json:

    "socket": {
      "path": "/tmp/ghost.sock",
      "permissions": "0666"
    }
  },

But there’s no ghost.sock in the /tmp directory. Do I have to change these settings in v5?

Setup information

Ghost Version
v5.0.1

Node.js Version
v16.15.0

How did you install Ghost?
DigitalOcean 1-click app, upgrade to v5 via ssh and ghost upgrade

2

I think socket support was removed as a breaking change:

3

Oh, damn. Okay, I don’t feel too bad about missing that, since it took me a while to find it even after you pointed out it was in there!

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.