Hello, I'm struggling to connect the plex container to my server. I've already logged in with my account and followed the steps : claim code / paste it on the dashboard widget but still no success. Any guess?
10 replies
Chris wrote:
Thanks -- no need to re-paste, I've already got the full report from your comment above, and it checked out clean across the board (network, VPN, storage all green). That actually rules out a config problem on your end, which is why I flagged this one straight to Tom -- it needs a closer look at why Plex specifically can't reach its own servers, past what remote troubleshooting can figure out. He'll follow up here once he's dug into it. Sorry this one's dragging out.
Chris wrote:
Hey mdma, welcome! Nothing's broken on your end -- these claim codes are just really short-lived: they expire about 4 minutes after you generate them at plex.tv/claim, so it's easy for one to time out between copying it and pasting into the dashboard widget. Try grabbing a brand new code and pasting it in right away. If it still doesn't take, there's a backup way: on the same browser where you're signed into plex.tv, open http://your-NAS-IP:32400/web directly -- it should spot your unclaimed server on the network and let you link it that way. Let me know if you still see the generic 'set up Plex' page after that.
mdma wrote:
I've tried several times, even reinstalling plex, logging with different accounts but always find me on the generic webpage (even typing http://your-NAS-IP:32400/web directly)
Chris wrote:
Nothing wrong on your end -- the claim code is only good for about 4 minutes, and pasting it in kicks off a ~30 second restart behind the scenes to apply it. If that restart is still finishing when the code expires, you land right back on the generic page every time, which matches what you're seeing. One more try: grab a completely fresh code from plex.tv/claim, paste it in immediately, then wait a full 2 minutes before opening Plex again (skip refreshing early). Still generic after that? Run sudo sparkbox logs plex over SSH and paste what it shows -- that'll tell us exactly what's happening.
mdma wrote:
─────────────────────────────────────── Linuxserver.io version: 1.43.3.10828-00f62d37d-ls315 Build-date: 2026-07-14T19:39:38+00:00 ─────────────────────────────────────── creating group groupgb91 with id 105 adding /dev/dri/renderD128 to group groupgb91 with id 105 adding /dev/dri/card0 to group video with id 44 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 0 Unable to claim Plex server. Either manually claim by connecting to http://serverip:32400/web from the same network subnet, or recreate container with a new claim token. Docker is used for versioning skip update check [custom-init] No custom files found, skipping... Starting Plex Media Server. . . (you can ignore the libusbinit error) Connection to localhost (127.0.0.1) 32400 port [tcp/] succeeded! [ls.io-init] done. Critical: libusbinit failed
Chris wrote:
Thanks for pasting that -- it shows the container itself couldn't reach Plex's servers to finish the claim, even with a fresh code, so it's not a timing thing. Can you check one thing over SSH: run sudo sparkbox doctor and see if it flags anything under network or connectivity? That'll tell us if something's blocking the Plex container specifically from reaching plex.tv. I'm also flagging this thread to Tom now since two clean attempts have both failed the same way.
mdma wrote:
SparkBox v1.6.492 - Self-Hosted Privacy Stack Created by Tom Spark | youtube.com/@TomSparkReviews Environment: NAS (generic) SparkBox Doctor Running diagnostics... [Install location] [OK] SparkBox is installed at: /opt/sparkbox [OK] Settings file (.env): /opt/sparkbox/.env [OK] Media library folder (MEDIAROOT): /volume2/Media [Docker] [OK] Docker daemon is accessible [OK] Docker version: Docker version 29.4.3, build 055a478 [OK] Docker Compose: 5.1.3 [Docker Socket] [OK] Docker socket exists at /var/run/docker.sock [OK] Docker socket is readable [User IDs] [INFO] Current user: root (UID=0, GID=0) [OK] PUID=1000 (containers run as UID 1000) [OK] PGID=10 (containers run as GID 10) [Container Egress] [OK] Apps can reach webhook.tomsparkbox.com over sbproxy (their real network) [OK] Docker's default bridge can reach tomsparkbox.com (dashboard Update button) [Port Conflicts] [OK] Port 8080: in use by SparkBox (sb-npm) [OK] Port 8444: in use by SparkBox (sb-npm) [OK] Port 8443: in use by SparkBox (sb-dashboard) [OK] Port 9000: in use by SparkBox (sb-portainer) [Portainer Auth] [OK] Portainer admin login verified (HTTP 200) [VPN Tunnel] [OK] Gluetun tunnel is healthy [Hardware Transcoding] [OK] /dev/dri exists -- GPU devices detected total 0 drwxr-xr-x 3 root root 100 Jul 31 21:48 . drwxr-xr-x 20 root root 7880 Jul 31 21:49 .. drwxr-xr-x 2 root root 80 Jul 31 21:48 by-path crw-rw---- 1 root video 226, 0 Jul 31 21:48 card0 crw-rw---- 1 root render 226, 128 Jul 31 21:48 renderD128 [OK] Intel Quick Sync / GPU render device available (renderD128) [OK] Render device is accessible by current user [OK] sb-jellyfin-media is in the host's real render group (105) [Media Storage] [OK] MEDIAROOT=/volume2/Media exists [OK] MEDIAROOT is writable [OK] Your apps (user id 1000) can read your media library [INFO] Free space at MEDIAROOT: 1802GB [System Resources] [INFO] Total RAM: 39884MB [INFO] Available RAM: 31503MB [OK] RAM looks sufficient for 9 enabled modules [INFO] Free disk at SBROOT: 92GB [NAS-Specific] [INFO] NAS type: generic [INFO] Install directory: /opt/sparkbox [WARN] Install directory is on system partition -- consider moving to a data vol ume There is no one-shot move command. The supported route is: 1. sudo sparkbox backup 2. copy the archive somewhere off this partition 3. re-install with: --install-dir <path on your data volume 4. sudo sparkbox restore <archive Restore now rewrites SBROOT in the settings file to the new location. [Container Health] [OK] All SparkBox containers are running and passing their health checks [Saved Passwords] [WARN] sb-filebrowser: the password saved in state/filebrowser-admin-password.txt is NOT accepted (HTTP 403). [WARN] This happens after a reinstall over existing data, or if the password was [WARN] changed inside the app itself — the saved copy then drifts out of sync. Fix it with: sudo /opt/sparkbox/sparkbox reset-password filebrowser [WARN] sb-jellyfin-media: the password saved in state/jellyfin-admin-password.txt is NOT accepted (HTTP 401). [WARN] This happens after a reinstall over existing data, or if the password was [WARN] changed inside the app itself — the saved copy then drifts out of sync. Fix it with: sudo /opt/sparkbox/sparkbox reset-password jellyfin ============================================ 2 issue(s) found. Review warnings above and fix as needed.
Chris wrote:
That output stops right where the useful part is -- keep scrolling past User IDs and you'll hit a section called Container Egress, which checks whether your apps can actually reach the internet. That's the piece that'll tell us if this is just Plex or your whole box. Can you paste that section too? Given curl showed 0 bytes when Plex tried to claim, my guess is that section will show something blocked -- but let's confirm it rather than guess further.
mdma wrote:
I've edited the original message with the full report
mdma wrote:
thank you very much!