Okay, it seems there are some #tailscale (or similar services) users here. Everything works great so far, tailscale serve + their services are easy to use. However, I'd like to get an understanding if it is possible to access my #homelab services without the tailscale client whenever I'm in my home lan network und with the tailscale client when I'm connected remotely - from the same https (sub-) domain. I have read that I need a public domain and a #reverseproxy for that (which I don't have in my current setup) - is this the right way to go?

Okay, it seems there are some #tailscale (or similar services) users here. Everything works great so far, tailscale serve + their services are easy to use. However, I'd like to get an understanding if it is possible to access my #homelab services without the tailscale client whenever I'm in my home lan network und with the tailscale client when I'm connected remotely - from the same https (sub-) domain. I have read that I need a public domain and a #reverseproxy for that (which I don't have in my current setup) - is this the right way to go?

That's just the "normal" #nginx domain, location and #reverseProxy stuff. I don't have a good example at hand (we have it at work, but the git is not yet public, sorry), maybe others can point to a good tutorial?

@prosodyim maybe?

(Reminder to myself: Put more $dayjob stuff to the public git. There are no secrets anyway.)

#Jabber#XMPP #prosody

Caddy Web Server 2.10 released with encrypted ClientHello (ECH) support, post-quantum key exchange, ACME profiles, libdns 1.0 APIs, global DNS config

https://github.com/caddyserver/caddy/releases/tag/v2.10.0

#caddyserver #caddyreverseproxy #webserver #reverseproxy #acme #postquantumcryptography