Server Version#: 1.24.5.5173-7000
DS918+
DSM 7.0-41890
I just updated to the newest PMS version and can’t connect via local IP. I followed other threads and am on the same subnet, also restarted router and NAS. Does my certificate need to be reset?
Thanks
What is the IP address of the server & of your computer?
Are you attempting to open it via a Quick Connect link in Package Center? (which doesn’t work for Plex anymore in DSM 7)
I did look at your account. The certificate was from August.
I took the liberty of resetting it just in case.
Please restart the server and try again before replying.
I restarted and am still getting the same message.
The NAS is at 192.168.1.27 and PC is 192.168.1.14
I cannot connect PMS directly through http://192.168.1.27:32400/web/
It will take about 15-20 seconds longer than normal to install while the installer and Plex.tv negotiate new credentials for your server based on that token. The installer will then update your server configuration (Preferences.xml) to use them.
PMS will start already having been claimed to your Plex account.
You should no longer have access issues.
Followed your steps, same issue persists.
Open File Station.
Navigate into the PlexMediaServer shared folder → AppData → Plex Media Server.
Right-click “Logs” → Compress to Logs.zip
Attach that file here please for me to review.
Logs.zip (415.3 KB)
Thank you for looking
PMS cannot lookup Plex.tv and get the IP address.
You have a network configuration error in the DNS configuration / resolver.
The normal configuration is to have the NAS point to the IP address of your modem/router provided by the ISP.
Oct 25, 2021 22:44:22.404 [0x7f942ce97b38] ERROR - Error issuing curl_easy_perform(handle): 6
Oct 25, 2021 22:44:22.404 [0x7f942ce97b38] WARN - HTTP error requesting GET https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxx (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
updated my plex server PR4100 to the newest update now i cant connect anymore. been dealing with this for a few months with the last 3 updates. when ever i do get my plex server working it randomly shuts down.
whats the point of having updates or a plex pass when these updates are taking our systems out. i would like to get a plex advisor to assist.
192.168.1.72 refused to connect.
ERR_CONNECTION_REFUSED
Check any cables and reboot any routers, modems, or other network devices you may be using.
If it is already listed as a program allowed to access the network, try removing it from the list and adding it again.
Plex Media Server
Version:
1.24.5.5173
Installed on:
Tuesday, 2021 October 26, 8:30:47 AM
Can you manually get into the Logs and make a ZIP file for me?
Is this on Synology or WD? You are in a Synology forum & thread but reference WD.
Plex Media Server Logs_2021-10-26_18-17-53.zip (3.5 MB)
sorry i was searching for help related to my problem. i have the WDPR4100
its working now but if you can check to see if i have any errors i would appreciate it.
Your logs show it took a bit to upgrade to 1.24.5 but is otherwise looking fine. It was optimizing the database for just over 2 minutes (a bug cleanup released in 1.24.5)
allowRetries=0'
Oct 26, 2021 08:32:46.588 [0x7ff127132b38] DEBUG - [JobRunner] Jobs: Starting child process with pid 15296
Oct 26, 2021 08:32:46.606 [0x7ff128208b38] DEBUG - Jobs: '/mnt/HD/HD_a2/Nas_Prog/plexmediaserver/binaries/CrashUploader' exit code for process 15296 is 0 (success)
Oct 26, 2021 08:34:02.863 [0x7ff12b8846e8] WARN - Held transaction for too long (../Library/FullTextSearch.cpp:58): 78.100000 seconds
Oct 26, 2021 08:34:13.714 [0x7ff12b8846e8] WARN - Held transaction for too long (../Library/FullTextSearch.cpp:71): 9.370000 seconds
Oct 26, 2021 08:34:37.262 [0x7ff12b8846e8] WARN - Held transaction for too long (../Library/FullTextSearch.cpp:81): 22.980000 seconds
Oct 26, 2021 08:34:44.591 [0x7ff1274c7b38] DEBUG - BPQ: [Starting] -> [Processing]
Oct 26, 2021 08:34:52.489 [0x7ff12b8846e8] WARN - Held transaction for too long (../Library/FullTextSearch.cpp:94): 14.870000 seconds
Oct 26, 2021 08:34:52.490 [0x7ff12b8846e8] WARN - Held transaction for too long (../Library/DatabaseMigrations.cpp:237): 126.420000 seconds
Oct 26, 2021 08:34:54.045 [0x7ff12b8846e8] DEBUG - Analyzing database.
Oct 26, 2021 08:34:58.510 [0x7ff12b8846e8] DEBUG - Vacuuming database.
Oct 26, 2021 08:37:46.704 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.708 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.713 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.718 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.722 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.727 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.733 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.737 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.742 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.747 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.751 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.756 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.760 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.765 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.770 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.774 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.779 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.783 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.788 [0x7ff12b8846e8] INFO - SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 26, 2021 08:37:46.792 [0x7ff12b8846e8] DEBUG - Completed forward migration 202109061500.
Oct 26, 2021 08:37:46.826 [0x7ff1274c7b38] DEBUG - BPQ: generating queue items from 0 generator(s)
Oct 26, 2021 08:37:46.826 [0x7ff1274c7b38] DEBUG - BPQ: generated 0 item(s) for queue
Oct 26, 2021 08:37:46.869 [0x7ff1274c7b38] DEBUG - PlayQueue: 0 generated IDs compressed down to a 20 byte blob.
Oct 26, 2021 08:37:46.869 [0x7ff1274c7b38] DEBUG - PlayQueue: 0 generated IDs compressed down to a 2
Plex Media Server v1.24.5.5173-8dcc73a59 - Western Digital MyCloudPR4100 x86_64
Besides rebooting the router and modem, is there any further troubleshooting I can do? I’m stumped as I have not changed networking equipment or service when this started happening.
You have two ethenet adapters plugged in.
Oct 24, 2021 18:42:56.567 [0x7f0c7f5bd0c8] DEBUG - * 3 eth0 (192.168.1.27) (loopback: 0)
Oct 24, 2021 18:42:56.567 [0x7f0c7f5bd0c8] DEBUG - * 4 eth1 (192.168.1.54) (loopback: 0)
which one is the default gateway? (Control Panel - Network Interface)
Whichever one is the default, unplug the other.
Also confirm the one you want to be the default has the “Use as Default Gateway” box checked.
Now restart DSM and Plex.
When restarted,
Ope an incognito window to http://ip.addr.you.chose:32400/web
See if it’ll respond and let you sign in now.
(Having two adapters on the same network which aren’t bonded almost always confuses Plex because it will confuse Synology – resulting in a mess)
Works now! Never had a problem with the two ethernet adapters the past two years (will I miss out on link aggregation I don’t know). Unfortunately I lost my PMS in the process of constant uninstalling unless I can recover it?
If the data is still there (Use FileStation to verify you still have files and folders in PlexMediaServer/AppData/Plex Media Server),
Now open the server
Still appears:
“Not authorized
You do not have access to this server”
Please helpPlex Media Server.zip (58.8 KB)
