48
Reverse proxy (self.selfhosted)
submitted 6 months ago* (last edited 6 months ago) by mfat to c/selfhosted@lemmy.world
39 comments fedilink hide all child comments

I have an openwrt router at home which also acts as my home server. It's running a bunch of services using docker (Jellyfin, Nextcloud, etc.)

I have set up an SSH tunnel between my openwrt router and VPS and can access jellyfin successfully.

I understand that I need to set up a reverse proxy to access multiple services and have https.

But I'm confused if I should set up this reverse proxy on the VPS or on the router itself. Is nginx the easiest option? Should i add subdomains in cloudflare for every service?

Pease don't recommend vpns since they are all blocked where i live (wireguard, tailscale openVPN, etc.) I'm limited to using ssh tunneling only.

Thanks

you are viewing a single comment's thread
view the rest of the comments
[-] just_another_person@lemmy.world -4 points 6 months ago* (last edited 6 months ago)

Firstly...why are you routing your home stuff through a VPS? I'm confused on what is happening here.

If you just want to access your things remotely, setup a VPN server on the router, and connect to it that way. You also dont need a reverse proxy or SSL if you're already accessing things over a secured connection. Where did you get this info from?

[-] Felix_lm22@sopuli.xyz 2 points 6 months ago

Please read the post man, all VPNs are blocked on the protocol level

[-] refalo@programming.dev 0 points 6 months ago

That's not how VPNs work, you can't just "block all of them". I think OP just needs to use a pure-TLS VPN solution (like SoftEther) or an obfuscated one like shadowsocks/obfs from a not-super-well-known provider (or self-host it on a VPS/etc.) and they should be golden.

[-] Felix_lm22@sopuli.xyz 2 points 6 months ago

They sniffing the traffic with DPI and block vpn tech on protocol level, so easy detectable things like OpenVPN, Wireguard and Tailscale doesn’t work anymore

[-] refalo@programming.dev 1 points 6 months ago

I understand, that's why I suggested some non-easily-detectable solutions.

[-] just_another_person@lemmy.world 0 points 6 months ago* (last edited 6 months ago)

That was added later, obviously. Even still, you don't need a VPS for this. This is overly complex .

If SSH works, just forward ports and be done with it.

[-] mfat 2 points 6 months ago

I don't want to remember port numbers. I'm trying to give each service its own subdomain.

[-] just_another_person@lemmy.world -3 points 6 months ago

Beggers CAN be choosers, apparently 🤦

[-] Felix_lm22@sopuli.xyz 1 points 6 months ago

VPS

You should if your ip is private, not public.

this post was submitted on 05 May 2024
48 points (91.4% liked)

Selfhosted

40298 readers
1135 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz