502 bad gateway after last update

In the error above, the port that the connection was trying to be established on was :2368 but doing a netstat -plant I saw that the correct port was :2369

I don’t know what caused this change, as it was working just fine before I had updated ghost. Apparently, the update changed some of my ports in the nginx configurations for my website -> /etc/nginx/sites-enabled/kurazav.com-ssl.conf & /kurazav.com.conf) had the ports set to :2368 instead of :2369

1 Like