Server Version#: 1.13.8.5395
Player Version#: -
Another one of these. I’ve recently set up a docker with Plex Server. Upon enabling Remote Access, I get a green status for a couple seconds, then a little later it goes back to red. To add to the confusion, I disabled ethernet and got Wi-Fi working for a minute or so, then it went back to Red.
I’ve had Plex running on another computer before (not-dockered) and it ran fine. Port forwarding seems ok.
(I did not manage to get the recommended docker setup when running)
I’m not sure where to go from here. I’m willing to restart my setup with the recommended docker setup, get logs, etc, if someone is willing to take the time to help me through this.
I hate to hear it for you, but I’m happy I’m not the only one!
I have torn apart my network thinking something mysteriously changed. Restarted the modem, router, server. I recreated the Port Forward rule on my router. Downloaded a fresh Plex Server app, put it in place. Still seeing the problem. Installed plex server on windows bootcamp partition on a MBP. It connects with manual port forward without issue. So, it isn’t my network. I start digging through the Plex logs and find that one log entry it calls out with the proper ip address, port number, and user. Then there is another log entry that has my ip address as an empty string value. It later warns that async identifiers do not match. This is the only thing that I can see wrong thus far. I’m not sure what started causing the problem as I haven’t made any changes recently.
I’m running:
OS X El Capitan (on a Dual Xeon Mac Pro)
Plex Server 1.13.8.5395
One thing I’ve noticed besides, is that my logs are marked one hour behind. I’m not entirely sure if the logs are not applying the daylight saving time, or if the time is indeed incorrect. From previous experience, the wrong clock can wreak havoc with…anything, really.
When you are running in docker and not using host networking (host networking is only really viable on linux hosts), you are essentially behind a double-NAT (one is your router and the second is docker). The automatic port forwarding mechanisms don’t work in the double-NAT scenario. If you manually setup port forwarding on your router to the host and it has the manual port forwarding setup (which you do in your docker run statement) then it should work much better. This does require that your computer not change IP address in your home network or at least if it does that you change the router’s port forwarding to match the change.
I did set up port forwarding manually, pointing to my host IP (it doesn’t change). That was actually the first thing I did, but it did not seem to do much. I might be missing something, though I’m not sure how to troubleshoot it to make sure it’s a port forwarding issue, or something else.
Would my next step be capturing my connections for the specific port?
I am now seeing 502 and 504 responses now. That definitely would cause connectivity issues. (DEBUG - HTTP 504 response from GET https://plex.tv/media/providers?X-Plex-Token=<…blah, blah, wouldn’t you like to know>)
Quick update:
After roughly 24hours, my Plex Server is still accessible remotely. I even remoted in during lunch to watch for a bit. Everything seems to have gone well for now.
Seems like my initial statement “Port forwarding seems ok” was actually incorrect
Nothing to do with static IPS. It’s what I mentioned, I had an incorrect port forwarding. To further elaborate:
I had set it up as any external connection coming through (regardless of IP), would need to use port 32400, and those would be linked with my internal port 32400. What I actually needed to set up, was that any external connection - regardless of IP OR port - requesting a connection to port 32400, would be directed to my internal IP running PMS, also at port 32400.
Essentially my set up was ANYIP:32400 => MYINTERNALIP:32400
and I changed it to:
ANYIP:ANYPORT => MYINTERNALIP:32400
Regarding IPs, I do have to make sure that my internal IP does not change, but my router already actually does that by default, impressively. So that required no messing around.
Are you by any chance using both Wired and Wi-Fi connections. I remember once upon a time having troubles by having both toggled. It would behave like you mention. It was mostly due to an unstable wired connection (and not having a fixed local IP on my machine)
