Plex "You do not have access to this server" on TrueNAS Scale

[rpr11]

I am currently running TrueNAS-SCALE-22.02-RC.1 trying to install the plex application version 1.6.12 but after the container finishes deploying and I try to connect to the server on http://serverIP:32400 I get a blank page saying "Not authorized You do not have access to this server". When I configure the container with no claim token the server works fine and has me logged in with my plex account the server just isn't claimed which would be fine if I didn't want to enable remote access. Also I tipple checked that the right plex account is signed in (I only have 1) and the servers are showing up as owned by that account in the authorized devices section when I go to the settings for my account at plex.tv but I cannot access the media servers remotely or locally. so I believe that the claim token is working and that it is some problem with the container.

container config:

• Application Name: plex
• Version: 1.6.12
• Configure Host Network: true
• Configure Plex TCP Service:
  • Port to expose for Plex UI: 32400
• Plex Storage:
  • Transcode Volume:
    • Enable Host Path for Plex Transcode Volume: true
    • Host Path for Plex Transcode Volume: /mnt/tank/containers/plex/transcode
  • Data Volume:
    • Enable Host Path for Plex Data Volume: true
    • Host Path for Plex Data Volume: /mnt/tank/media
  • Config Volume:
    • Enable Host Path for Plex Config Volume: true
    • Host Path for Plex Config Volume: /mnt/tank/containers/plex
• Plex Claim Token: claim-8d5xdfFzYyLzQK7yyFGa
• Plex container timezone: 'America/Chicago' timezone
• Update Strategy: Kill existing pods before creating new ones

log file:
2021-10-28T14:18:45.489144853Z [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
2021-10-28T14:18:45.561095813Z [s6-init] ensuring user provided files have correct perms...exited 0.
2021-10-28T14:18:45.562578174Z [fix-attrs.d] applying ownership & permissions fixes...
2021-10-28T14:18:45.563514566Z [fix-attrs.d] done.
2021-10-28T14:18:45.564548803Z [cont-init.d] executing container initialization scripts...
2021-10-28T14:18:45.566619818Z [cont-init.d] 40-plex-first-run: executing...
2021-10-28T14:18:45.771249740Z Attempting to obtain server token from claim token
2021-10-28T14:18:45.859030406Z % Total % Received % Xferd Average Speed Time Time Time Current
2021-10-28T14:18:45.859194865Z Dload Upload Total Spent Left Speed
2021-10-28T14:18:50.782944617Z
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:03 --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:04 --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:04 --:--:-- 0
100 7034 0 7034 0 0 1428 0 --:--:-- 0:00:04 --:--:-- 1970
2021-10-28T14:18:50.798721069Z Token obtained successfully
2021-10-28T14:18:50.823315552Z Plex Media Server first run setup complete
2021-10-28T14:18:50.824280373Z [cont-init.d] 40-plex-first-run: exited 0.
2021-10-28T14:18:50.826201959Z [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing...
2021-10-28T14:18:50.834442579Z [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0.
2021-10-28T14:18:50.836150871Z [cont-init.d] 50-plex-update: executing...
2021-10-28T14:18:50.916255123Z [cont-init.d] 50-plex-update: exited 0.
2021-10-28T14:18:50.917373402Z [cont-init.d] done.
2021-10-28T14:18:50.918585242Z [services.d] starting services
2021-10-28T14:18:50.928334398Z [services.d] done.
2021-10-28T14:18:50.931518933Z Starting Plex Media Server.
2021-10-28T14:19:03.758350115Z Critical: libusb_init failed

 

[LarsR]

Did you use an old claim token or did you generate a new one with plex.tv/claim? When i first set up plex i took more then the 5 Minutes a generated token is valid so i had to generate a new one.

 

[rpr11]

I used a fresh token the container took about 2 minutes to boot up from the time i generated the token and the server did show up under my devices when I checked.

 

[adapa]

LarsR
any solution to this? I'm running into the same issue

 

[adapa]

I was able to address this;
the url ported over is problematic, make sure http://[your ip].port etc