Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] binhex - Plex Pass

Featured Replies

I am having a weird error, and wanted to see if other see it. If I try and get to my Plex Server just by ip:port I get a Error 401. But, if I go to UnRAID first and open the webpage from the Docker tab it opens up just fine. This start very recently.

  • Replies 1.8k
  • Views 412.8k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • apparently plex has removed the redirection to /web, so now you need to append /web to the url, for example:- http://192.168.1.10:32400/web

  • Hi all, the issue where the container is stopping MAY of been related to the introduction of healthchecking, this checks to see if the internet connection is operational, if not the container is marke

  • I obviously don't reclaim my Plex server very often (this might even be the first time!), but i went through it this morning and it was relatively painless, FWIW here are my notes (some of this is fro

Posted Images

  • Author
14 hours ago, carnivorebrah said:

t just says "400 Bad Request". Any ideas how to fix this?

 

4 hours ago, strahd_zarovich said:

If I try and get to my Plex Server just by ip:port I get a Error 401.

apparently plex has removed the redirection to /web, so now you need to append /web to the url, for example:-

http://192.168.1.10:32400/web

Well there you go. Thank you binhex

On 4/24/2025 at 9:59 PM, binhex said:

 

apparently plex has removed the redirection to /web, so now you need to append /web to the url, for example:-

http://192.168.1.10:32400/web


Well, that's another annoying change by the Plex powers that be...

For others interested, I added this to my nginx proxy config to redirect to /web/.
 

    # Redirect root to /web
    location = / {
        return 302 /web/;
    }
    
    location / {
      # Normal config here...


I tried having another location for /web/ but couldn't get it working.

I recently updated to 1.41.7.9717-1-01 over the weekend and for one of my libraries my 'Refresh Metadata' and 'Fix Match' options stopped working, when i would select 'Fix Match' the presented options were completely blank and I could not even search the title within TVDB.

 

For extra context I use XMBCnfoTVimporter as that libraries main agent and manually 'Fix Match' a series when I add it and get the metadata from TVDB, up until this update it has been working fine for the past year.

Rolling back to 1.41.6.9685-1-01 immediately fixed the issue, is this by design from Plex with the latest updatae or just a bug from the latest updated? I would assume the latter.

Anyone else run into a similar issue with the new update or able to recreate?

dbrepair.sh scan showed no issues with database either before and after scanning

Fixing Plex Behind Cloudflare Tunnel After the Latest Update

Hey everyone! I’ve been running my Plex server behind a Cloudflare Tunnel for a while, but the recent Plex update introduced a change where the web interface now requires /web at the start of every request. Here’s how I fixed it with a simple URL Rewrite Rule in Cloudflare:

 

Open Your Cloudflare Dashboard

  1. Log in to Cloudflare and select your account and website.
  2. Go to Rules > Overview.
  3. Click Create rule > URL Rewrite Rule.

 

Configure the Rewrite Rule

  • Rule Name: Plex Web UI Rewrite
  • If Incoming Request matches:
    http*://plex.mydomain.com*
  • Then…
    • Action: Rewrite Path of Moved Section
    • Target Path: (leave blank)
    • Rewrite To: 
      /web

       

Your final rule should effectively read:

Match requests to plex.mydomain.com/* and rewrite the path to /web.

 

Save and Test

Save the rule and make sure it’s enabled (you may need to drag it to the top of your rule list).

Open your browser and visit: https://plex.mydomain.com

You should be redirected automatically to /web and see the Plex login screen.

 

Why This Works

The Cloudflare Tunnel proxies requests from plex.mydomain.com to your local Plex server at localhost:32400.

The URL Rewrite Rule appends /web to every incoming request, satisfying Plex’s new requirement without any extra bookmarks or manual redirects.

 

That’s it! You’re back up and running. Hope this helps anyone else who ran into the same issue Cloudflare Tunnels! 😊

Im having a strange thing happening for about a week now a few remote managed users are getting a playback error on some material but not all. It states playback has stopped due to multiple playback errors. please check your connection and try again. They are able to watch the episodes if they decrease the playback quality as low as it goes. But outside of these few episodes everything else plays fine no issues

Forgot to mention I am transcoding to ram, using a intel iGPU from a 12700k. I looked at my logs and i dont see any errors and if i try and play back the same material both remotely and locally i dont see the same issues. But if they try it always fails, and its multiple users. Is it possible to transfer to the non plex pass version without breaking my plex setup?

Edited by T_Matz

Last update, I just rolled back the version to binhex/arch-plexpass:1.41.6.9685-1-01 and now everything is working as expected again. Not sure what the issue was with the new version but it did not like remote play on a few tvs. I think they are roku TVs

If you are getting the 401 error, edit the template, set the WebUI field to:
http://[IP]:[PORT:32400]/web

On 4/22/2025 at 4:58 AM, binhex said:

try stopping the container, then delete the file /config/perms.txt and then start the container, this should reset permissions for you, it could take a while to process so leave it running until the conainer starts, or if it's in a broken state then leave it for around 30 minutes then perform the dbrepair.sh again

I"m sorry got pulled away for travel for work. Is perms.txt located on the flash drive? If so my config doesn't have a perms.txt file in it? If its located somewhere could you point me in the right direction? Thank you!

 

EDIT: Found it...its in the docker director...deleted it but it didn't seem to help. My system is pretty messed up and docker container don't want to restart once they've been stopped so I had to restart my server to get it to restart plex. So not sure if that impacted what you mentioned about resetting permissions. 

Edited by valhalla540

I'm also getting the 400 error, but adding /web to the url doesn't fix it. Clients are still working it seems but no luck with the webui.

 

Here are the logs from a docker restart:

 

2025-05-05 00:10:57.301945 [info] Host is running unRAID
2025-05-05 00:10:57.323003 [info] System information: Linux Dan-Server 6.6.78-Unraid #2 SMP PREEMPT_DYNAMIC Thu Feb 20 13:33:15 PST 2025 x86_64 GNU/Linux
2025-05-05 00:10:57.343802 [info] Image tags: BASE_RELEASE_TAG=2025032801,IMAGE_RELEASE_TAG=1.41.7.9717-1-01
2025-05-05 00:10:57.369498 [info] PUID defined as '99'
2025-05-05 00:10:57.399737 [info] PGID defined as '100'
2025-05-05 00:10:57.455331 [info] UMASK defined as '000'
2025-05-05 00:10:57.477473 [info] Permissions already set for '/config'
2025-05-05 00:10:57.510878 [info] Deleting files in /tmp (non recursive)...
2025-05-05 00:10:57.535973 [info] TRANS_DIR defined as '/config/transcode'
2025-05-05 00:10:57.569452 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'
2025-05-05 00:10:57.590391 [info] Starting Supervisor...
2025-05-05 00:10:57,864 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2025-05-05 00:10:57,864 INFO Set uid to user 0 succeeded
2025-05-05 00:10:57,866 INFO supervisord started with pid 7
2025-05-05 00:10:58,868 INFO spawned: 'plexmediaserver' with pid 64
2025-05-05 00:10:58,869 INFO reaped unknown pid 8 (exit status 0)
2025-05-05 00:10:58,972 DEBG 'plexmediaserver' stderr output:
Plex Media Server is already running. Will not start...

2025-05-05 00:10:58,980 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22646628284944 for <Subprocess at 22646628284608 with name plexmediaserver in state STARTING> (stdout)>
2025-05-05 00:10:58,980 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22646626747728 for <Subprocess at 22646628284608 with name plexmediaserver in state STARTING> (stderr)>
2025-05-05 00:10:58,980 WARN exited: plexmediaserver (exit status 1; not expected)
2025-05-05 00:10:58,980 DEBG received SIGCHLD indicating a child quit
2025-05-05 00:10:59,984 INFO spawned: 'plexmediaserver' with pid 70
2025-05-05 00:11:00,986 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-05-05 00:11:13,418 DEBG 'plexmediaserver' stdout output:
Critical: libusb_init failed

 

On 4/15/2025 at 5:26 PM, Kognac said:



Still having this issue, tried to use a backup, but I get the same error. tried today going back to the latest branch.

I am still having this issue, running the dbrepair.sh appears to do nothing as well since I went through all the steps and it didn't help fix anything.
*** steps used to fix Database corruption***


How to start a DbRepair Within the Plex Console, Type: DBRepair.sh
 

These are the options, you likely only need to do the first two, Option 1 and 2.

Select

1 - 'stop' - Stop PMS.

2 - 'automatic' - Check, Repair/Optimize, and Reindex Database in one step.

3 - 'check' - Perform integrity check of database.

4 - 'vacuum' - Remove empty space from database without optimizing.

5 - 'repair' - Repair/Optimize databases.

6 - 'reindex' - Rebuild database indexes.

7 - 'start' - Start PMS

8 - 'import' - Import watch history from another database independent of Plex. (risky).

9 - 'replace' - Replace current databases with newest usable backup copy (interactive).

10 - 'show' - Show logfile.

11 - 'status' - Report status of PMS (run-state and databases).

12 - 'undo' - Undo last successful command.

21 - 'prune' - Remove old image files (jpeg,jpg,png) from PhotoTranscoder cache & all temp files left by PMS.

42 - 'ignore' - Ignore duplicate/constraint errors.

88 - 'update' - Check for updates.

98 - 'quit' - Quit immediately. Keep all temporary files.

99 - 'exit' - Exit with cleanup options.


Select Option 1 to stop the Plex Media Service(PMS) then select Option 2 and it should fix your database with minimal input.

7d9iwJ.png

Nothing seems to be working (testing deleting the perms.txt file to see if that helps), and I would really not like to rebuild the Plex database again, It took forever last time, about a week to fully rebuild. Going back to branch: 1.41.5.9522-1-01 fixes the issue, but I would like to get to the latest releases again.

***okay update the next morning, So last night I was able to get it to start working correctly. I fixed it by deleting the perms.txt document and then after restart it was able to recognize and read the database.

Edited by Kognac

I just updated to the latest version of binhex-plexpass and my local live tv now stutters. I have an hdhomerun hooked up. I'm not all that familiar with unraid, so bear with me. How do I rollback to the prior version? I'm not seeing anywhere in the container info where I can edit the version I want.

 

UPDATE: I figured it out. A rollback to v. 1.41.7.9749-1-01 seems to have fixed the issue.

Edited by Jack_Flack

on Unraid 7.1.2, binhex-plexpass docker version 1.40.2.8312-1-04. not showing any updates available, but when i find binhex-plexpass in the app store, it shows that it was recently updated. i also see some others above mentioning a version that would be above mine.

 

this would be a non issue, but the recent plex ios app update it now saying that i have to update my server to be able to access it through the app.

 

any ideas why i wouldnt be showing an update available?

9 hours ago, squeekr said:

on Unraid 7.1.2, binhex-plexpass docker version 1.40.2.8312-1-04. not showing any updates available, but when i find binhex-plexpass in the app store, it shows that it was recently updated. i also see some others above mentioning a version that would be above mine.

 

this would be a non issue, but the recent plex ios app update it now saying that i have to update my server to be able to access it through the app.

 

any ideas why i wouldnt be showing an update available?

Check and see if the Repository is set to: binhex/arch-plexpass:latest

15 hours ago, Kognac said:

Check and see if the Repository is set to: binhex/arch-plexpass:latest

this is it. thank you so much. i think i may have set it to a specific version in the past to roll it back due to some issue, and forgot.

Plex at it again with breaking core features every update. Live TV & DVR is currently broken. I can no longer use my xmltv guide provided by my threadfin docker app on the latest update. Rolling back to 1.41.7.9795-1-01 fixes it.

Hello all. I tried searching through for "Not authorized" but couldn't find anything. I am trying to migrate my Windows Plex server to the binhex-plexpass on my Unraid server. I want to have as little impact as possible to my remote users. I have copied the entire "Plex Media Server" folder from my Windows machine that includes the "Cache" and all other folders over to the "Plex Media Server" within the /config folder on the Unraid container. I added the PLEX_CLAIM variable but I still get "Not authorized" and I don't see the server show up in my "Authorized Devices" on my Plex account. Has anyone successfully done something like this?

2025-05-22 15:28:31,904 DEBG 'plexmediaserver' stdout output:

Critical: libusb_init failed

  • Author
6 minutes ago, dopeytree said:

2025-05-22 15:28:31,904 DEBG 'plexmediaserver' stdout output:

Critical: libusb_init failed

its not critical, ignore it.

Anyone having issues with their Plex Media Server this week. Starting since like Tuesday I keep having to completely reboot unraid to get Plex to work, then after a good 16 hours it dies again.

Logs don't really show anything.

Created by...

___. .__ .__

\_ |__ |__| ____ | |__ ____ ___ ___

| __ \| |/ \| | \_/ __ \\ \/ /

| \_\ \ | | \ Y \ ___/ > <

|___ /__|___| /___| /\___ >__/\_ \

\/ \/ \/ \/ \/

https://hub.docker.com/u/binhex/

2025-05-23 19:04:22.972602 [info] Host is running unRAID

2025-05-23 19:04:22.984554 [info] System information: Linux NAS-MorNet 6.1.106-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 21 23:36:07 PDT 2024 x86_64 GNU/Linux

2025-05-23 19:04:22.996534 [info] Image tags: BASE_RELEASE_TAG=2025042801,IMAGE_RELEASE_TAG=1.41.7.9799-1-01

2025-05-23 19:04:23.009299 [info] PUID defined as '99'

2025-05-23 19:04:23.025114 [info] PGID defined as '100'

2025-05-23 19:04:23.177842 [info] UMASK defined as '000'

2025-05-23 19:04:23.190461 [info] Permissions already set for '/config'

2025-05-23 19:04:23.203885 [info] Deleting files in /tmp (non recursive)...

2025-05-23 19:04:23.217748 [info] TRANS_DIR defined as '/config/transcode'

2025-05-23 19:04:23.232399 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no'

2025-05-23 19:04:23.244854 [info] Starting Supervisor...

2025-05-23 19:04:23,332 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing

2025-05-23 19:04:23,332 INFO Set uid to user 0 succeeded

2025-05-23 19:04:23,333 INFO supervisord started with pid 7

2025-05-23 19:04:24,334 INFO spawned: 'plexmediaserver' with pid 64

2025-05-23 19:04:24,334 INFO reaped unknown pid 8 (exit status 0)

2025-05-23 19:04:24,348 DEBG 'plexmediaserver' stderr output:

Plex Media Server is already running. Will not start...

2025-05-23 19:04:24,352 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22611256490512 for <Subprocess at 22611256490176 with name plexmediaserver in state STARTING> (stdout)>

2025-05-23 19:04:24,352 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22611254937872 for <Subprocess at 22611256490176 with name plexmediaserver in state STARTING> (stderr)>

2025-05-23 19:04:24,352 WARN exited: plexmediaserver (exit status 1; not expected)

2025-05-23 19:04:24,352 DEBG received SIGCHLD indicating a child quit

2025-05-23 19:04:25,353 INFO spawned: 'plexmediaserver' with pid 70

2025-05-23 19:04:26,354 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2025-05-23 19:27:11,092 DEBG 'plexmediaserver' stdout output:

Critical: libusb_init failed

2025-05-23 19:27:21,860 DEBG 'plexmediaserver' stderr output:

connect: Operation timed out

2025-05-23 19:27:27,875 DEBG 'plexmediaserver' stderr output:

connect: Operation timed out

2025-05-23 19:27:33,891 DEBG 'plexmediaserver' stderr output:

connect: Operation timed out

2025-05-23 19:27:39,907 DEBG 'plexmediaserver' stderr output:

connect: Operation timed out

Edited by comfox
added log

Attempting DB repair and the script fails to kill the PMS process, but continues the script anyway.

[INFO] Plex Media Server database repair script - written by binhex.

1) Check integrity 3) Rebuild indexes 5) Quit

2) Repair structure (basic repair) 4) Low-level recovery

Please select the Plex DB repair operation: 4

Selected operation 'Low-level recovery' will stop Plex Media Server, do you want to continue? y

[INFO] Stopping Plex Media Server by sending kill to PID '67

257'

./dbrepair.sh: line 18: kill: 67

257: arguments must be process or job IDs

[INFO] Backup of existing database to filename 'com.plexapp.plugins.library.db.backup.20250525012017' has been performed.

[INFO] Executing SQLite query in filename '/tmp/low-level-db-recovery.sql'...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.