Honestly it couldn’t be simpler. Look at wg-easy docker container. You’ll be up and running in 10 minutes.
Comment on Access home server from anywhere
jaykay@lemmy.zip 10 months agoMmmmmm, tunnels sound boring haha I might try figuring out wireguard. Do you have any trusted guides on it? Or should I just google :P
sunbeam60@lemmy.one 9 months ago
bless@lemmy.world 10 months ago
Good thing about wireguard is it’s really simple. Google should get it done, if you get stuck send me a DM. I started with basic wireguard, I now run firezone in docker as I like the frontend.
jaykay@lemmy.zip 10 months ago
(I’m gonna copy what I said in another comment lol)
I don’t know if I’m shooting myself in the foot by trying to do in docker for now or not, but I’d rather do that before I do it on bare metal. It seems to work already, as I can see that my IP changes on my phone when I access it. Hell, I can even access my routers’ dashboard. However, I still can’t access the services on the server (by IP, like 192.x.x.x:8989), which I can access if I’m on Wi-Fi. So I’m trying to figure that out. Any ideas?
bless@lemmy.world 10 months ago
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@lemmy.zip 10 months ago
Yup, run journalctl and I can see ufw blocking requests. Now just need to figure out how to allow it