Nginx - 502 Bad Gateway

Get Help
1

Dear,

I don´t understand, because first i have a smooth running 1.8.7 version, however after display-registering it becomes “502 Bad Gateway” (nginx) only after container-reboot.
Since few days i try to find the failure.

Synology DSM 6.1.6 /Docker, Xibo 1.8.7, mysql 5.6, phpMyAdmin 4.6

I´m very happy about some helpful advices.
Many thanks from Germany. Sten

2

Does that mean after you register a display you can no longer access CMS at all?
or is it showing that error on a particular page?

Are you using custom or standard ports for your docker containers?
Is there proxy in place and if so what is it configured?

3

Hi Peter, thank you for reply.

I mean, after autmated display-registering by system. After them, CMS-Login becomes “502 …” without any changing by myself. Before the CMS was running smooth. Meanwhile i testing with a brandnew installation.
Hm…

The docker containers have standard ports
CMS (8888:80 and 8080:8080)
DB (32773:3306)
XMR (50001:50001 and 9505:9505)
phpMyAdmin (8081:80)

The Proxys:

  1. Signage over HTTPS (signage.synology.me) 443 to localhost 8888
  2. Local over HTTP (signagetv) 80 to localhost 8080
  3. Local over HTTPS (siganetv) 443 to localhost 8081

/1) for public access

Is that correct?
Sten