Caddy subdomain reverse proxy performance
Caddy subdomain reverse proxy performance
I'd asked about using a VPS to get better routing to my homelab in this post: https://lemmy.world/post/1424540
I've narrowed down my problem- if i use a subdomain in my caddyfile, performance is 1/3 or worse compared to just the root.
example.com {reverse_proxy 192.168.1.57}
will saturate my gigabit lan connection at 980ish. On a 5gUW connection i get my advertised 50 mbit or more
librespeed.example.com {reverse_proxy 192.168.1.57}
I get 220-250 megabits on my internal lan. The same 5gUW connection will only get 7 or 8 mbit.
It's strange to me that everything seems to work just fine, but it's just slow. Anyone got any ideas?
You're viewing a single thread.
is it possible the subdomain resolves to an ip your router can't see due to nat hairpinning?
1 0 ReplyI tried to dig into that but couldn't come up with a good test. But if NAT hairpinning wasn't working right, I'd be limited to my ISPs 50Mbit, right? I could get 200+ Mbit on wifi. I also tested this from work (50 Mbit sym fiber) and subdomains always were slower. I figured out today it's HTTP/3 causing my problems. I don't know if I care to troubleshoot anymore since it's working great with http 1 & 2.
4 0 ReplyInteresting stuff, perhaps report it to the Caddy devs, h3 isn't really "stable" afaik
2 0 Replyhttps://github.com/caddyserver/caddy/issues/4876
Looks like they already know, and upstream is working on it. I am curious why the sub domains get http/3 and the root domain does not.
4 0 Replywow, some of those comments mirror your situation exactly hah
2 0 Reply