Selfhosted

40296 readers

391 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 1 year ago

MODERATORS

[email protected]

102

Access home server from anywhere (self.selfhosted)

submitted 11 months ago* (last edited 11 months ago) by jaykay to c/[email protected]

83 comments fedilink hide all child comments

Hi, I know this topic has been talked about 70 thousand times but I’m still not sure.

I have home server on an intel NUC behind the ISP router. On it I have the standard arr apps, jellyfin, pi-hole etc etc. I would like to access them through a domain rather than an IP. So I set them up in docker, behind traefik, behind authelia and behind cloudflare. I am the only one that uses it.

Now, I’m worried about the security of it all. I’ve been searching here and there and I’ve read about cf tunnels, wireguard server, vps, vlan, OPNsense etc etc. I still don’t know what would be the most secure. Should I just stay with what I have?

EDIT: I'm not behind CGNAT

you are viewing a single comment's thread
view the rest of the comments

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

Hmm do a traceroute and see where it's dying. Can you ping inside IP of the tunnel on the wireguard server? What about outside?

What did you deploy in docker, firezone or basic wireguard?

Does your phone say connected and you see both incoming and outgoing packets? Is there a firewall in place on the wireguard host (ufw maybe)?

If you have nmap available you can also check port status.

[–] jaykay 3 points 11 months ago* (last edited 11 months ago) (1 children)

Yup, run journalctl and I can see ufw blocking requests. Now just need to figure out how to allow it

EDIT: Adding a rule "ufw allow from 192.x.x.x/24" fixed it, just need to find out if THAT's secure now lmao

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago) (1 children)

You can bound ufw rules to interfaces, so you can allow in only on the wg0 interface and not eth0 interface.

Glad it's working! I love wireguard!

[–] jaykay 2 points 11 months ago

I couldn't use the interface, as wg is in a docker container, but I used the container IP, and it seems to be working. Huge thanks! Now I can get rid of Cloudflare and related containers :D (just need to fix the homepage first, I'm not using IPs for services lol)