Plex Bad Gateway

Hi, I may have broken something. I was doing a lot of restarts lately of my server and now my plex on docker is broken… I don’t know if restarts had something to do with it tho. It just started displaying “Bad Gateway” when I want to access the web UI.

If anyone can help me

Here are logs from docker:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.

[s6-init] ensuring user provided files have correct perms...exited 0.

[fix-attrs.d] applying ownership & permissions fixes...

[fix-attrs.d] done.

[cont-init.d] executing container initialization scripts...

[cont-init.d] 01-envfile: executing... 

[cont-init.d] 01-envfile: exited 0.

[cont-init.d] 10-adduser: executing... 

usermod: no changes


          _         ()

         | |  ___   _    __

         | | / __| | |  /  \

         | | \__ \ | | | () |

         |_| |___/ |_|  \__/

Brought to you by


To support LSIO projects visit:




User uid:    0

User gid:    0


[cont-init.d] 10-adduser: exited 0.

[cont-init.d] 40-chown-files: executing... 

[cont-init.d] 40-chown-files: exited 0.

[cont-init.d] 45-plex-claim: executing... 

[cont-init.d] 45-plex-claim: exited 0.

[cont-init.d] 50-gid-video: executing... 

[cont-init.d] 50-gid-video: exited 0.

[cont-init.d] 60-plex-update: executing... 

Atempting to upgrade to: 

failed: Connection timed out.

failed: Connection timed out.

failed: Cannot assign requested address.

failed: Cannot assign requested address.

failed: Connection timed out.

Could anyone help me fix it?

looks like a host nat issue with the container reaching the internet. also, we dont support or recommend running our containers with puid/pgid of root.

can you provide your compose and host os/version?

1 Like

Thanks for the reply. I checked my networking and found a really stupid fault there. My VPN provider apparently has this annoying feature to add his own internal DNS on top of others. And when I am not connected it basically means that every connection needs to wait for it to timeout and fall back to a secondary one. It appears that the container was closing the requests before DNS could properly switch.

It also meant that diagnosing this was hard as all other services had an internet connection…

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