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?

  • drktEnglish
    2·
    11 months ago

    deleted by creator

    • momsi@lemmy.worldEnglish
      21·
      1 year 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)

      • legoraft@lemmy.worldOPEnglish
        1·
        1 year ago

        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

        • momsi@lemmy.worldEnglish
          1·
          1 year ago

          Then you would need to put that, and only that IP in the allowed IP section.

          • legoraft@lemmy.worldOPEnglish
            1·
            1 year ago

            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.

            • momsi@lemmy.worldEnglish
              2·
              1 year ago

              Can you post your config of the client? Remember to redact sensible information.

              • legoraft@lemmy.worldOPEnglish
                1·
                1 year ago

                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 = 25
                • momsi@lemmy.worldEnglish
                  2·
                  1 year ago

                  Two 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…

                  • legoraft@lemmy.worldOPEnglish
                    1·
                    1 year ago

                    yeah tje 192.135.163.0 is changed, originally it was 192.168.0.1/24 iirc. Weird that there isn’t anything wrong, because when.I use the internal IP of the cockpit machine with the port the cockpit instance is on, it doesn’t show anything. Thanks for the help tho!

    • moonpiedumplings@programming.devEnglish
      1·
      1 year 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.