Comment on Caddy subdomain reverse proxy performance
doot@social.bug.expert 1 year ago
is it possible the subdomain resolves to an ip your router can’t see due to nat hairpinning?
Comment on Caddy subdomain reverse proxy performance
doot@social.bug.expert 1 year ago
is it possible the subdomain resolves to an ip your router can’t see due to nat hairpinning?
lemming741@lemmy.world 1 year ago
I 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.
doot@social.bug.expert 1 year ago
Interesting stuff, perhaps report it to the Caddy devs, h3 isn’t really “stable” afaik
lemming741@lemmy.world 1 year ago
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.
doot@social.bug.expert 1 year ago
wow, some of those comments mirror your situation exactly hah