Selfhosted

60451 readers

900 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

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

submitted 2 years ago by legoraft@lemmy.world to c/selfhosted@lemmy.world

11 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 4 points 2 years ago (2 children)

Probably it would be much easier for you to setup tailscale. Just install it on the system you host the other services, install on the other end and use the tailscale ip. It should require minimal effort to set up with the added benefit of not having ports open, and way easier maintaining.

As for wireguard, the allowed up section tells what ips should be routed through the tunnel, it's not that difficult, but hard to wrap your head around at first. A friend of mine also used to use the Fritzbox Implementation of wireguard and I remember you need to specifically setup what clients you want the tunnel to have access to.

Have a look at tailscale.

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

[–] decta@feddit.nl 2 points 2 years ago

this.