Hoping this isn’t just me. I’ve reset my AT&T gateway to defaults and tried multiple devices wired and wireless. But no matter what I can’t get https://plex.tv. Specifically any request to plex.tv on port 443 times out when I’m on AT&T U-Verse fiber internet. Works fine on AT&T cellular network and on my Comcast internet. Only appears to be blocked on AT&T home internet.
Anyone else experiencing this?
Can you set a different DNS server? Try Google’s (8.8.8.8)
I already don’t use AT&T DNS. The IPs for plex.tv resolve correctly, but they are all unreachable on port 443. All devices trying to connect to it time out.
Yikes, at least I’m not the only one. Thanks for the link!
Same here. AT&T are blaming it on a DSLAM server issue, but I’m not buying it.
Are you still experiencing the same issue? I configured a VPN connection on my plex server as a workaround until the issue is resolved.
Can you run a tcptraceroute to port plex.tv:443?
Same here, below is the traceroute, removed some of my IPs.
I will say I have a 172.x.x.x IP from ATT and it looks like other services are having issues with that block.
That’s highly unlikely.
Looks like the traffic blackholes after the Level3 EU hop.
I am on ATT Fiber and all is well. East Coast US.
# dig plex.tv
; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7_5.1 <<>> plex.tv
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4141
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;plex.tv. IN A
;; ANSWER SECTION:
plex.tv. 4 IN A 52.31.211.151
plex.tv. 4 IN A 52.18.254.79
plex.tv. 4 IN A 54.154.198.3
plex.tv. 4 IN A 52.50.215.159
plex.tv. 4 IN A 54.171.147.115
plex.tv. 4 IN A 52.16.101.236
plex.tv. 4 IN A 52.50.147.131
plex.tv. 4 IN A 54.171.218.244
;; Query time: 1 msec
;; WHEN: Tue Mar 19 22:08:18 EDT 2019
;; MSG SIZE rcvd: 164
Well, whatever is happening, it’s on their end.
I did a traceroute and received the exact same thing.
What are the first two octet values of your public IP?
Definitely not a DSLAM issue. That’s a device that serves a neighborhood or large area. It’s also for DSL, not fiber.
172.1.x.x
172.7.x.x
Someone somewhere along the way has inadvertently/advertnantly blocked public IP space in the 172.0.0.0/12 from passing traffic. This is not on your end nor Plex’s end. This is somewhere in the middle.
You will have to wait it out. Unfortunately this problem is going to be owned by a high level backbone network engineer that neither you or AT&T Customer support will have direct access to. It will have to be escalated. The good thing is that its not impacting just Plex users. It seems to be impacting Microsoft Office 365 users as well–so I am sure its already been escalated.
Some AS is probably misidentifying that traffic as RFC1918 address space via some fat-fingered ACL or fw rule…
