It seems like the server is caching the xml without the remote info. when I look at the /api/resources end point, my server does not acknowledge that there’s a remote connection.
However, I can put the external IP and port of my plex server into my browser, and reach it no problem.
Is there some way to force the resources xml to propagate?
Don’t look any further guys, this is a Plex ■■■■-up. I’ve managed to reinstate direct connections for web/browser based clients, but their API handles things differently so all apps who rely on this have stopped working. It’s one thing to ■■■■-up (we all do once in a while), but not informing your customers about it is just bad business.
I am working with operations now…
May I have your Log files please ? (Settings - Server - Help - Download Logs)
I’m doing the best I can. So far, I’ve eliminated 30 user-rooted problems while chasing this issue. Please be patient with me?
Logs attached.
Edit: FYI it’s an unRAID docker installation.
@ewellinger said:
I tried downgrading to1.10.0.4523and it didn’t fix the issue. Seems like A LOT of people are running into this issue (see this, this, and this)
Why has there not been an announcement about this yet??(Although to be fair I’m not entirely sure this is the same issue)
Sorry, I’m actually on FreeBSD not CentOS
@ChuckPA said:
I’m doing the best I can. So far, I’ve eliminated 30 user-rooted problems while chasing this issue. Please be patient with me?
No worries @ChuckPA. Diagnosing something like this can be super tricky, it’s just frustrating as hell when the status page says everything is fine and you spend multiple hours trying to diagnose what’s happening.
@csaaam said:
@wirestyle22 said:
I rolled my server back to version 1.9.7.4460 and that fixed it. Everyone I know had the same issue I did. They are all CentOS 7 and Fedora though.here’s the link to that version: https://downloads.plex.tv/plex-media-server/1.9.7.4460-a39b25852/plexmediaserver-1.9.7.4460-a39b25852.x86_64.rpm
Does not work for me, I also downgraded but the problem remains, frustrating as hell
This is going to sound stupid but when i rolled it back I had to go back to http://ip address:32400/web/index.html and setup the directories / scan the media. Did you do that?
Thanks for letting me know it includes BSD. Now it’s not OS specific. Good info.
Can you recreate the error (remote access enable error) and grab the log files?
ANY information is helpful
@wirestyle22 said:
@csaaam said:
@wirestyle22 said:
I rolled my server back to version 1.9.7.4460 and that fixed it. Everyone I know had the same issue I did. They are all CentOS 7 and Fedora though.here’s the link to that version: https://downloads.plex.tv/plex-media-server/1.9.7.4460-a39b25852/plexmediaserver-1.9.7.4460-a39b25852.x86_64.rpm
Does not work for me, I also downgraded but the problem remains, frustrating as hell
This is going to sound stupid but when i rolled it back I had to go back to http://:32400/web/index.html and setup the directories / scan the media. Did you do that?
Since this thread is in the public area, May I ask for your help in sorting / identifying the OS being referred to?
Rolling back shouldn’t require a full setup if on Linux
Logs attached, on Windows 10
@ChuckPA said:
@wirestyle22 said:
@csaaam said:
@wirestyle22 said:
I rolled my server back to version 1.9.7.4460 and that fixed it. Everyone I know had the same issue I did. They are all CentOS 7 and Fedora though.here’s the link to that version: https://downloads.plex.tv/plex-media-server/1.9.7.4460-a39b25852/plexmediaserver-1.9.7.4460-a39b25852.x86_64.rpm
Does not work for me, I also downgraded but the problem remains, frustrating as hell
This is going to sound stupid but when i rolled it back I had to go back to http://:32400/web/index.html and setup the directories / scan the media. Did you do that?
Since this thread is in the public area, May I ask for your help in sorting / identifying the OS being referred to?
Rolling back shouldn’t require a full setup if on Linux
I am personally using CentOS 7. I went to rollback and yum was yelling at me, so I uninstalled the latest version and then installed version 1.9.7.4460. So not a true rollback. Probably should’ve clarified that. My bad.
I also know Fedora 26 and 27 also have the same issue.
@twilliams69 said:
Logs attached.
Edit: FYI it’s an unRAID docker installation.
unRAID and docker make this REALLY tough.
I do not see any connection attempts to PubSub (the my-plex connector). Can you recreate and grab fresh logs (the playback activity must have rolled over too soon)
@ChuckPA said:
@ewellingerThanks for letting me know it includes BSD. Now it’s not OS specific. Good info.
Can you recreate the error (remote access enable error) and grab the log files?
ANY information is helpful
I actually am now seeing the server show up when looking remotely with my iphone, so the problem might be solved? I’m going to keep an eye on it though and if I see it come up again I’ll get a log dump.
@wirestyle22 said:
@ChuckPA said:
@wirestyle22 said:
@csaaam said:
@wirestyle22 said:
I rolled my server back to version 1.9.7.4460 and that fixed it. Everyone I know had the same issue I did. They are all CentOS 7 and Fedora though.here’s the link to that version: https://downloads.plex.tv/plex-media-server/1.9.7.4460-a39b25852/plexmediaserver-1.9.7.4460-a39b25852.x86_64.rpm
Does not work for me, I also downgraded but the problem remains, frustrating as hell
This is going to sound stupid but when i rolled it back I had to go back to http://:32400/web/index.html and setup the directories / scan the media. Did you do that?
Since this thread is in the public area, May I ask for your help in sorting / identifying the OS being referred to?
Rolling back shouldn’t require a full setup if on Linux
I am personally using CentOS 7. I went to rollback and yum was yelling at me, so I uninstalled the latest version and then installed version 1.9.7.4460. So not a true rollback. Probably should’ve clarified that. My bad.
I also know Fedora 26 and 27 also have the same issue.
“Rolling back” on Redhat is a rpm -e and then install the package again. NO need to remove your metadata in /var/lib/plexmediaserver
@ewellinger said:
@ChuckPA said:
@ewellingerThanks for letting me know it includes BSD. Now it’s not OS specific. Good info.
Can you recreate the error (remote access enable error) and grab the log files?
ANY information is helpful
I actually am now seeing the server show up when looking remotely with my iphone, so the problem might be solved? I’m going to keep an eye on it though and if I see it come up again I’ll get a log dump.
Nothing happened yet at plex.tv. They are waiting for us 
Fresh logs.
Last activity is a quick play from app.plex.tv and server stills says Indirect.
This is an unRAID docker install.
Synology 918+ DSM 6.1.4-15217 Update 5
Plex Media Server 1.11.0.4633
I’ve tested it on multiple operating systems (Windows 10, CentOS 7 and FreeBSD 11) and all behave the same, so it’s most definitely NOT an OS issue. All is fine (locally) as long as you don’t need to query Plex.tv for remote server lookups.
@boolean said:
I’ve tested it on multiple operating systems (Windows 10, CentOS 7 and FreeBSD 11) and all behave the same, so it’s most definitely NOT an OS issue. All is fine (locally) as long as you don’t need to query Plex.tv for remote server lookups.
Yes that is the case. The relay does work, but you can’t directly connect.
