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?

  • legoraftOPEnglish
    1•9 months ago

    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.

      • @moonpiedumplingsEnglish
        1•9 months ago

        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.

      • @[email protected]English
        1•9 months ago

        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)

    • @[email protected]English
      1•9 months ago

      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.