HTTP/2 and HTTP/3

HTTP/2 on the origin. HTTP/3 only if UDP 443 is actually open.

NGINX already speaks HTTP/2 on a current TLS vhost. QUIC needs a build that has it, and a firewall hole for UDP. Cloudflare in front already does HTTP/3 at the edge.

What is worth doing

ALPN, then the protocol the client can use

HTTP/2

On for HTTPS. A missing directive on one vhost is a config fix, not a project. HTTP/2 does not speed up a slow PHP page. It multiplexes the files around it.

HTTP/3

Only if NGINX or the panel build includes QUIC, and UDP 443 is open in UFW and in the provider firewall. A flag in a config the binary ignores does nothing.

Cloudflare

The browser already talks HTTP/3 to the edge. The origin can stay HTTP/2. Enabling QUIC on the VPS as well is optional, and we say if it is wasted.

Not a speed job

A protocol switch does not fix a 4 second PHP request

If the wait is the application, this page is the wrong hour. We check one request before editing the listen line.

NGINX support → · Performance →

Price

€55 an hour. HTTP/2 is usually inside that hour.

Standard €55 an hour. Priority €75. Emergency €95. Out of hours €125, if someone is free. Minimum 1 hour. HTTP/3 is the same rate if the binary supports it. A custom NGINX build to get QUIC is quoted, not assumed.

Pricing →

Site still on HTTP/1.1, or QUIC enabled and nothing connects?

Tell us NGINX or Apache, and whether Cloudflare is in front. No root password in the first message.

Request Support → Contact Us