[SOLVED] Everything Reaches Server EXCEPT app.plex.tv

Plex Players Desktop Players
1

Server Version#: 1.16.4.1469
Player Version#: 4.0.1

I’m running Plex via docker on Unraid. Using pfSense and have a static IP. Literally every player can reach plex via secure connection except Plex web. I can even access securely through my domain at “plex.mydomain.com.” Roku, Android, iOS and UWP app are all connecting securely.

pfSense has the DNS resolver connection set correctly. NAT port-forward is working correctly.

I’m generally ok getting on the server, but I’m assuming its a simple setting that I missed. Last I remember, I was good to connect through app.plex.tv before update to 4.0.1 (or 4.0.0 if I missed that).

2

What happens if you go to plex.tv and hit the “Launch” button?

3

image
image.jpg775×368 65.5 KB

Plex.tv and Launch is how I access Plex web. Everything is unreachable unless I go through an Insecure Connection - which I don’t really want to do.

4

Have you added your custom domain to:

Settings/Network/Custom server access URLs

5

My custom domain is in there and access through “plex.mycustomdomain.com” is working well and presenting a secure connection.

Secure connections is set to “Preferred” as well.

6

I dunno then, its probably related to Docker which I don’t use.

7

It just occured to me that when I hit my custom domain, the web (embedded) version is generally older than the hosted version (app.plex.tv)

Currently:
Hosted - Version 4.0.1-ece7064
Embedded - Version 3.104.2-1b12c68
(this is equal to hitting your localip:32400/web as well)

I don’t know if something changed but you could check yours.

8

Can you please PM/Post web client logs? It’s difficult to tell what might be happening from a screenshot alone

9

Where do I find the logs for the webclient?

10

Settings / Troubleshooting / Download Logs

They will all be in that .zip file

11

The best way is to go to the Debug page in settings, ensure it’s set to “Enabled” Go back to the home screen, refresh the page, then go back to the debug page and click the “You can view the debug logs here” link.

This redacts your token, but if you’re concerned about other identifying info like IP or machine identifier then there’s not much you can do aside from manually scrubbing those, and depending on how you do that it could reduce the usefulness of the logs

Feel free to PM me the output of that page

12

Welp - as I suspected, it really was a simple fix. I was combing through the console and noticed a bunch of random strings and UI that were missing or being blocked. At that point I caught out of the corner of my eye that Privacy Badger had a number of things also being blocked. Somehow, all FOUR of the browsers that I was testing on yesterday had PB installed. Disabled the plugin for that site, and I’m good to go.

Of course it was that. Plex Web is working fine now. Sorry for the hassle and theank you both for the help!

1 Like
13

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