HTTP/3, the latest version of the Hypertext Transfer Protocol, brings significant improvements over earlier versions.

xCloud has already supported HTTP/3 on OLS (OpenLiteSpeed) servers. Now, this support is also available for NGINX servers. This means you can create and run websites on the HTTP/3 protocol whether you are using OLS or NGINX. In this guide, we will show you how to enable HTTP/3 for both new and existing sites on NGINX servers.

What Is HTTP/3 and Why Is It Important? #

HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on top of QUIC, a transport layer protocol developed by Google. Unlike HTTP/2, which relies on TCP, HTTP/3 operates over UDP. This enables faster connection establishment, elimination of head-of-line blocking, improved performance on unreliable networks, and enhanced security.

Reduced Latency #

QUIC combines the transport handshake and encryption handshake into a single process. This reduces the number of round trips required to establish a secure connection and leads to faster page loads for visitors.

Elimination of Head-of-Line Blocking #

In HTTP/2, the loss of a single data packet can delay all other data streams. HTTP/3 processes each stream independently, ensuring that only the affected stream is delayed. For example, if you are chatting with an AI tool like ChatGPT and one response segment is delayed, HTTP/3 ensures that other parts of the chat, such as text already loaded or supporting images, continue to display without interruption. This independent processing improves the loading speed of site assets such as images, CSS, and JavaScript files.

Improved Performance on Unreliable Networks #

HTTP/3 supports connection migration, allowing users to maintain uninterrupted connections even when switching networks, such as from Wi-Fi to mobile data. This ensures a seamless browsing experience for visitors using mobile devices or unstable networks.

Enhanced Security #

QUIC is encrypted by default. HTTP/3 leverages this encryption to provide a more secure connection without additional configuration, protecting user data and communications.

How to Enable HTTP/3 in xCloud for New Sites? #

For all new websites deployed on xCloud, HTTP/3 support is enabled automatically if the server runs NGINX version 1.25.0 or higher. Site owners do not need to take any additional steps. New sites are provisioned with all necessary server configurations and SSL/TLS settings to ensure full compatibility with HTTP/3 for supported browsers and clients.

How to Enable HTTP/3 on Previously Deployed Sites on NGINX Servers #

For sites deployed before HTTP/3 support was deployed from xCloud, you need to regenerate NGINX to enable HTTP/3. Here are the steps to regenerate the permissions of the rescue site associated with each domain.

👉 Note: xCloud already supports HTTP/3 on OLS (OpenLiteSpeed) servers by default. For NGINX servers, follow the steps below to enable HTTP/3.

Step 1: Login and Select the Site  #

To reset the file and folder permissions of your site. First, log in to your xCloud dashboard,go to your website where you want to activate HTTP/3. Now, go to the ‘Site settings’ option from the left navigation bar.

Step 2: Reset the Permissions  #

Then roll down a little and toggle on the ‘Regenerate NGINX Configurations’ option to enable and then enable the ‘Restart NGINX’ option as well and click on the ‘Run Now’ button.

This is how easily you can reset the files and folder permissions and enable HTTP3 for your sites.

How to Verify HTTP/3 Activation for Your Site #

After regenerating permissions, verify that HTTP/3 is active by opening an online tool such as HTTP3 Check to confirm that the site serves content over HTTP/3.

Enabling HTTP/3 in xCloud improves website performance, security, and user experience. New sites automatically benefit from HTTP/3, while existing sites can enable it by regenerating the rescue site permissions. Advanced users may also configure HTTP/3 manually if desired. This upgrade ensures faster, more reliable connections for all visitors, including those on mobile or unstable networks.