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.