Cant connect my server to my plex account

Server Version#: NAS DS218+ DSM 7.0.1-42218
Player Version#: 1.25.2.5319-7000

Hello guys

Today i had the problem that my plex server said that i dont have permissions for my medias with my account (movies, series, animes, etc.). It was weird because with another account i could watch my media. After some researching i didnt found a solution for my problem so i decided to reinstall my plex. I first deleted my plex server on my nas. than i downloaded the DSM7 for Intel 64-bit and installed it. After going on http://192.168.1.147:32400 i configured the server as usual. But already there i saw a red message with a message like “couldnt connect to server”, but i could finish the configuration. After setting up all my media i saw that i cant watch it because theres a message (picture 1). It says; “Server NAS-Alessio is not logged into a Plex account and is therefore not secured”, when i click on the yellow button im getting to the settings to connect my server with my plex account. When i click the button “connect server” (on German “Server verbinden”) nothing happens. What can i do, so i can watch my series again? Theres also a Update for the server but i just installed the newest version?

Can someone help me?

Greetings

@BallLP

Is your computer on the 192.168.1.x subnet with your NAS?

Can you show me this picture?

Also, Can you (use FileStation) go to the PlexMediaServer shared folder,

  • navigate into AppData/Plex Media Server,
  • Right-Click “Logs”
  • Compress to Logs.zip
  • Download that file
  • Attach here for me to see what’s wrong

Hey ChuckPa

Sorry i was the entire week sick and i hadnt the power to do something.

Sorry i totally forgot the picture, there you go (i hope it worked):


And like you wish there are all the logs:
Logs.zip (870.7 KB)

Greetings

Thanks for the logs.

  1. DNS is failing (CURL ERROR 6)
  2. You are showing two different subnets (192.168.0.x and 192.168.1.x). Which one is your default gateway on? (Synology: Control Panel - Network - Interfaces )
Jan 06, 2022 04:48:15.613 [0x7ff08bfefb38] ERROR - SSDP: Error parsing device schema for http://192.168.0.254:49152/wps_device.xml
Jan 06, 2022 04:48:30.959 [0x7ff08be9fb38] DEBUG - HTTP requesting GET https://plex.tv/api/v2/features?X-Plex-Token=
Jan 06, 2022 04:48:35.964 [0x7ff08be9fb38] ERROR - Error issuing curl_easy_perform(handle): 6
Jan 06, 2022 04:48:35.964 [0x7ff08be9fb38] WARN - HTTP error requesting GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxe host name) (Could not resolve host: plex.tv)
Jan 06, 2022 04:48:35.964 [0x7ff08be9fb38] WARN - FeatureManager: Couldn't get features. Trying again soon.
Jan 06, 2022 04:48:47.623 [0x7ff08bfefb38] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.0.254:49153/wps_device.xml
Jan 06, 2022 04:48:47.624 [0x7ff08bfefb38] DEBUG - HTTP requesting GET http://192.168.0.254:49153/wps_device.xml
Jan 06, 2022 04:49:02.624 [0x7ff08bfefb38] ERROR - Error issuing curl_easy_perform(handle): 28
Jan 06, 2022 04:49:02.624 [0x7ff08bfefb38] DEBUG - HTTP simulating 408 after curl timeout
Jan 06, 2022 04:49:02.625 [0x7ff08bfefb38] ERROR - SSDP: Error parsing device schema for http://192.168.0.254:49153/wps_device.xml
Jan 06, 2022 04:49:32.739 [0x7ff08bfefb38] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.0.254:49153/wps_device.xml
Jan 06, 2022 04:49:32.739 [0x7ff08bfefb38] DEBUG - HTTP requesting GET http://192.168.0.254:49153/wps_device.xml
Jan 06, 2022 04:49:47.741 [0x7ff08bfefb38] ERROR - Error issuing curl_easy_perform(handle): 28
Jan 06, 2022 04:49:47.741 [0x7ff08bfefb38] DEBUG - HTTP simulating 408 after curl timeout
Jan 06, 2022 04:49:47.741 [0x7ff08bfefb38] ERROR - SSDP: Error parsing device schema for http://192.168.0.254:49153/wps_device.xml
Jan 06, 2022 04:49:47.742 [0x7ff08c653b38] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 23.732124 seconds: 192.168.1.126 (Philips hue (192.168.1.126))
Jan 06, 2022 04:49:47.742 [0x7ff08bfefb38] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.1.126:80/description.xml
Jan 06, 2022 04:49:47.742 [0x7ff08bfefb38] DEBUG - HTTP requesting GET http://192.168.1.126:80/description.xml
Jan 06, 2022 04:49:47.749 [0x7ff08bfefb38] DEBUG - HTTP/1.1 (0.0s) 200 response from GET http://192.168.1.126:80/description.xml
Jan 06, 2022 04:49:47.750 [0x7ff08bfefb38] DEBUG - NetworkServiceBrowser: found 1 SSDP devices via http://192.168.1.126:80/description.xml
Jan 06, 2022 04:49:47.750 [0x7ff08bfefb38] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.1.126 (Philips hue (192.168.1.126))
Jan 06, 2022 04:50:17.795 [0x7ff08bfefb38] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.0.254:49153/wps_device.xml
Jan 06, 2022 04:50:17.795 [0x7ff08bfefb38] DEBUG - HTTP requesting GET http://192.168.0.254:49153/wps_device.xml
Jan 06, 2022 04:50:32.796 [0x7ff08bfefb38] ERROR - Error issuing curl_easy_perform(handle): 28
Jan 06, 2022 04:50:32.796 [0x7ff08bfefb38] DEBUG - HTTP simulating 408 after curl timeout

what Plex sees is:

Jan 01, 2022 19:55:34.253 [0x7ff0905726e8] DEBUG - Detected primary interface: 192.168.1.147
Jan 01, 2022 19:55:34.253 [0x7ff0905726e8] DEBUG - Network interfaces:
Jan 01, 2022 19:55:34.253 [0x7ff0905726e8] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
Jan 01, 2022 19:55:34.253 [0x7ff0905726e8] DEBUG -  * 5 ovs_eth0 (192.168.1.147) (loopback: 0)
Jan 01, 2022 19:55:34.253 [0x7ff0905726e8] DEBUG -  * 6 docker0 (172.17.0.1) (loopback: 0)
Jan 01, 2022 19:55:34.253 [0x7ff0905726e8] DEBUG -  * 1 lo (::1) (loopback: 1)
Jan 01, 2022 19:55:34.253 [0x7ff0905726e8] DEBUG -  * 5 ovs_eth0 (fe80::211:32ff:feb8:afc7%ovs_eth0) (loopback: 0)
Jan 01, 2022 19:55:34.253 [0x7ff0905726e8] DEBUG - Creating NetworkServices singleton.
Jan 01, 2022 19:55:34.253 [0x7ff0905726e8] DEBUG - NetworkServices: Initializing...

Hey

My Default Gateway is on 192.168.1.1. That should be correct.

What is the DNS address in the Syno?

Is it pointing to 192.168.1.1 (or whatever address your modem/router is) ?

It was on “Automatic”. But now i changed it to manual and changed it to 192.168.1.1 and IT WORKEDDDDD! Yuuuhuuu

Thank you for your awesome help, ChuckPa!!

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