I changed the url of my blog with ghost config url XXX and got: Successfully set 'url' to 'XXX' + sudo systemctl is-active ghost_YYY Ghost is running. Don't forget to run ghost restart to reload the config! So I ran ghost restart. It hung for a few minutes and then I got + sudo systemctl is-activ…

Ah—after restarting nginx (sudo systemctl restart nginx), success! No more 502s. What a relief. This mysterious port change sure does look like a Ghost issue…

Ghost restart "Could not communicate with Ghost"

Developer help

loophole June 15, 2023, 6:21pm 2

journalctl -u ghost_YYY -n 50 says no entries.

Might be a dupe of 5.44.0 Could Not Communicate with ghost - #4 by TeslaCuil

Topic		Replies	Views
502Bad Gateway Error after restarting Ghost Developer help	1	257	November 25, 2023
502 Bad Gateway after Ghost restart Self-hosting	2	484	February 19, 2022
Suddenly Unable to Completely Start Ghost After Server Restart Developer help	3	2104	February 11, 2019
Ghost is not running after update Self-hosting	2	586	March 28, 2023
502 bad gateway after last update Developer help	10	2082	February 11, 2021

Ghost restart "Could not communicate with Ghost"

Related topics