A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
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.
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. 🤙
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.
I'm not familiar with wireguard but I use Tailscale and it works really well
Can you ping the server through your tunnel? Maybe try a traceroute to see if it gets through your router correctly.
If this does work, check if the arrs have some "restrict to local network" setting.
If not, I'd check the firewall logs on your router to see if it is blocking the connection.
You can set up one device to do masquerading and forwarding then you can see entire lan