1. The problem I’m having:
I’m trying to setup a reverse proxy to a murmur server that is running in my homenet. The machine running caddy is connected to my homenet through a wireguard vpn. This setup works very nice with caddy for most reverse proxies. However, now that I try to access my murmur server with a subdomain I always get an Server connection failed: The TLS/SSL connection has been closed.
error in my mumble client.
I don’t really know what the issue here is. My murmur config is very minimal. If I understand the caddy documentation correctly then a udp proxy is supported. I run caddy in version 2.9.1.
2. Error messages and/or full log output:
As far as I can tell, this is the only error I get
Feb 02 15:44:40 personal-vps caddy[1866]: {"level":"error","ts":1738507480.1248767,"logger":"http.log.error","msg":"EOF","request":{"remote_ip":"37.209.30.113","remote_port":"62477","client_ip":"37.209.30.113","proto":"HTTP/2.0","method":"GET","host":"mumble.mydomain.com","uri":"/","headers":{"Sec-Fetch-Site":["none"],"User-Agent":["Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36"],"Sec-Ch-Ua":["\"Brave\";v=\"131\", \"Chromium\";v=\"131\", \"Not_A Brand\";v=\"24\""],"Sec-Fetch-User":["?1"],"Upgrade-Insecure-Requests":["1"],"Accept-Encoding":["gzip, deflate, br, zstd"],"Accept-Language":["en-US,en;q=0.9"],"Priority":["u=0, i"],"Sec-Ch-Ua-Platform":["\"Linux\""],"Accept":["text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8"],"Sec-Fetch-Dest":["document"],"Sec-Ch-Ua-Mobile":["?0"],"Sec-Fetch-Mode":["navigate"],"Sec-Gpc":["1"]},"tls":{"resumed":false,"version":772,"cipher_suite":4865,"proto":"h2","server_name":"mumble.mydomain.com"}},"duration":0.06714513,"status":502,"err_id":"u4xrbizqv","err_trace":"reverseproxy.statusError (reverseproxy.go:1373)"}
3. Caddy version:
2.9.1
4. How I installed and ran Caddy:
As systemd with a Caddyfile
a. System environment:
Systemd on ubuntu 24.04
d. My complete Caddy config:
mumble.mydomain.com {
reverse_proxy 10.10.10.10:64738
#also tried this
reverse_proxy udp/10.10.10.10:64738
}