Selfhosted

44601 readers

2135 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 2 years ago

MODERATORS

[email protected]

OMV remote access (feddit.org)

submitted 2 days ago by [email protected] to c/[email protected]

15 comments fedilink hide all child comments

Hello,

recently I recycled my old laptop and started out with OpenMediaVault. After some initial difficulties I figured out how things work. Just to mention: I'm not an IT guy but can solve and figure out things. I want to have access to one or another self hosted services. But I'm a bit lost which approach and tools to use without exposing and making my NAS vulnerable on the internet.

Do you know any beginner friendly guides especially for OMV? I also want to understand what happens if and what my next action causes/can cause. So I don't just want to dumb follow a tutorial and that's it.

Thank you for your help and please let me know if you need any more details.

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

[–] [email protected] 3 points 2 days ago* (last edited 2 days ago) (1 children)

But I’m a bit lost which approach and tools to use without exposing and making my NAS vulnerable on the internet.

You're looking for a reverse proxy;

*.domian.dev {
        encode zstd gzip
        @jelly host jelly.domian.dev
        handle @jelly {
                reverse_proxy {selfhost_ip}:{port}
        }
        @ping host ping.domian.dev
        handle @ping {
                respond "pong!"
        }
}

Running caddy like this directly connects your jelly.domain.dev domain to your selfhost ip on a specific port. From within your selfhost you ensure that you're only allowing in the IP of the VPS, so no one can else can directly connect.

Works great. I use this myself. I have a local NAS (with media) and run a jellyfin server from my PC (to use my GPU for transcoding). The jellyfin server only allows 1 remote IP (my VPS), and local connections. The local jellyfin server can be accessed via my domain at jelly.domain.dev.

[–] [email protected] 2 points 22 hours ago

Thank you for your tip! Reverse proxy was one of the techniques I was referencing in my post. But somehow I didn't get how this thing functions. It's easier than some might think actually. But on the weekend I have to sit down and nail it down to a solution