I’ll definitely take a look at so thx. Also I’m using duckdns right now so i didn’t need to port forward anything but if I use my domain do i need to port forward ports 80&443 from through my router to my debian server (192.168.200.101)?
Comment on How to reverse proxy?
theselfhoster@sopuli.xyz 7 months ago
[deleted]
Octavusss@lemm.ee 7 months ago
walden@sub.wetshaving.social 7 months ago
To access things outside of your LAN (for example from your phone while at the grocery store), each service gets a DuckDNS entry. “service.myduckdns.com” or whatever.
Your phone will look for service.myduckdns.com on port 443, because you’ll have https:// certificates and that all happens on port 443.
When that request eventually gets to your router and is trying to penetrate your firewall, you’ll need 443 open and forwarded to your Debian machine.
So yes, you have it right.
Also forward port 80.
WhatAmLemmy@lemmy.world 7 months ago
You can also choose a mesh vpn like tailscale and then you don’t have to worry about ddns or port forwarding at all, ace you can still use a reverse proxy.
Octavusss@lemm.ee 7 months ago
I mean i have a wireguard on my router but how can I point the domain from my provider like (godaddy) to my server without opening ports?
Flamekebab@piefed.social 7 months ago
Yeah, another vote for Caddy. I've run nginx as a reverse proxy before and it wasn't too bad, but Caddy is even easier.