Comment

Comment on Plex (or Jellyfin) + Pangolin help needed

Here is how the Pangolin resource is configured

Use the hostname that is reachable on docker instead of IP. I think in this case that would be plex (name of docker service/container(?))

Go to access logs in pangolin dashboard and try to find out at which level the problem occurs. Where’s the last spot you see your query? Pangolin? Newt? It disappears after newt? Your plex service logs something about the query?

source

Sort:hotnew top

marighost@piefed.social ⁨1⁩ ⁨week⁩ ago
I figured it out!!

It was simple. I just told Plex to allow the 172.18.0.0/24 subnet. It’s always something simple huh.

Thanks for pointing me at the logs. Sometimes it all looks like gibberish when you’re learning, then you stop and read and search. Have a wonderful evening! (and the 10000 years of excellent luck, too!)

source
marighost@piefed.social ⁨1⁩ ⁨week⁩ ago
The only logs from Pangolin are from me accessing https://overseerr.dom.tld. From Plex’s GUI console though, I get this:

Request: [172.18.0.2:46974 (WAN)] GET / (6 live) #18eb GZIP Signed-in Completed: [172.18.0.2:46974] 401 GET / (6 live) #18eb GZIP 0ms 464 bytes (pipelined: 1)

That 172.18.0.2 is the IP of the Newt container (that subnet is its bridge network, anyway). So it’s making some request to Plex and receiving a 401?

From Mozilla:

The HTTP 401 Unauthorized client error response status code indicates that a request was not successful because it lacks valid authentication credentials for the requested resource.

So what would cause Plex to throw a 401?
source