overview for legoraft

Access local cockpit instance without port forwarding in c/selfhosted

[–] legoraft 1 points 2 years 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!

Access local cockpit instance without port forwarding in c/selfhosted

[–] legoraft 1 points 2 years ago (2 children)

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

Access local cockpit instance without port forwarding in c/selfhosted

[–] legoraft 1 points 2 years ago (4 children)

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.

Access local cockpit instance without port forwarding in c/selfhosted

[–] legoraft 1 points 2 years ago (6 children)

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

Access local cockpit instance without port forwarding in c/selfhosted

[–] legoraft 3 points 2 years ago

Thank you for the info! I'll take a look at tailscale and try to wrap my head around the wireguard thing. Thanks for the help!

Access local cockpit instance without port forwarding in c/selfhosted

[–] legoraft 1 points 2 years ago (11 children)

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.

6

Access local cockpit instance without port forwarding (self.selfhosted)

submitted 2 years ago by legoraft to c/selfhosted

17 comments fedilink

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?

google drive, getting away in c/[email protected]

[–] legoraft 2 points 2 years ago* (last edited 2 years ago)

I have used both internxt and skiff. Both are E2EE, but skiff does have an online editor somewhat like google drive, so maybe that's a bit better for online writing.

[openbox] custom ascii for neofetch in c/[email protected]

[–] legoraft 2 points 2 years ago (1 children)

do you have the dotfiles to that bar somewhere?

[openbox] custom ascii for neofetch in c/[email protected]

[–] legoraft 4 points 2 years ago (3 children)

that bar is amazing! What are you using?