Siddharth Singh on Nostr: Just confirming, but is Ditto itself running? That's what a 502 Bad Gateway typically ...

Just confirming, but is Ditto itself running? That's what a 502 Bad Gateway typically indicates, that the service being proxied to isn't active, and your triage list didn't actually mention that. Please don't mistake me, just eliminating the obvious.

Next up, if you have some sort of firewall set up it may be blocking nginx's ability to communicate with Ditto.

Also, if you've configured ditto to listen on a different port other than 4036, please check that your nginx config is updated to reflect that.

There have been some issues with nginx configs in the past but as of latest ditto, nothing. Could you also confirm if you're on latest `main`?