Issue Details
The quic-go package defaults to a 1280 byte InitialPacketSize. With packet headers, this does not allow the initial handshake packets to fit into the 1280 byte MTU of tailnets. This breaks all attempts to create HTTP3 connections over tailnets.
This is a well known issue with quic-go.
Caddy uses quic-go with its default InitialPacketSize. This means all HTTP3 connection attempts to Caddy over tailnets will fail. This further means that Caddy's HTTP3 functionality and automatic Tailscale TLS certificates functionality are mutually exclusive.
Assistance Disclosure
AI not used
If AI was used, describe the extent to which it was used.
No response
Issue Details
The quic-go package defaults to a 1280 byte
InitialPacketSize. With packet headers, this does not allow the initial handshake packets to fit into the 1280 byte MTU of tailnets. This breaks all attempts to create HTTP3 connections over tailnets.This is a well known issue with quic-go.
Caddy uses quic-go with its default
InitialPacketSize. This means all HTTP3 connection attempts to Caddy over tailnets will fail. This further means that Caddy's HTTP3 functionality and automatic Tailscale TLS certificates functionality are mutually exclusive.Assistance Disclosure
AI not used
If AI was used, describe the extent to which it was used.
No response