Unable to connect to Plex except via Web

[appliance]

for the first 50 hours of troubleshooting, i couldn't even deploy (connection refused). I removed 10.0.0.2 (a real NIC) from the allowed networks to fix this. I never seen the plex UI on Scale. Using traeffic which works with other app (1 - that's my progress this month). But at least Plex is doing something:
WARN - [CERT] MyPlex: Updating device connections failed, retrying in 10 seconds.
ERROR - [CERT] PKCS12_parse failed: error:23076071:PKCS12 routines:PKCS12_parse:mac verify failure
[CERT] Found a certificate, but couldn't install it.
[CERT] PKCS12_parse failed: error:23076071:PKCS12 routines:PKCS12_parse:mac verify failure
[HttpClient] HTTP error requesting GET https://plex.tv/api/v2/devices/7f997400a1a9672a4dca80010d1ccaaxxxxxd7a8/certificate/subject (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
ERROR - [HttpClient] MyPlex: Error -6 requesting XML from: https://plex.tv/api/v2/devices/7f997400a1a9672a4dca80010d1ccaaxxxxxd7a8/certificate/subject
ERROR - [CERT] CERT: Error acquiring new certificate: error fetching Subject
WARN - [CERT] MyPlex: Invalid connection URL '192.168.1.2'.
these messages repeat 100x per second, coredns pod gets busy. The plex address:9443 gives "bad gateway" text.

 

[Samuel Tai]

@appliance, have you configured DNS servers and a default router under Network->Global Configuration?

 

[appliance]

@appliance, have you configured DNS servers and a default router under Network->Global Configuration?

it's via DHCP, but i configured it also there, it doesn't make difference. NAS can access DNS and internet.
i changed back from ClusterIP to Simple, but it won't start now and app events claim different change: "ClusterIP -> LoadBalancer". Error "0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports." and volume not mounted. So i switched to NetLoader, and then back and now it's loaded. But with the settings "ClusterIP".
Also before this UI forced me to set "Node port" despite not correct for ClusterIP, that was fixed by [ ] unchecking advanced options.
-> More than often, UI doesn't save settings so better reapply. reapply.

so it looks like i have this dns issue also
-> ndots were needed to access Plex on PC
-> sync traeffic https port number to wan/vpn port was needed to access Plex on other LAN and WAN machines
- no other access is possible (LAN IP:32400 etc)

 

[somewhatdamaged]

I was using the official Plex app which worked fine, i then moved to TrueCharts Plex and experienced the same issues, server not showing as available etc. Switched back to the official app and its working again, exact same setup. No remote access setup required as its all being used over the local LAN

 

[nomb]

Yea I've had nothing but issues with TrueChart apps that need to broadcast out. Plex, syncthing, etc. It's a real shame.
My solution was (I'm running ProxMox -> TrueNas -> TrueNasDocker) to move apps that need to broadcast out to the proxmox layer.

 

[odignal]

So, you need to tell your client to connect to it directly on http://ip.address.of.plex:32400

To be specific, this must be configured under "Container Configuration -> Image Environment -> Advertise IP". https could also work, if you configured it. And if you want to make the server available from the internet, I guess (did not test) you must use your external URL including your forwarded port, like "http(s)://your.external.domain:32400". Unfortunately, the input field is mislabeld as Advertise IP instead of Advertise URL, and the help text could contain an example URL :)

 

[bjenning04]

I was able to resolve my issues by editing the active Plex application and checking the box for "Configure Host Network". I believe I had opted to leave it unchecked after watching various setup videos and not seeing anyone check it (My Mistake).

Steps:

View attachment 55096

View attachment 55097


Thank you @truecharts & @winnielinnie for fielding my questions!

Omg, how dumb. After an hour of beating my head against a wall, this was 100% my issue.

 

[grapes17]

I was able to resolve my issues by editing the active Plex application and checking the box for "Configure Host Network". I believe I had opted to leave it unchecked after watching various setup videos and not seeing anyone check it (My Mistake).

Steps:

View attachment 55096

View attachment 55097


Thank you @truecharts & @winnielinnie for fielding my questions!

Thank you thank you thank you!

I had this exact same issue, and it's been bugging me all week. I finally did a search, landed here, and your answer is the one that solved my issue.

 

[kwilas]

I was able to resolve my issues by editing the active Plex application and checking the box for "Configure Host Network". I believe I had opted to leave it unchecked after watching various setup videos and not seeing anyone check it (My Mistake).

With the official Plex app on TrueNAS Scale, the above also resolved my remote access errors. I do have a port forward to the host configured on the router.

 

[robo555]

I was able to resolve my issues by editing the active Plex application and checking the box for "Configure Host Network". I believe I had opted to leave it unchecked after watching various setup videos and not seeing anyone check it (My Mistake).

Steps:

View attachment 55096

View attachment 55097


Thank you @truecharts & @winnielinnie for fielding my questions!

Thanks, that tick box was my problem as well, and you post helped me solve it!

 

[The_Giefster]

I was able to resolve my issues by editing the active Plex application and checking the box for "Configure Host Network". I believe I had opted to leave it unchecked after watching various setup videos and not seeing anyone check it (My Mistake).

Steps:

View attachment 55096

View attachment 55097


Thank you @truecharts & @winnielinnie for fielding my questions!

This was my issue as well. If you do not have "Configure Host Network" checked then plex listens on its Kubernetes IP rather than your local network IP.

I was using the truecharts plex app before and it worked straight out of the box. But I have had so many issues with truecharts updating apps and crashing Kubernetes. So I ditched them and stuck with the official app.

 

[chri5]

I have had so many issues with truecharts updating apps and crashing Kubernetes. So I ditched them and stuck with the official app.

Same here, I am getting tired of my server turning into a dumpster fire after updating truecharts apps.