Server Version#: 1.43.2.10687
Player Version#:
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
I haven’t had a problem in forever. Nothing has changed. User text about an hour ago and said they couldn’t connect. Went into the settings and it was green and connected. Couldn’t find anything wrong so I did an update in case that we the cause. Update went through fine. Then it started to show the Not available outside message. I’m on AT&T BWG320-505 and 3 Deco’s for wireless in the house. I’m not sure the update caused it since the user said he couldn’t connect and he has in the past without issue. It’s irksome only because nothings changed.
Don’t really know where to start. I disabled it once and reenable it and it went green for a few seconds then flipped to red.
If it shows it’s reachable, check your Plex Media Server.log and the numbered rollover files for any certificate errors. CSR: 429 or other certificate errors may require someone from Plex to reset your certificate.
I’m a relative newbie. Had a double NAT problem over a year ago that took me a week to resolve with some amazing help on this forum. Still, it basically has always just worked.
I’m not running a VPN. Port is 32400
Had to google how to get the log. I downloaded it and it’s a 3.4 mb file.
Would not know what rollover files are or what a certificate error looks like.
Then your forwarding rule is no longer valid, for some reason.
You mentioned being DoubleNAT in the past. Did you check if those settings/changes you made to deal with that reverted? Maybe AT&T updated your gateway and passthrough settings got deleted/reset?
Assume you setup the forwarding on the deco previously? If you go into the deco, does it still report your WAN IP as your public ip, or is it showing a 192.x or 10.x IP as the WAN IP? This would indicate the passthrough is no long valid on the AT&T. If it does show your public IP as the WAN IP, is your forwarding rule still valid? Pointing to your server IP and the port you set in plex?
Plex is utilizing and enforcing secure connections. As such you need working DNS that can resolve your local ip’s and well as rebind the server to a generated plex.direct address to validate the clients. Getting the port forward and DNS will allow external clients to connect.
Whichever device hands out DHCP address and sets the DNS server ip’s, if you set the DNS to Cloudflare (1.1.1.1,1.0.0.1) or Google (8.8.8.8, 8.8.4.4) that will greatly help.
The BGW320-505 does not provide a user-accessible setting to configure or disable DNS Rebind Protection.
To bypass this limitation, users must configure their downstream router (such as an Asus or TP-Link) to point its DNS settings directly to external servers (e.g. A third-party provider like Cloudflare, Google), effectively bypassing the BGW320’s internal DNS handling.
Key workarounds include:
1.) IP Passthrough: Enable IP Passthrough mode on the BGW320 and configure the custom DNS settings on the connected router.
2.) Local DNS Servers: Use devices like Pi-hole or Unbound on the local network, ensuring the BGW320 does not interfere with DNS resolution.
3.) Disable DHCP: Turn off DHCP on the BGW320 and use a separate DHCP server to assign custom DNS addresses to clients.
When the double NAT came up it was when I switched from Xfinity to AT&T. The idea was to disable the AT&T box and have Deco X20 (mesh) continue as the router. I preferred this since the AT&T settings appear user unfriendly and I was happy with the Deco. Apparently the AT&T doesn’t really want to give up control. Anyway, spent a week with an AT&T guy and this forum. Both people were awesome. As I vaguely recall we ended up manually pointing the router to the AT&T address and it fixed it. I simply followed their instructions.
This lasted for a very long time but I still had some issues. In the end I caved and allowed the AT&T to be the router and changed the Deco setup to Access Point mode. It worked and has lasted for a very long time. All this happened in Feb 2025.
I’ve looked at the Deco and don’t see the WAN IP. The options become limited in Access Point Mode. I see all three Deco’s and their IP’s on the AT&T device.
I’ve read previously where AT&T updates their devices automatically. Since I did nothing it would be a likely culprit. I have the screen up for their device which has 12 tabs and each having it’s own sub setting. Not sure how to check
On the BGW320 the DHCP Server is enabled. On the Deco, in Access Point Mode the ‘Smart DHCP’ is enabled. Again this has worked fine for over a year but I’m not really sure which one is handing out the addresses. I would assume the BGW320 because the Deco should just be an Access Point. That was the thinking when the switch was made.
You’re likely going to have to redo your full setup and put the AT&T into passthrough mode and let the Deco handle everything, basically making the AT&T act as a modem/ont.
Before doing that, go to Firewall → NAT Gaming and screenshot and share what’s on that screen to see if your old rule is still valid. If your AT&T was handling the port forwarding, which it seems like it was, the rule would be there.
Your DECO wouldn’t show the WAN IP as your public ip since you didn’t use passthrough and used AP mode on the deco units.
Just a drop down with nothing added. A little scary to go back to something that was so difficult to resolve. I’m assuming there’s no way to simply set the port to work like it was before.
I’m now guessing that is what this means from pl_5309: “The BGW320-505 does not provide a user-accessible setting to configure or disable DNS Rebind Protection.”
OK, looks like there’s no rule for your ports anymore. I don’t have a guide. @FordGuy61 has some great guides on the forum, maybe you can search and find one of theirs. Just going off a picture I found online.
This all assumes you didn’t do passthrough originally, which based on your description, you didn’t.
Click “Custom Service”
Name it Plex
Set the range as 32400 - 32400
Set the base port as 32400
Set protocol to TCP
Click Add
Go back to the Firewall page, and click Add.
Select the Plex service you just created
Select your Server IP/Name from the second dropdown
This is another issue with using the AT&T gateway and not putting it into passthrough mode. If you are impacted by DNS Rebind Protection issues, you can’t change the dns servers since they keep it locked down. However, in this case, currently your server isn’t even visible externally based on the port test, so until that piece is setup, we won’t be able to identify if the DNS issue is also a problem.
Yes. Went through the steps you said. Added the port. Went back to Firewall and added. Assigned to the Server from the drop down. Then confirmed it from the link.
