Server Version#: 1.40.0.7998
Player Version#: 8.31(1)
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
Sounds like your server and the Apple TV aren’t actually on the same network (subnet), are they?
Relays are only used for indirect connections. That means a connection considered as „remote“ by your server/client where your remote access setup isn’t working for that particular connection or not at all.
Are you able to connect to the server from other clients?
My plex server and ATV are on the same network connect via Ethernet. Subnet is same. I am able to access Plex server on mobile with “Enable relay”. same result (unable to connect) if I uncheck “Enable relay”.
Somehow Plex thinks you are not in the same network.
Set “Secure connections” under
Settings - Server - Network
to “Preferred”, if you have it currently on “Required”.
Then stop and restart Plex server.
What kind of router do you have?
Are there other network related devices in the network, like a DNS-based filter (Pi-hole, Privoxy etc.)?
Are you using a VPN?
Does your ISP provide you with settings to enable or disable “advanced security features”?
yes, its Preferred. and I am not on VPN. I have not change any setting for my router AXE1600 for a while .
I don’t have any device in my network like DNS-based filter (Pi-hole, Privoxy etc.)
Not sure for the last one “advanced security features”. ISP is Xfinity for years I am not aware of any change recently.
In fact, I have been using Plex for years and don’t see any issue until now.
Do you know if there’s a setting for “Rebind protection” on your router? If there is, allow an exception for plex.direct
Normally, this protection is a good thing. So one might prefer to have it enabled. It does prevent a host in your local network from getting assigned a domain name from the outside.
An attacker could use this to e.g. turn one of your computers into a banking website and then change the regular domain name of your bank to this device.
A better way than just an On/Off switch would be to allow a white list of domains which are allowed to be assigned to local devices.
Which, in Plex’s case, would be plex.direct. Your Plex server is automatically getting assigned a subdomain on this domain, so local clients can use this domain name to communicate with it.
I’d try this switch out. Disable it for a few hours, then reboot the client devices which had difficulties, and see if there is a change.
So you know at least where to take further action, once it is confirmed that DNS rebinding protection is indeed to blame.
2 Likes
I disabled Rebind protection yesterday, and this morning tested again, unfortunately. still can not access Plex server.
Look at the properties of the network connection of your Windows machine. Is it classified as “public”? If so, set it back to “private”.
sorry get back late. the network profile is Private.
What’s this “AI Cloud” in your router settings? Sounds like something to be switched off.
OK, Finally I am able to connect my Plex server from both Phone and Apple TV.
I didn’t change anything of my router setting, instead I updated the FIRMWARE. now everything is working. not sure anything changed for the FIRMWARE.
But I do see something from release note.
2023/12/18
New Features:
- Added new IPTV profiles, including Celcom, Celcom-TM, and UNIFI-Business+VoIP.
Bug Fixes and Enhancements：
- Fixed WAN connection issues.
- Resolved an issue that caused hostname errors in the DDNS service.
- Resolved OpenVPN server TAP mode issue.
- Added MTU setting for WireGuard client.
- Ensured consistent display of client status on the WireGuard server.
- Enhanced system stability when accessing the WireGuard server with DMZ enabled.
- Improved stability when enabling or disabling the WireGuard server.
- Optimized memory utilization and fixed an occasional server error when registering DDNS with an app.
- Corrected a bug encountered when adding a rule to the network services filter.
- Fixed connection in load-balance mode when both WANs have static IPs.
- Resolved USB path display issue in RE Mode.
- Improved VPN client internet accessibility with AiProtection.
Security Fixes：
- Fixed OpenSSL vulnerabilities.
- Upgraded to the latest dropbear version.
- Fixed a stack overflow vulnerability.
Honestly, it could have been a number of these.
Anyway, glad it worked out for you!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
