You do, it’s in the web client log above. You masked it out.
Well - the hostname and URL, rather.
(Works without firewall, breaks with firewall … I mean … I think I know where the problem is … this might be better suited to support from the firewall people.)
The only IPs showing in the log are:
#3 is a Hurricane Electric ip which I would guess is one of the indirect IPs used for the plex.tv.
I cannot access https://184.105.148.99:32400/web
I do see some CGNAT IPs, but those may be mine.
What error?
But you can access it when NOT behind the firewall?
Look for firewall logs.
Is it in a fully transparent mode?
Is it :32400 or :8443? His appears to use :8443 from the previous log snippet. And that’s not the same address as from the log snippet - 89 vs 99.
https://184-105-148-89.{GUID}.plex.direct:8443
I’m currently bypassing the firewall trying to find his public IP - I did ask him as well
:32400 - Can’t connect
:8443 - Unable to establish a secure connection
I highly doubt his IP is 184.105.148.* - I’ve seen four or five addresses in the same range which would make me think its an actual IP used by the plex.tv backend systems.
Also - I’m pretty sure his ISP isn’t Hurricane Electric 
Ok, I have his public IP and cannot browse to port 32400 or 8443
Both are ‘not responding’
I did ask and his reply was ‘plex says :32400’
Ahh, I agree! I think 184.105.148.89 is a Plex Relay address. (Working on confirming that myself.)
Do you see his actual public address in the list of connections the Web Client tests? If you don’t, then his server may not have Remote Access set up correctly.
I believe that if any Plex Relay addresses are present, that’s a sign that his server doesn’t have Remote Access set up correctly. I believe Relay addresses are only registered when direct Remote Access isn’t functional.
If he wants to get involved we can investigate what addresses his server is actually registering. He can get his token and view this URL:
https://plex.tv/api/resources?includeHttps=1&X-Plex-Token=TOKENHERE
So I see two issues -
Did you attempt connecting to the full address listed in the Web Client log?
Does it behave differently when NOT using the Firewall?
If the behavior is different with the firewall in place, what logging or diagnostics are available on the firewall?
Perhaps the firewall is doing some form of HTTP/HTTPS inspection, or geo filtering, or DNS filtering, or just general firewall bullshit.
I think he’s working on it. I told him it wasn’t working then it stopped working even via relay outside the firewall. I’ll wait to hear back from him to verify he has his Remote Access is set up correctly.
Both issues seem correct.
I haven’t tried #2, will try when its back up on his end. I can run a packet capture on the firewall, and there are standard ACL monitoring abilities.
Just to confirm - yes, that’s Plex Relay.
Did you make any progress? I’m just curious to learn if it’s a firewall issue or was a coincidence with things in their end.
He did ‘remember’ that he had a firewall in the way. Checking to see if he fixed it.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
