Plex unable to get public ip address from plex.tv

I Can confirm that its back up for remote users as well

:wine_glass: time :slight_smile:

1 Like

Mine is still down. And even more annoyingly I can’t even access it locally. It just says plex is down for maintenance. Surely access to my server locally (on localhost) shouldn’t depend on plex.tv.

All, please restart your PMS, and hopefully, should be fixed

1 Like

@nx6 @jackyaz

I cannot yet find what I have but did find similar here.

slaps self for being OFF-TOPIC :newspaper_roll:

1 Like

@ChuckPa I see some spending in my future…

1 Like

Thanks!

muahahahahahah :smiling_imp:

1 Like

Thanks! Oh, and my remote access is working again too!

To Ops, something something monitoring :stuck_out_tongue:

@ChuckPa …thanks for keeping us informed. I, like many others, was pulling out my hair wondering what the heck i must’ve done wrong.

Question…so although PMS appears to be back, I can only play ā€˜some’ content (smaller files) over the WAN … And the Remote access page is still reporting that Plex is ā€˜Not available outside your network’.

Any advice? (Running PMS via a container in Docker on a Synology NAS.

Thanks in advance. (Enjoy the wine time)

Have you restarted PMS since the partial outage ?

I say this because, PMS contacts Plex.tv each time it starts.

If it could not get its IP address (where the problem was),

Then Plex.tv would not have a valid IP address to give the clients to use when they want to start playback

Given you say ā€œsmaller filesā€, I am curious about this.

Might you have DEBUG logging enabled and can capture a failure of a normal file for me?

I don’t think smaller vs normal files is at all outage related

1 Like

Hey Chucks

Was just about to. Hoping that resolves the issue.

Cheers…

ChuckPa/ALL…

I got to the bottom of the issue.

I have a Synology DS918+ and recently had to move my WHOLE operation from a Mac Mini i’d been using which served me faithfully for 10 Plus years…

My searching, indexing, acquisition, organisation and monitoring…all moved to Synology under the DOCKER-Container system. A lot of learning and seeking advice…

Anyway…found out the reason behind the lack of WAN connectivity…it was the fact that despite having created the relevant port forwarding rule on my ASUS router for PLEX…I had to in like manner create an equivalent one as a firewall rule on the Synology effectively allowing port 32400 to pass … so in essence…that port needed opening/forwarding on BOTH the Router AND the Synology within it’s firewall rules.

Soon as i did that…BANG…FIRING on all cylinders and advertising to the world.

Hope this helps at least one person with a similar set up who may find themselves in this kind of situation…

Now i have to optimise the settings in Plex as the CPU load is super high…even with just two streams…

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