[BUG] <title>Cannot access Plex - Docker shows running #420
Comments
|
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
|
Did I do something wrong? This is the first time I posted and I am not an Unpaid expert. I just need help. Thanks |
|
No you didn't do anything wrong but also we don't provide an SLA for our containers/expect a response within X time. With your issue, realistically you need to check your Plex server logs (not container logs) also test from your local lan. |
|
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions. |
|
This seems to be happening to more and more people, this "Critical: libusb_init failed" error.
Many people are seeing this same thing, where the server is running, but it is inaccessible and doesnt show any port or IP. |
|
If you read your logs, it clearly stats it's an error that can't be ignored. It doesn't stop Plex from running. Your issue is related to unraid not the container. |
|
Check your log and see what's printed right before the critical libusb init error |
|
Thank you for looking into this. I cleaned everything out and reinstalled, same error. Here is the log: |
|
I mean the docker log |
|
Not much: Connection to localhost (::1) 32400 port [tcp/*] succeeded! Brought to you by linuxserver.io To support LSIO projects visit: ─────────────────────────────────────── User UID: 99 **** Server is unclaimed, but no claim token has been set **** |
|
Looking at the Unraid logs i see this error pop up (not sure if it is related): Apr 2 15:24:37 CorsoUnraid nginx: 2025/04/02 15:24:37 [error] 8899#8899: *707720 open() "/usr/local/emhttp/webGui/javascript/ace/mode-log.js" failed (2: No such file or directory) while sending to client, client: 192.168.0.20, server: , request: "GET /webGui/javascript/ace/mode-log.js HTTP/1.1", host: "192.168.0.254", referrer: "http://192.168.0.254/Shares/Browse?dir=%2Fmnt%2Fuser%2Fapps%2Fplex%2FLibrary%2FApplication%20Support%2FPlex%20Media%20Server%2FLogs" |
|
From your log: |
|
Also your log shows: Readme explains what you need to do |
|
Also, running it all on a custom network, and all my other containers are working fine. Just this one is an issue. Claimed or Unclaimed, it is the same issue. If you look at the bigger log above, it was claimed. Here is the same log from the same install, now claimed: % Total % Received % Xferd Average Speed Time Time Time Current Brought to you by linuxserver.io To support LSIO projects visit: ─────────────────────────────────────── User UID: 99 Server claimed successfully, navigate to http://serverip:32400/web to complete plex setup. Still the same issue though:
|
|
Like it's already been mentioned, that lib usb issue is not an error. You issue is to do with unraid and/or it's UI. |
|
Cool, thanks. I guess I'll go bother them. |
|
i have exactly the same issue, not on unraid, but on docker almalinux running docker compose. Did a fresh install today all the wat from alma linux to docker, but i can't access the webinterface of plex... My log is the same: [migrations] started **** Server is unclaimed, but no claim token has been set **** |
|
I am also experiencing the issue where the plex container can't seem to connect externally, like the logs @riktanius shared. The actual plex logs have gone since it happened, but haven't seen it happen this month yet |
|
Make sure you claim the server first. Otherwise you won't see it in the gui unless you connect from the same subnet (not likely if it's in a docker network). @Stylee32 If not, check the browser console and it should tell you which addresses it is trying to access the server at and how/why it's failing. |
|
@aptalca the container runs in its own bridge network along with the rest of the arr stack with Caddy connected to it to reverse proxy.. While I don't have the logs anymore, this was appearing in the actual plex server logs "DEBUG - HTTP simulating 408 after curl timeout" |
Is there an existing issue for this?
Current Behavior
I cannot see my Plex server either through VPN or through the Plex app on any device. I was watching from a remote location on Sunday night and I abruptly lost connection. It is as if my Plex server has disappeared. The Docker still shows that it is running. When I copy the log, I do see an error: libusb_init failed. I had this issue once before and I fixed it by deleting my Plex docker and installing it again. I tried to do the same this time but it did not work.
I have a thread here with no solutions: https://forums.unraid.net/topic/186901-cannot-access-plex-even-though-it-is-running-on-unraid-with-no-errors/#comment-1525461
I also have a thread here: https://forums.plex.tv/t/cannot-see-plex-server-on-unraid/905472
**** Server already claimed ****
Docker is used for versioning skip update check
[custom-init] No custom files found, skipping...
Starting Plex Media Server. . . (you can ignore the libusb_init error)
[ls.io-init] done.
Critical: libusb_init failed
Thanks
Expected Behavior
No response
Steps To Reproduce
Cannot access Plex server from any device, the server disappeared but in Plex it shows that it is running
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: