Hi, I’ve recently built myself my first server to host a minecraft server. I manage this server through cockpit, which isn’t port forwarded.
Now I’m going to move to a different place, but I want to keep that server at this house because of more stable internet and me moving to a smaller space, but I don’t know how I could access this server remotely.
I’ve already tried adding a vpn to my router, but when connected, I still can’t access my cockpit dashboard. Am I doing anything wrong or do I need to port forward to access my cockpit instance remotely?
Hi! I’ve done a bit more thorough googling, because of you I knew what to look for a bit better. I have a wireguard vpn on my fritz box router enabled, which allows me to connect to the vpn from my laptop.
I’ve read up on how to acces local devices and I found something about adding an IP to the “AllowedIPs” section, but I don’t really get which IP I should add.
deleted by creator
While not what OP wants, this is what I want, but it isn’t working for me. I am trying expose a subnet behind nat, to a public server. I am currently testing this by attempting to expose the vlan created by libvirt on my laptop to my public vps. I followed the linked point to site guide, and ironically, the virtual machines created on my laptop can access the wireguard subnet, but public vps cannot access the virtual machines? (the guide said that it would be the opposite without the iptables nat/masquerade rules) I am guessing because I am doing this somewhat backwards, where the device exposing the lan is behind nat, whereas it is the other way around in the guides that I have seen.
This would tell the peer with this configuration to send all traffic for the whole 192.168.1.0/24 through the tunnel, not sure that is what OP wants. (Didn’t look at the link though)
The best thing would be if I can just type the local IP of my server in the browser and just get routed to my server when I have the VPN enabled
Then you would need to put that, and only that IP in the allowed IP section.
I’ve tried this, but it didn’t work. At home, I can access my cockpit server by typing the machines IP and port 8080. When I try this on the VPN though, it doesn’t work. I can access my routers settings, but not the server.
Can you post your config of the client? Remember to redact sensible information.
Here is my config file (I redacted the keys and changed up IP’s just to be safe):
[Interface] PrivateKey = [Redacted] Address = 192.135.163.201/24 DNS = 192.135.163.1 DNS = fritz.box [Peer] PublicKey = [Redacted] PresharedKey = [Redacted] AllowedIPs = 192.135.163.0/24,0.0.0.0/0 Endpoint = 9xs.myfritz.net:51609 PersistentKeepalive = 25Two things:
192.135.163.0 is not a private IP… the private range would be 192.168.0.0/16. I guess that’s because you changed the IPs bit maybe better check that
And 0.0.0.0/0 means “all IPs” so it doesn’t really make sense to put the other one there.
Other than that I don’t see anything wrong…
The folks replying here have pretty much hit the nail on the head. Adding your home network to that AllowedIPs line in the confit file should do the trick.
Someone else mentioned Tailscale, which would be another great option—with a web UI to dial in routes.