Plex Media Server 1.41.7.9717 Causes 401 Unauthorized Error

Plex Media Server Plex Pass Betas
1

Server Version#: 1.41.7.9717

As Soon as I update to the latest beta I start getting 401 Unauthorized error on Plex web. It also stops working on my android device. The content would load but I am unable to play anything as it would keep spinning.

I logged in via the IP(Which still worked) and checked all the settings and everything and the server was claimed and everything. So probably something to with the new beta update.

Just wanted to bring this to your attention so that this does not end up in the new stable. Downgrading to latest public version resolved the 401 unauthorized issue.

image

4 Likes
2

I had the same issue, with 1.41.7.9717, I had to go manually to https://…/web to open the gui. I downgraded to 1.41.6.9685 and is working again without /web.
Redirect is broken, i tried localip:port, remoteip:port, customdomain. Also app.plex.tv was showing an issue with SSL being required.

2 Likes
3

I don’t think this is a problem with beta. I am using the Docker version from linuxserver.io which is latest and I am on 1.41.6 but I have the same issue. I can also only access Plex from the Windows app and not on the web.

1 Like
4

You don’t have server updates set to beta in your admin settings, do you? Latest tag in LinuxServer.io image will update you to the latest beta automatically if you are on latest tag and server updates are set to beta. I don’t experience this issue on latest public just the new beta.

5

Looks like devs are aware of this issue. Please confirm if the support team stumbles upon this.

1 Like
6

thanks for reporting. Glad I didn’t upgrade. I was tempted to.

7

Last docker update bit me too. Just spent hours reviewing nginx proxies, firewall settings, and resetting the homelab. Ouch.

Changed a little code to the docker compose file and back in business. (Not a pro, but I think it is right)

image: plexinc/pms-docker:${VERSION:-latest}

Then set an environment variable VERSION to the tag you want. Leave blank when bugs are fixed.

1 Like
8

I also have the same issue with 1.41.7.9717. I can open the locally address (10.x.x.x:32400/web) but the external one gives 401 Unauthorized.

edit
Manually putting /web after the external address worked for me

1 Like
9

I tried modifying my Traefik rule as follows but still experiencing the 401 Unauthorized.
Any idea?

  services:
    plex-svc:
      loadBalancer:
        passHostHeader: true
        servers:
          - url: "http://10.0.1.170:32400/web/"
1 Like
10

No need to change it, just append /web manually when using the previous setup until it gets fixed.

1 Like
11

Also have the same issue. I have appended /web as the path in nginx proxy manager and that just gives me a 404 back.

12

the better fix is to rollback lol. It’s a beta version anyway.

1 Like
13

It is the fix if wanting to use the beta and keeping his usual Traefik setup. Goes without saying that you can roll back.

14

What I’m saying is, is there even any reason to use 1.41.7.9717?

Which one of these patches is he in desperate need of?

  • (Continue Watching) Always return ancestor guids for in-progress items (PM-3303)
  • (Filters) The DOVI filter would result in an error when applied to a show library (PM-3272)
  • (Transcode) Transcoding High Bitrate EAC-3 could result in choppy audio. (PM-691)
  • (Transcodes) Some transcodes could result in larger than required bitrates (PM-2772)
15

You do you, just let others do what they want to do.

1 Like
17

Hey Everyone, New beta is out that fixes this issue.

Mods, this thread can be closed.

2 Likes
18

Same issue Version 1.41.8.9834 2025-06-07

20

I was able to work around using a saved URL I had previously saved http://127.0.0.1:32400/web/index.html#!/

Loading, by right clicking the Plex icon in the Windows system tray, and selecting “Open Plex” from the context menu, loads a different URL
http://127.0.0.1:32400/myplex/launch?X-Plex-Token=local-8xxxxxx6-bxxf-4xx2-axx8-6xxxxxxxxxx0, which results in a 401 Unauthorized error. (Note x’d out most of the numbers/letters in the token string. Hope this helps others

21

Found another posting on the internet… TL’DR is this was caused by having two instances of Plex Server running (for example one instance started as service, second instance started in user space) 99% sure this is because I recently tweaked things to get Plex starting at boot time without user intervention, as I have Windows automatic update and restart enabled

22

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