Can't Claim Server (UnRaid)...Possible problem with AT&T?

Server Version#: 1.40.4.8679 Says Updated Available Please Update Manually (Listed under Server-General at myip:32400/web)

Player Version#: 4.135.1 (Listed under Plex Web at app.plex.tv)

Further Information: My ISP AT&T, I have Fiber. My gateway is the BGW210-700.

This has been driving me absolutely bonkers since Monday, July 29th. Some time between 3pm PDT and 7pm PDT, I can no longer access my Plex Server over LAN or remotely. I did not change ANYTHING in my network, server or Plex from when it was working to when it stopped.

It’s fairly well documented that people have had a slew of issues running Plex when they are using an AT&T Fiber Gateway. The only thing that I had to configure 2 years ago when I initially set up Plex on my network, was opening port 32400 in my AT&T Gateway. I did that in order to get Remote Access to work. Local had already been working. After opening the port 2 years ago, I’ve never had a problem.

I have troubleshot this with a Network Engineer friend who is a lifelong Plex user and he is also stumped and has never seen this before. I am very green to all of this, but I trust his advice and knowledge. He believes this is an issue with AT&T.

Things we have discovered that are strange:

  • I cannot access plex.tv/claim while connected to my home network regardless of what device I try it from. I have tried to connect to plex.tv/claim from my laptop, my wifes laptop and my phone. On both laptops, I have tried from 3 different browsers both normal as well as incognito/private. We also tried to claim the server inside the docker container’s Console utilizing the claimpms.sh file…When checking the logs, the container gets hung up on verifying the token.

  • When I disable wifi on my phone, or use my phone’s hotspot for wifi on my laptop, it immediately loads plex.tv/claim

  • Also strangely, I lost access to my work unions website from my home network around the same time. Since then, I also noticed I can’t access ubuntu.com. Ubuntu, my union and Plex.tv/claim all TIMEOUT.

Things we have tried to fix this:

First Big Fix we tried:
I configured a Pepwave Mobile Router with my simcard in it. I set the router to match my AT&T Gateways IP and subnet. I connected the Mobile Router to my server via ethernet and connected to my laptop via wifi.

THIS WORKED! I was able to bring my server online, Claim my server in the WebUI and play my server’s media on my laptop (over LAN).

Next, I hotswapped my server’s ethernet cable from the mobile router to my AT&T. Gateway and connected my laptop to the AT&T Wifi network…

THIS WORKED! I still had access on my laptop to the Plex server and was still able to play media from it.

At this point I thought we had solved it; however, when I opened Plex on a local client device (Chromecast with Google TV connected over ethernet to my AT&T Gateway) it said my server was OFFLINE.

Sad Face…

Second Big Fix we Tried:
We configured my AT&T BGW210-700 into IP Passthrough mode and used my Pepwave MAX BR1 as the router for my home network.

My network engineer buddy went through every setting of this with me to insure it was done correctly and we were able to successfully passthrough everything to the Pepwave router; however, I STILL couldn’t access plex.tv/claim or my union’s website.

At this point, I factory reset everything just to get back to a state of normalcy. I factory reset my AT&T BGW210-700, and also “reset” (just powered it off and back on) the A&T ONT box.

Not shockingly, this also didn’t solve my problems.

Things I haven’t tried yet, but will get around to in the next 2 weeks:
One reddit post recommended setting the AT&T Gateway into “Default Server” mode instead of IP Passthrough and configuring that. My engineer buddy said he doesn’t think that will present any different results than when we tried the IP Passthrough, so we haven’t tried it.

I will be purchasing a dumb switch and seeing if I can put the dumb switch between the ONT and the AT&T Gateway. In essence, I’m going to try and trick the network so it uses the AT&T Gateway only to Authenticate the ONT, but then will use my personal router for everything else…I have no idea how this works, but we’ll see.

On Thursday, I called AT&T:
ANYWAY, after spending 26 actual hours with my buddy trying to trouble shoot this over a 3 day period, I called AT&T on Thursday to see if they could provide any insight. I explained the issues to the AT&T Technical Support Agent and ended with, “Basically the issue i’m running into is that I can’t access plex.tv/claim or icg600.com from my home network”

She had me try a couple things and on her end she ran a ping and trace route to each of the sites. What she told me was able to access both sites from her network, but the Trace Route times out.

She said at this point there is no further help she can provide. I asked if I could open a claim or a ticket for this to be escalated to their engineers and she said, “No. We don’t do claims/tickets and we don’t have engineers in support. It’s basically a luck-of-the-draw with who answers your call from Tech Support and what their knowledge base is.”

I asked what she thinks my next course of action is, because I really don’t want to have to switch my ISP to Spectrum (I still have nightmares from dealing with them), but that’s seeming like the only option.

Her response was that I should reach out to the hosts of both websites and see if they have my IP address blocked or all AT&T IP’s blocked for some reason…I reached out to my union’s webadmin and the “IT Dept” is looking into it, but I haven’t received a direct response yet. I know Plex doesn’t have a “technical support” email or phone number, so I figured posting here was the next best thing.

If you’re still here, thank you for taking the time to read this novel and I will be eternally grateful for any help or insight you can provide!

It is most likely either DNS problems or AT&T problems.

Connect the PC to the gateway with an Ethernet cable.
Disconnect everything else.
Reboot the gateway.

If you still cannot get to the desired sites on the Internet then call AT&T. The gateway may be faulty or they may have something misconfigured in their network.

You can also test DNS and see if it is working correctly. Use nslookup and see if you can resolve the IP addresses and possibly ping them (plex.tv sites do not respond to ping).

c:\>nslookup apple.com 192.168.1.254
Server:  dsldevice.attlocal.net
Address:  192.168.1.254

Non-authoritative answer:
Name:    apple.com
Addresses:  2620:149:af0::10
          17.253.144.10

c:\>nslookup apple.com 8.8.8.8
Server:  dns.google
Address:  8.8.8.8

Non-authoritative answer:
Name:    apple.com
Addresses:  2620:149:af0::10
          17.253.144.10

c:\>nslookup apple.com 1.1.1.1
Server:  one.one.one.one
Address:  1.1.1.1

Non-authoritative answer:
Name:    apple.com
Addresses:  2620:149:af0::10
          17.253.144.10

c:\>ping 17.253.144.10

Pinging 17.253.144.10 with 32 bytes of data:
Reply from 17.253.144.10: bytes=32 time=4ms TTL=57
Reply from 17.253.144.10: bytes=32 time=4ms TTL=57
Reply from 17.253.144.10: bytes=32 time=4ms TTL=57
Reply from 17.253.144.10: bytes=32 time=3ms TTL=57

Ping statistics for 17.253.144.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 4ms, Average = 3ms

c:\>

Engineering Buddy also agrees it’s DNS problems or AT&T problems. But I guess what I’m trying to figure out, is how to prove to AT&T it’s their problem.

Here’s what I get when I nslookup and ping the websites that aren’t loading for me as well as apple.com from inside the UnRaid Console.

root@Tower:~# nslookup icg600.com
Server:         192.168.1.254
Address:        192.168.1.254#53

Non-authoritative answer:
Name:   icg600.com
Address: 70.47.211.121

root@Tower:~# ping 70.47.211.121
PING 70.47.211.121 (70.47.211.121) 56(84) bytes of data.
^C
--- 70.47.211.121 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9228ms

root@Tower:~# nslookup plex.tv/claim
Server:         192.168.1.254
Address:        192.168.1.254#53

Non-authoritative answer:
Name:   plex.tv/claim
Address: 143.244.220.150

root@Tower:~# ping 143.244.220.150
PING 143.244.220.150 (143.244.220.150) 56(84) bytes of data.
^C
--- 143.244.220.150 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9223ms

root@Tower:~# nslookup apple.com
Server:         192.168.1.254
Address:        192.168.1.254#53

Non-authoritative answer:
Name:   apple.com
Address: 17.253.144.10
Name:   apple.com
Address: 2620:149:af0::10

root@Tower:~# ping 17.253.144.10
PING 17.253.144.10 (17.253.144.10) 56(84) bytes of data.
64 bytes from 17.253.144.10: icmp_seq=1 ttl=54 time=4.19 ms
64 bytes from 17.253.144.10: icmp_seq=2 ttl=54 time=3.69 ms
64 bytes from 17.253.144.10: icmp_seq=3 ttl=54 time=4.08 ms
64 bytes from 17.253.144.10: icmp_seq=4 ttl=54 time=3.86 ms
^C
--- 17.253.144.10 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 3.690/3.954/4.192/0.193 ms

Towards the end of my original post you’ll see I called AT&T on Thursday. They claim none of it is their fault and that it’s likely the Host blocking my IP or a block of AT&T IP addresses.

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