VPN connects, but the home server’s local address still fails
A NAS is running a and several other home services. A family member received a VPN key so they could reach the from outside the home, but the and port still give a network error after the VPN connects. Changing Windows rules seemed to fix it once, but the same error came back the next day.
The connection is using the real and port, not a local hostname. The setup uses afraid DDNS, wg-easy, and .
Key points
- A NAS is hosting a and other home services.
- A family member can connect to the VPN but cannot reach the and port.
- The failure appears as a network error, not as a VPN login problem.
- A Windows change helped once, but the problem returned the next day.
- The setup uses afraid DDNS, wg-easy, and .