My joplin cloud server has 502 error report

I use my Oracle service to self-built the Joplin cloud, and my 22300 port and 5432 port have still listened to and docker-compose successfully runs but I cannot log into the Joplin UI image through the use of my domain name which shows 502 bad gateway, can you help me?

@cengzhijie3 welcome to the forum.

If the Joplin server is up and running without error then the 502 Bad Gateway suggests that there may be something wrong with your reverse proxy config.

I don't think so is that I listening to port 22300 which automatically changes but the 5432 port still fixes. I use the Nginx proxy managed to server proxy.

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