Legit?
LOL, i’ve spent so much time trying to stop the google and Roku chatter that it would kill me to have to try another DNS, which really only leaves my own (which is slow and not meant to host recursive), my ISP or Google.
So, this “indirect connection” I am now seeing from work, if I am understanding this correctly - for some reason I am now using the plex relay, is this correct?
If I point at my server as I used to (EDIT: REMOVED) be able to, it does not work. So, it seems like Plex is still messed up. Firewall on or off, the port refuses to be listened to by the Plex server and shows as closed on canyouseeme.
Oh, you are using a custom domain?
That doesn’t help at all in my experience. It introduces several more breaking points.
Are your cryptographic certificates for this domain up-to-date and properly imported into Plex?
Furthermore, if you want Plex cients to actually use this domain, (instead of Plex’s own *.plex.direct FQDNs), then you must also tell Plex that under
Settings - Server - Network - ‘Show Advanced’ - “Custom server access URLs”
https://support.plex.tv/articles/200430283-network/
The custom domain is NOT configured in plex, it’s just a standard A record so I can do email and host my weather station off my other server. So don’t even let that confuse the issue!
So, I now know why the servers are connecting - it’s via the relay. Plex (or windows) is still not listening to 32400 from the router. I’m going to install wireshark in the next hour or so and post back some captures.
Did you exempt plex.direct from DNS rebinding protection on your Pihole?
I take it you are familiar with https://support.plex.tv/articles/206225077-how-to-use-secure-server-connections/
and
https://blog.filippo.io/how-plex-is-doing-https-for-all-its-users/
?
Not using DNS rebinding (not an option on my router).
Yes, am familiar with those links.
Just grabbed Wireshark portable. Will initiate an inbound connection and see what is going on and post it back here. May need to go to devs.
If you are using pihole, then it would be located there. But I guess it is not an issue, otherwise you would have trouble accessing your server in the local network as well.
mkmorris:
I am having the same issue here. Stays green for about 4 seconds, then goes to unavailable outside your network.
I did a plexpass Web Update and the Windows 10 1903 update today…not saying that is the cause…but 4 days ago it was working; today I have issues.
I am right there with you
fiestadude
I am also having the same issue! I have tried to remove all the port forwarding setting and updated. Nothing is helping.
I can fix this by VPN’ing into my network from my computer, tablet or phones (work, personal). So for me, troubleshooting is done. I tried capturing traffic with wireshark yesterday but I just don’t have enough time to muddle through this and need to get back to work where they pay me to do the same thing and not troubleshoot someone else’s product.
It’s not pihole, and it’s not DNS Rebinding (that MUST be done in the router and can affect pihole, but it is not done in pihole itself (ref: https://discourse.pi-hole.net/t/why-wont-pi-hole-work-with-dns-rebind-protection-enabled/3142).
It’s not Cloudflare DNS (or at least, I highly doubt it is) as one would hope that a company using Cloudflare for their network (ref: https://www.plex.tv/en-ca/blog/plex-cloudflare-important-security-update/) would not have an issue with another one of their services and either or both companies would be pretty braindead if that were the case.
That said, if I find anything, I will note it here. For now, and for clarity, I am removing all personally identifiable information (URLs, etc) from the posts I have made above.
For what it’s worth, been having the IDENTICAL problem for 2 days.
Clients using the iOS app are able to still stream using the indirect connection, but besides that she’s toast. Goes green for a few seconds then unavailable. Can confirm port forwarding and all that good stuff is identical to how it should be and always has been.
Also for what it’s worth, I noticed my BitTorrent client won’t top like 4kb/sec with a 1gig internet connection right about at the same exact time as the Plex Server issues. Using it on another computer still on my same network doesn’t replicate the same problem. I have NO clue how that connects to it or if it makes any sense, but that’s what I’m experiencing.
I have the same issue after upgrade to 1.16.3.1402. Before of the upgrade, all runs ok. All options with my router runs equal than before upgrade. Obsiously that is an issue of the upgrade 1.16.3.1402, very severe. Unacceptable.
This topic was automatically closed after 90 days. New replies are no longer allowed.
