For some reason, my server isn’t showing up in my account, even when I connect directly to my LAN IP Plex UI (192.168.0.110:32400) - I just see “looking for server” continue to spin.
I’ve gone through all the steps in https://support.plex.tv/articles/204604227-why-can-t-the-plex-app-find-or-connect-to-my-plex-media-server/
and nothing is connecting me. In the past, anytime I’m upgrading or somehow removed the server from the list (as I’ve done to remove my Nvidia Shield Plex server), the UI almost immediately picks up that there is an “unclaimed server” on my network and lets me reclaim it. This time, nothing. So to be clear, I have a running Plex server on my Synology, showing up and operating like normal within the Synology DSM, but not when I go to plex.tv or the LAN UI. Also I have turned off all my VPN connections on my entire home network.
edit: I should not have said ‘for some reason’ - this all began when I upgraded my Plex install on the Synology. And I just noticed that update came out yesterday. Is there a connection? A BUG?!?
I’ve done that several times. Also, your instructions aren’t 100% clear - when following the on-screen prompts, do I enter the IP address of PMS server as 192.168.0.110 or 192.168.0.110:32400 or http://192.168.0.12:32400/web or…?
I’ve tried just about every combo. This is getting exhausting!
Here’s the server logs, but I wonder if it’s getting them from the right server because it’s only connected at this point to my Shield server not my Synology server? Plex Media Server Logs_2019-02-26_22-21-54.zip (1.4 MB)
I’ve tried everything. And it doesn’t make sense if it’s a hardware or network settings issue because everything else is working properly. Including other networked packages on the synology itself, like HA-Bridge, a home automation server running inside a docker.
The backstory is that I recently replaced my ISP provided router with an Asus AC3500. The PPPoE settings were tricky since I’m on fiber, but once I got that worked out everything else was fine.
I set up my Nord VPN correctly on the router it as well, using openVPN, but I couldn’t get Plex to remote connect through the VPN even when I edited the openVPN config file to add trace routes for plex. I have since turned off all the VPN, including on the synology itself, and took out the nord VPN DNS server entries from the Asus router settings as well, basically just trying to say that I returned the Asus to full default settings. Is there something I must be missing? The only thing I can think of is that last thing you said, about updating my synology to Jun’s newer loader? I don’t want to blow it all up yet again to upgrade, but what about reinstalling Plex using the previous version? How else can I downgrade? Like I said at first, everything was working fine until I did the manual update.
I’m currently running v1.03b of Jun’s loader. Do I have to go through all the original steps to create a new USB? Or is it an easier process to update?
This is going from bad to worse. Now my XPenology seems to be bricked even though many on the forums reported no problems updating. But now I’m having a hard time wading through the thousands of forum pages to determine if I need a special version of Jun 1.04b for the DS3617xs DSM or if I can use the one from Jun’s synoboot-ds918.zip ? Basically, do I need to use the 918 .pat file or can I use the 3617xs .pat file when I re-do this whole thing?
So, use the DS918+ pat file even though my old install was 3617xs? Am I going to lose all my old data now? I don’t care about which model number as long as it works and I don’t lose all of my previous DSM.
I spent the whole day trying to get my Plex server back onto my account. I now have the Synology back up and running, I’ve disabled firewall on the router, I’ve uninstalled and reinstalled Plex v13, v14, v15, used the SSH method… everything. No dice. What next? Like I’ve said, everything else on this DSM as well as my entire network has full internet access without any problems. Should I just forget it and go back to just using it on the Shield? I’m not sure it has the horsepower that my Dell 780MT Xpenology has?
How obvious can it be if I have literally poured over every single setting on my router, on Synology…
How can you be sure it’s not Plex when everything else is working? I cannot get Plex server to run correctly (be claimed by my Plex acccount) on the Nvidia Shield now either. It’s like my entire Plex account is now hosed and unusable. Is there ANYTHING I might be missing on this particular router model? It’s the Asus RT-AC3500. I’ve tried running that claimpms.sh script SEVERAL times and always with the same result.
My bad, it’s an Asus RT-AC5300, not 3500. THIS beast: https://www.asus.com/us/Networking/RT-AC5300/
But I even tried putting the Synology IP on the DMZ so that it was completely exposed and it still couldn’t connect. I’ve added all the port forwarding… and the uPnP… I understand you saying that ‘no one else’ is having the same issue, but maybe that’s because this installer just came out 2 days ago? If it’s not Plex, then why is Plex the only thing that’s giving me hassles on networking?
I can revert everything over to my ISP provided router to test this whole thing, but wow.
So… new developments. On a whim, I opened the Plex Server app on my Mac Mini (I had removed that server from my account a while back when I switched it over to my Synology). Suddenly, that seemed to knock something loose in my account settings because from there it was able to see the Nvidia Shield (as well as the Mac Mini) as a server. Does this mean that I was right and it’s NOT the Asus router? Because the Shield, the Mac Mini, and the Synology are all on the same LAN (with the same WAN settings). AND, to make it even more odd, I didn’t even add the port forwarding to the router for the Mac Mini (although UPnP might have done it for me?)
So… does this tell us anything about the Synology version that just came out? Also it’s worth noting that I immediately refused the alert that was asking me to update the Mac Mini Plex Server app to 1.15, wondering if there’s a serious bug with this new version? I know that “no one else” is having these problems, but having worked with software devs before, this is precisely how bugs are discovered… from that ONE person who got it.
It IS adding up! Earlier you were thinking it was possibly due to the Asus router, and we’ve all but ruled that out because now two other servers are running correctly on my network. And yes, didn’t that latest plex version just come out? That’s what it says on the plex page. I wasn’t referring to the other ones. Also I know it is not the NIC because other services are running just fine on the synology. In fact, my nvidia shield Plex server is using the media folders on the synology as its library. (which reminds me of another question… Can two plex servers be using the same NAS folders as their libraries?)
Also running Version 1.15.1.710 and having similar issues
Can access everything locally but the server is telling me Not available outside your network.
No changes in any setup and was working fine before the update.
Tried to connect using the Samsung TV app last night…Unable to find server.
I can browse to the server on our externally NAT’d web address without any issues.
Regarding my situation - as a reminder, I now have Nvidia Shield and Mac Mini servers up and running, communicating with plex.tv, and claimed. Also remote access is working if I turn it on in their respective server settings. BUT my Plex Server running on my Synology is NOT able to be seen by Plex and when I try the claimpms.sh script, it gives an error that it can’t connect with plex.tv. Is there any reason I should try running Plex server as a docker? And/Or… since the other two servers are running on my LAN, doesn’t that mean there is some setting on the Synology that is messing up the networking? Is there a way to hit reset on Synology in regards to networking and ports, etc… but retain everything else I’ve already got set up like file sharing and docker?
I fixed it! It was indeed Plex, not any other aspect of my network or settings or hardware or Synology (that I know of, at least)… it was the preferences xml file. I know that in your FAQ it says to delete the Plex folder but that it’s optional if you want to keep your metadata, etc. So I left it there, hoping the re-install would rebuild the xml file. This time I zipped the original Plex prefs folder, then re-installed. Then took the xml file from the re-install after I claimed the server (in fact, because it was the same name as before, I don’t remember actually “reclaiming” it) - and used the fresh xml in place of my old xml after unzipping the original prefs folder. I stopped and started the Plex package each time I was making changes. Then finally I gave the plex user account privileges to the original media folder. And VOILA! Everything is back to the way it was. Thanks SO much for your help and FAQ!
Since this happened right after the update to 1.15, and I’m now back online with my original logs and prefs folders, do you want me to post my log?
Earlier you were thinking it was possibly due to the Asus router, and we’ve all but ruled that out because now two other servers are running correctly on my network. And yes, didn’t that latest plex version just come out? That’s what it says on the plex page. I wasn’t referring to the other ones. Also I know it is not the NIC because other services are running just fine on the synology. In fact, my nvidia shield Plex server is using the media folders on the synology as its library. (which reminds me of another question… Can two plex servers be using the same NAS folders as their libraries?)
