Selfhosted

40731 readers

383 users here now

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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

Can't access containers remotely (lemm.ee)

submitted 2 weeks ago by [email protected] to c/selfhosted

9 comments fedilink hide all child comments

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 are viewing a single comment's thread
view the rest of the comments

[–] just_another_person 8 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

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.

[–] [email protected] 2 points 2 weeks ago (1 children)

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.

[–] just_another_person 2 points 2 weeks ago (1 children)

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.

[–] [email protected] 6 points 2 weeks ago

Solved. All I needed to do was route the Back to Home (wire guard ) address list to a table for the server. 🤙

[–] colonelp4nic 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

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"

[–] just_another_person 3 points 2 weeks ago

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.