No Access to Server

Deploying as Kubernetes using kustomize.

Server deploys and the pod logs show:

2024-06-05T14:32:05.277638715-04:00 [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
2024-06-05T14:32:06.232318561-04:00 [s6-init] ensuring user provided files have correct perms...exited 0.
2024-06-05T14:32:06.233264842-04:00 [fix-attrs.d] applying ownership & permissions fixes...
2024-06-05T14:32:06.233780212-04:00 [fix-attrs.d] done.
2024-06-05T14:32:06.234326237-04:00 [cont-init.d] executing container initialization scripts...
2024-06-05T14:32:08.279942183-04:00 Plex Media Server first run setup complete
2024-06-05T14:32:08.280422231-04:00 [cont-init.d] 40-plex-first-run: exited 0.
2024-06-05T14:32:08.281352243-04:00 [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing...
2024-06-05T14:32:08.880238117-04:00 [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0.
2024-06-05T14:32:08.881226056-04:00 [cont-init.d] 50-plex-update: executing...
2024-06-05T14:32:08.896946968-04:00 [cont-init.d] 50-plex-update: exited 0.
2024-06-05T14:32:08.897854875-04:00 [cont-init.d] done.
2024-06-05T14:32:08.898460795-04:00 [services.d] starting services
2024-06-05T14:32:08.903110553-04:00 [services.d] done.
2024-06-05T14:32:08.903787676-04:00 Starting Plex Media Server.

Going to Web at
http://192.168.1.###:32400/web/index.html#!/settings/web/general

See nothing about any Library or server settings.

Have run:
UserCredentialReset

And tried the 800 other things that has been suggested with not avail.

Server Version#: plexinc/pms-docker:1.40.2.8395-c67dce28e
Player Version#: Version 4.125.1

Any ideas?

Don’t dive so deep into it.

http://192.168.1.xxx:32400/web

then click your way in.

FYI: all RFC-1918 IPs (e.g. 192.168.0.20) are safe to publish as they are non-routable and not unique.

Thanks for the response.
I am not sure what you would expect to see here but my server does not show anywhere.

All I see is a server that I have been granted access too.

Have you configured the container to be network=host so it’s not off on a separate subnet which can’t be seen by broadcast packets.

Thanks for the response.

Running one Kubernetes replica pod (“172.16.10.87”) which forwards to 192.168.##.###.
192.168.##.###:32400 provides access to the Web portal but no library setup.

As far as I know, there can be no network=host mode with Kubernetes.

# pod logs
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...  
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...  
[cont-init.d] 40-plex-first-run: executing...   
Attempting to obtain server token from claim token   
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current   
Dload  Upload   Total   SpentLeft  Speed 
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0100 100990 100990 0  14026  0 --:--:-- --:--:-- --:--:-- 14006   │
Token obtained successfully
Plex Media Server first run setup complete  
[cont-init.d] 40-plex-first-run: exited 0.  
[cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing... 
[cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0.
[cont-init.d] 50-plex-update: executing...  
[cont-init.d] 50-plex-update: exited 0. 
[cont-init.d] done.
[services.d] starting services  
[services.d] done. 
Starting Plex Media Server.

I think it would be helpful if someone could explain what “Plex” requires to ‘Claim’ access to the server. A lot of people talk about how to “fix” it but is it explained anywhere?

Your Credential Utility puts items in the Preferences file but Plex says to remove them to get server access. So it gets hard to find what is needed to associate the user to a server.

Thanks again for the help.

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