Custom URL access issues since latest PMS update

Plex Media Server Remote Access
1

Server Version#: 1.25.6.5577
Player Version#: 1.25.6.5577

Hi Plex Support.

This could be coincidental, but since the last server update I have been unable to access my plex through my custom URL. This was installed around when you had the recent API authentication outage. I have this behind Cloudflare and it hits an NGINX reverse proxy. I have verified that the cloudflare proxy part is not the issue by disable the DNS proxy on my plex URL. I can access the server locally and through plex.tv. I can see that my firewall (pFsense) doesn’t seem to be the issue. Other proxied sites are working and I have checked the logs. The traffice definitely hits Plex throught the firewall.

When I access the custom URL it displays a black screen and very slowly it will then sometimes show me the plex logo but it never goes to the log in screen. I have seen some posts regarding removing the new cert in the cache. This did not work. I have also reset my password and forced it to sign out all sessions to create a new Plex token. I then re-claimed my server.

I have seen some support techs resetting certs on the Plex side. Are you able to please look into my account and see what needs to be done? Have spent 6 hours and I am not able to resolve this. Been searching everywhere and the solutions that worked for other people have not helped me unfortunately.

EDIT: Sometimes the plex android app eventually loads and I can play a video. It takes ages to load the video and will buffer.
Also finding this in the logs: Feb 27, 2022 21:46:32.657 [10704] DEBUG - CERT: incomplete TLS handshake from [::ffff:192.168.1.151]:51319: sslv3 alert certificate unknown

Thank you :slight_smile:

2

An update to this. I’ve had my certificate reset, tried downgraded to last version, tried setting up plex in docker to route another subdomain to it. Same issue.

I am wondering why I can access locally and through plex.tv but not via my subdomain. It was all working perfectly till the last update. Is there anything else that can be checked?

This is driving me insane!

Thank you.

3

I often find it helpful to draw a picture.

Is this correct?

    Client → Cloudflare → Nginx → Plex

I notice that I get a Cloudflare error Access denied when browsing to your URL.

The logs don’t indicate any problems with the Plex SSL certificate.

What is 192.168.1.151? The Nginx server?

4

Hi Volts,

Yes this is correct:
Client → Cloudflare → Nginx → Plex

I also host another service with a Web server over cloudflare, proxied with SSL and there are no issues at all. Serious head scratcher. I am wondering if plex has corrupted in some way. Maybe I need to completely blow away the server and start again, then again the new instance I tested in docker didn’t work so maybe that’s not a good idea. I have changed the cloudflare firewall rules to allow you. Please check your pm as well :blush:

When there are no cached logins the plex page loads instantly. As soon as I authenticate with plex.tv the whole process fails. It just sticks on loading. The issue seems to be between authentication to plex.tv and the server after log in. Any auth logs on your end? I also run pfsense and have added the DNS rebind override under the resolver settings.

Edit: 192.168.1.151 was the desktop I was using to access through the cloudflare url. Same issues when off network.

5

Solution: Migrate from Windows 10 OS to Ubuntu. Bit drastic but it works!
Not sure what the issue was, possibly recent updates broke something.

6

How’d you fix your car’s transmission?
Oh, I bought a new car.

:slight_smile: :slight_smile:

1 Like
7

Hi Danny251,
please don’t mark this as solved as this issue still exists when running PMS on a windows machine and it would be useful for others to view this post for an actual solution.

I for instance have been having issues accessing plex via third-party apps (Overseerr & Tautulli) through my reverse proxy since server version 1.25.6.5577. Reaching my plex server through a web browser works without a hitch as it did before.
Now instead of simply using “subdomain.domain.tld” in Overseerr and Tautulli to be redirected to the media on my PMS I have to use “subdomain.domain.tld/web/”.

Something has definitely been broken of late… Just don’t know what yet (Windows 10 or PMS or plex.tv routing/DNS). :slight_smile:

Would be great if someone else could confirm this to get some support going.

8

That may or may not be a related issue. :slight_smile: do you think Plex has changed something?

Can I encourage you to create a post sharing the details of your system, the configuration of the proxy, and what behavior you’re experiencing?

Sometimes the different views and requirements of different clients can be complicated - remote web clients vs. remote Plex apps vs. local Web clients vs. local Plex apps vs other clients on the same server.

I like pictures, because I’m slow -

This client, uses this URL, traffic flows through this router, to this proxy, where it is rewritten to this new address, and sent to this server.

But this other client uses this IP address and accesses the server directly.

9

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