Confusions about production ready zero downtime deployment

[Whitestrake (Matthew Fay)]

I did find something about that here on these forums:

@francislavoie

That error typically means you’re listening on a unix socket or something, therefore Go’s stdlib can’t automatically determine a port to use for the Alt-Svc header to announce that HTTP/3 support is available to clients. It’s not really a problem, it just means that the Alt-Svc header won’t be used so clients won’t try HTTP/3.

Does that sound like it might be relevant?