Port forwarding is done in the modem/router (the actual edge device between your ISP and your machine). It is the one piece of equipment that touches both worlds which is what makes it the right place to decide what gets forwarded and what gets rejected.
@ChuckPa Thanks for the clarification. That helps. I don’t want to cause any confusion between Synology and my router.
@trumpy81 Ok, I did all the following.
- Reboot NAS
- Disabled Synology Firewall
- Verified that Gateway and DNS server are the same under Network Settings
- Reboot Modem & Router
- Verified that Port Forwarding is disabled on router
- Signed out of Plex Server
- Shut down Plex Server
- Signed out of
plex.tv - Renamed Preference file
- Restarted Plex Server
- Opened up Plex Server
It now stalls at http://[server_ip]:32400/web/index.html#!/setup/[hash] and displays a perpetual spinning circle. Here are the logs I could access from compressing the Logs folder from the FileStation.
Plex_2021-08-28_12-47_Logs.zip (3.9 MB)
Are there independent tests I can to do to verify that my Synology can access the internet? I think it can so I’m confused as to the network issues against the Plex servers. Is there a plex server domain I can explicitly ping?
the simplest way I know is canyouseeme.org and check what it finds.
It attempts to open the connection and reports back.
So I just redid a factory reset of my router as I was experiencing some issues. I was hoping it might resolve my Plex issues but it hasn’t. My server still cannot communicate with the plex.tv servers. I’ve disabled the synology firewall and turned off dos protection, but still no such luck. Can you think of anything else I can try?
Does it matter that I’m not signing in as the default admin user? I disabled it for security reasons, but I sign in as a different user with admin rights, and I think have all the right groups and permissions set.
Well here are my most recent logs. I’m using DSM 6.
Plex Media Server Logs_2021-09-03_18-17-24.zip (5.5 MB)
My NAS user has the exact same admin privileges as the default user, I think. When I look at the user settings, it’s in the administrators user group and it has Read/Write permission for every folder in the FileStation, including the Plex folder. How can I check if that user is the admin user for the Plex application?
I was waiting to upgrade to DSM 7 until I resolved this problem. It doesn’t sound like there’s a guarantee that upgrading would fix it. How do I upgrade? When I go to the Update & Restore screen, there isn’t an option for updating to DSM 7. I have a Synology DS412+.
These look like the same instructions from earlier in this post, correct? I’ve tried these and they don’t work. But here are new logs from another attempt. Plex Media Server Logs_2021-09-05_10-41-44.zip (5.8 MB)
If there is an issue with my Synology connecting to the plex.tv servers, then I’d like to figure out what the underlying cause is. If it’s a firewall issue, what explicit settings do I need to change? If it’s a router issue, what settings need to change? If it’s a user/group issue what settings do I need to change? Does Plex IT support have a ticket system that is tracking my issue, the logs, and what I’ve tried already?
Hmm, that’s unfortunate regarding DSM 7.
I understand that my Synology is my responsibility, but this is why it’s so confusing for me. I haven’t changed my Synology or network settings, and this used to work fine back in the spring. I have the same Synology, same router, same ISP. The only difference between the spring and now is that I moved addresses. As far as I know, I haven’t changed any settings. Plex Media Server used to work fine back around version 1.16, 1.18, etc. Starting around 1.21 or 1.22 I noticed I had more problems where I’d lose access to my Plex Server and need to reclaim it, but I always managed to do so following the earlier instructions you posted. But ever since I moved, I’ve lost complete ability to reclaim the server, and those instructions no longer work.
Yeah my Synology firewall is disabled. I’m at a loss as to why my Synology can communicate with other servers on the internet, but not plex.tv.
I appreciate any help y’all can give and I do understand that my network is my responsibility. I asked about the ticket support etc, because I’ve noticed on these forums that other people have experienced the same thing. So I wondered if maybe through that collective problem-solving, looking at all the server logs etc, and solving other people’s issues, if the Plex team have been able to categorize the types of underlying problems that can result in what I’ve been experiencing.
Could it be a case that Plex Media Server 1.21 and up started dropping support for the older Synology models like mine, DS412+, and at some point it got phased out? Is there a master list somewhere of versions of Plex Media Server and which Synology NAS are officially supported with each version?
Hey! been a while since we chatted. 
I’m looking at your logs. You definitely have some network issues getting from the Syno → Internet → Plex.tv
This is stopping everything from working.
Sep 03, 2021 18:11:52.946 [0x7f2841d8bb38] ERROR - Error issuing curl_easy_perform(handle): 7
Sep 03, 2021 18:11:52.946 [0x7f2841d8bb38] WARN - HTTP error requesting GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxt to server) (Failed to connect to plex.tv port 443: Host is unreachable)
In the Syno. Control Panel - Network - Interfaces - eth0 -
- What IP address does it have for default gateway and DNS?
- Does it look like mine where the DNS and gateway point to the modem/router ? (except using your LAN addresses)
- Lastly is eth0 the default gateway adapter?
- Show me please if not?
@trumpy81 thanks for your response. I’ve checked all the cables, and re-seated everything. I don’t think my router has any DNS Rebinding protection. I couldn’t find any references to that.
@ChuckPa Yes. In my router I gave the Synology a manually set IP in the DHCP list. Under Network - Network Interface Lan 1, I have the following:
- Gateway and DNS: 192.168.50.1 (verified router LAN IP set to this)
- IP address: 192.168.50.3 (same as it’s manually set in the router)
- LAN 1 is set to default gateway adapter. Is LAN1 the same as eth0?
Here are new logs. Plex Media Server Logs_2021-09-05_18-00-24.zip (5.1 MB)
-
eth0 = LAN 1 (eth1 = LAN 2) – That’s how Linux numbering works
-
I agree with Trumpy, set the DNS manually next. We’ve seen a few cases in the past week were DNS was blocking PMS from working correctly.
-
Do you use a Certificate on the Synology ?
Please confirm the IP address of your computer (you’re using to claim it) and the IP of the Syno one more time please?
@havok2063
I was having the exact same issue today, tried everything in this thread, and finally changing the DNS in my synology to 8.8.8.8 let it claim instantly!
Good luck.
1 Like
@havok2063 and @ChuckPa I’ve been having this exact same issue with my Synology NAS
I tried ALL of the above solutions, as well (up to and including even manually changing the permissions on my synoproxy.conf file due to getting permissions errors when trying to run the manual Claim Code fix). All failed.
It wasn’t until I got to the bottom of this thread and read @Jedx 's comment about changing DNS to “8.8.8.8” that I was FINALLY able to get my issue resolved, as well. For those who may need it, the link below details how to update your DNS to 8.8.8.8
I also noticed after I ran this final fix that my Cloud Sync actually started working again, syncing files I hadn’t even realized it hadn’t been syncing. Not sure how long that “hadn’t” been occurring…but I suspect it’s been a couple to a few years 
@Jedx I’m curious, after getting everything to sync and work for you, did you go back and modify your DNS back to your local IP or keep them configured to 8.8.8.8?
This issue seems to stem from some type of Quickconnect and/or my DDNS configuration issue related to previous configuration setup through a users Synology Account. I know I had moved away from connecting to my Synology NAS remotely a while back and just let my DDNS config and all laps/expire.
@ChuckPa given those details, are there any additional insights that you may be able to provide into this issue and why exactly the “8.8.8.8” fix appears to be working for at least “some” of the impacted?
Yeah switching to a DNS of 8.8.8.8 helped with the issue I was having. I also had some Static Routes set for Plex in my Network settings accidentally set incorrectly. Once I fixed those and switched the DNS to the public one, I haven’t had any problems the Plex reaching the outside network. I did try switching back to my local IP for DNS for a while, but it didn’t seem to improve anything. So I switched back to 8.8.8.8.
This also fixed it for me! Damn DNS settings was from a previous network setup i had like 5 years ago!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
