Can't access containers remotely
Can't access containers remotely
Hey everyone. So I created a wire guard tunnel to my home network in order to access my are containers but all I can access is my router login page and one of my access point login page. All being in the same range is 192.168.3.1(router), 192.168.3.2 (access point and switch) and 192.168.3.10 server. My arr listen to their respective ports ie 8989 for sonarr etc. When I'm at home I reach them with no issues. What could be the reason I can't access them remotely?
You're viewing a single thread.
Wireguard only gets you to the endpoint. You need extra routes from there.
Post your wg config, and possibly the staticnroute table on the router. What kind of OS the router is using might help as well to understand possible firewall rules being a problem.
Solution may be as simple as adding a static route to the Wireguard subnet so your other hosts can find it.
To add, here's an example of my OpenVPN config addition to ensure 192.168.3.* is accessible over VPN
verb 5 push "route 192.168.3.0 255.255.255.0 vpn_gateway"OpenVPN does routing a tad differently, but same point applies. Network clients need to know where to go to find a route that isn't part of the home subnet they are joined too. With containers in the mix without bridging, the host needs to know that the WG subnet can be found at the router.
Ah makes sense. I'm using a Mikrotik router and implemented the Back to Home function which automatically creates the tunnel and all firewall configs. Supposedly it's like me being in my home network but I need to look into your suggestions.
That may look fine from your router's perspective, but if your network clients don't get an updated routing tables, they won't know or possibly accept traffic from the new subnet on the VPN.
Solved. All I needed to do was route the Back to Home (wire guard ) address list to a table for the server. 🤙