Selfhosted

40246 readers

1134 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Access local cockpit instance without port forwarding (lemmy.world)

submitted 1 year ago by legoraft@lemmy.world to c/selfhosted@lemmy.world

18 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] momsi@lemmy.world 1 points 1 year ago (5 children)

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

[–] legoraft@lemmy.world 1 points 1 year 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.

[–] momsi@lemmy.world 2 points 1 year ago (3 children)

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

[–] legoraft@lemmy.world 1 points 1 year ago (1 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

[–] momsi@lemmy.world 2 points 1 year ago (1 children)

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.world 1 points 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!

load more comments (1 replies)