Infrastructure GuideDeployment &
Deployment &
QUIC Configuration.
Configure your TLS termination proxy to enable high-speed UDP (HTTP/3) acceleration for the Buzstorage backend.
1. NGINX Proxy Manager Setup
NestJS operates purely on TCP. To leverage UDP (HTTP/3), Nginx must handle the QUIC connection from the client and proxy it to NestJS over TCP.
3000.nginx-advanced.conf
# Enable HTTP/3 (QUIC) and alt-svc headers
add_header alt-svc 'h3=":443"; ma=86400';
add_header X-protocol $server_protocol always;
# Send proxy diagnostic headers to NestJS backend
proxy_set_header X-Forwarded-Protocol $server_protocol;
proxy_set_header X-QUIC $http3;Infrastructure Requirements
Your Nginx server block must be compiled with the nginx-quic module (or Nginx >= 1.25.0) and be listening on '443 quic reuseport'. NPM handles this partially, but you may need an updated Docker image that explicitly enables HTTP/3.
2. Verify Connection
Once the proxy is configured and the backend is deployed, you can verify that the connection is active using the system diagnostics endpoint.
Testing from the Employee Dashboard
- Open the Buzstorage Employee Dashboard.
- Navigate to Settings > Edge Proxy Status.
- Run the Proxy Connection Check.
If quicEnabled is false or the protocol is HTTP/1.1, the UDP proxy configuration is failing, and traffic is falling back to standard TCP connections. Check your NGINX configuration and ensure port 443 (UDP) is open on your firewall.