Selfhosted

40739 readers

351 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

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Can't access containers remotely (lemm.ee)

submitted 3 weeks ago by WeAreAllOne@lemm.ee to c/selfhosted@lemmy.world

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

[–] colonelp4nic@lemmy.world 2 points 3 weeks ago* (last edited 3 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@lemmy.world 3 points 3 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.