Plex Media Server 1.18 broke library access for my users

Plex Media Server NAS & Devices
1

Hi everybody. I’ve had some problems with PMS ever since I updated to 1.18.0.1944 this morning. All of my users—both managed and shared—lost access to my library. They would either get a spinning wheel or the “No soup for you! You don’t have access to this library” error.

Only me, the admin, was able to see any of my library. On the web player my library would work well for my account, but then when I tried switching to my wife’s managed user account I would get the “No soup for you!” error. After restarting my PMS, Synology, Router, and Modem several times, double-checking file permissions, and then port forwards, I rolled PMS back to 1.17.0.1709 and it’s working flawlessly.

Anybody else know what’s going on here? Any fixes?

Thanks.

Server Version#: 1.18.0.1944
Player Version#: Web player
Synology NAS DS718+ running DSM 6.2.2-24922 Update 3

3

Thanks for the advice. I did check the SHA-1 checksum but did again to be safe. Everything checked out so I installed 1.18.0.1944 again. Same issue happened.

Just rolled back to 1.17.0.1, works as expected. I’ve attached logs if they’ll tell us anything. Thanks.

Plex Media Server Logs_2019-10-12_00-16-54.zip (1.1 MB)

5

Thanks trumpy. What confuses me is that when I open with my admin account at http://nas-ip-address/web everything looks great, but when switching to a managed user’s account, from that very same browser instance, I get the “You do not have access to this server error.” I feel like that indicates a user or sharing permissions issue, right? I’m testing it on the same network, browser, IP address, etc.

I tried Public version 1.18.0.1913-e5cc93306 of PMS and experienced the same issues. Logs attached (I tested the managed user around 9:32 AM EST).

Currently back on 1.17.0.1709-982421575 so my users can access. I had a few use it this AM with no issues on this version.

Thanks.

10%20AM Plex Media Server Logs_2019-10-12_09-33-38.zip (1.6 MB)

8

Hi trumpy, any luck with the guru? I verified all my network settings and everything seems to be operational. I’ve also tried pretty much every suggested fix for similar issues found on the forums.

Please let me know if I should also post the topic in a different category. I initially thought it might be some sort of Synology permissions problem, so I went here first.

Thanks!

10

Wow, I’m very sorry to hear that your guru is in the hospital. He certainly did not have to review my logs while incapacitated, but I very much appreciate it.

Looks like correcting Preferences.xml solved the issue. I had to reclaim my server to my Plex account, but my managed user account is working as expected now and my PMS version is the public 1.18.0.1913.

Was this issue a result of something I did wrong while updating? Or just an occupational hazard?

Thanks to you and your guru for all the help!

12

Remember, Rub the tummy with the LEFT hand first clockwise, then the RIGHT hand counter-clockwise.

I am home now. Trumpy’s ping to my cell gave me something to do. It was an easy question.

I will be sleeping a lot these next few so not sure when I’ll be online

1 Like
13

Thanks for your dedication, Chuck! Hope you feel better soon.

14

Hello,
What ended up being the fix for this issue? I’m having the same problems when moving from 1.18.1 to 1.18.2. Sounds like a fix in Preferences.xml but I’m not seeing the actual solution. Thanks

15

Logs please (DEBUG on, VERBOSE off), collected in the ZIP, after a PMS restart and recreation/ recapture of the problem.

16

Good evening,

I have had the same issue at hand since around the time 1.18.* versions were released. I rolled back to the newest version I could find that still worked, which was version 1.16 in the Synology Package Center. I am revisiting this issue because I want to move forward and utilize the new features, so I installed PMS 1.18.3.2129 today.

I have included the PMS logs (Debug, not Verbose). Plex Media Server Logs_2019-12-10_21-25-13.zip (3.3 MB). I tried to read through them, but I am quite lost. Any help on this is highly appreciated.

Nick

17

Thank you for the logs.

I am seeing “Forbidden” error repeating in your logs when it attempts to contact Plex.tv

This type thing happens when:
a. Bad password / token used on the server’s account
b. Improper handling of credentials in a Proxy.

Dec 10, 2019 21:23:02.172 [0x7f25da87a700] DEBUG - EventSource: Stopping.
Dec 10, 2019 21:23:02.172 [0x7f25da87a700] DEBUG - PubsubServerManager: Switching to next host in region: 184.105.148.112
Dec 10, 2019 21:23:02.174 [0x7f25da87a700] DEBUG - EventSource: Stopping.
Dec 10, 2019 21:23:02.174 [0x7f25da87a700] DEBUG - EventSource: Resolving 184.105.148.112 port 443
Dec 10, 2019 21:23:02.174 [0x7f25da87a700] DEBUG - EventSource: Resolved 184.105.148.112 to 184.105.148.112
Dec 10, 2019 21:23:02.307 [0x7f25dab68700] DEBUG - EventSource: Connected in 92 ms.
Dec 10, 2019 21:23:02.307 [0x7f25dab68700] DEBUG - EventSource: Wrote data, reading reply.
Dec 10, 2019 21:23:03.135 [0x7f25da87a700] DEBUG - EventSource: Read HTTP reply header.
Dec 10, 2019 21:23:03.135 [0x7f25da87a700] DEBUG - EventSource: Failure in ParseHeader: HTTP/1.1 403 Forbidden
Server: nginx
Date: Wed, 11 Dec 2019 05:23:03 GMT
Content-Type: text/html
Content-Length: 162
Connection: close

<html>
<head><title>403 Forbidden</title></head>
<body bgcolor="white">
<center><h1>403 Forbidden</h1></center>
<hr><center>nginx</center>
</body>
</html>
 (0 - Success).

Can you elaborate please?

18

I an not utilizing a proxy or other intermediary connection to access plex.tv from the Synology NAS. However, I am unsure if the password or token is an issue. At one point, I had “logged out of everything” which caused accessibility issues to the Plex Media Server instance at that time. I don’t recall what method I used to fix it (you know the usual: some Google, some trial-and-error, some luck), but I do recall having to either change or find the old server authentication token.

19

Did anyone find a solution to this? I just migrated my library from a Mac to my Synology, and everything LOOKS fine, but seeing the error:

“EventSource: Failure in ParseHeader: HTTP/1.1 403 Forbidden Server: nginx Date: Sun, 09 Feb 2020 04:47:03 GMT Content-Type: text/html Content-Length: 162 Connection: close 403 Forbidden

403 Forbidden

nginx (0 - Success).”

In my logs, and streaming from Apple TV seems broken. I’ve now downgraded to 1.16 and that SEEMS to work. Transcoding also seemed broken with 1.18 with some movies. So it would seem 1.18 just doesn’t get along with the Synology (in my case a DS1019+).

20

I am having the same issue after updating recently. I can watch my Plex movies without problems, but my mother as shared user can’t. She gets the “No soup for you” treatment. When I log in with her credentials I get the same message. Within the same instance of my browser I can see my stuff, when logged in as myself or I see no soup in the other tab when logged in as my mother.

Meanwhile a friend, also a shared user, confirmed the issue seeing the same error when accessing my Plex server.

I’ve updated the Plex server manually two times since I got this error message and I am now at 1.18.8, still experiencing the same issue. Does anyone know how to solve this?

21

Roll back to 1.16. See if it fixes it. See here: DS1019+ Users other than admin can't see server, since migration

22

Thanks, that did the trick!

23

Sweet. Hopefully the developers take note of this.

24

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