<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>reloading &#8211; MASSIVE News</title>
	<atom:link href="https://massive.news/tag/reloading/feed/" rel="self" type="application/rss+xml" />
	<link>https://massive.news</link>
	<description>Progressive Mix of World News and Propaganda</description>
	<lastBuildDate>Sun, 04 Oct 2026 18:00:11 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.5</generator>

<image>
	<url>https://massive.news/wp-content/uploads/2024/08/m-150x150.jpg</url>
	<title>reloading &#8211; MASSIVE News</title>
	<link>https://massive.news</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How To Set Up an NGINX Reverse Proxy for Node.js, Python &#038; Go Apps</title>
		<link>https://massive.news/how-to-set-up-an-nginx-reverse-proxy-for-node-js-python-go-apps/</link>
		
		<dc:creator><![CDATA[wiredgorilla]]></dc:creator>
		<pubDate>Sun, 04 Oct 2026 18:00:03 +0000</pubDate>
				<category><![CDATA[Technology and Science]]></category>
		<category><![CDATA[access]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[apps]]></category>
		<category><![CDATA[BASIC]]></category>
		<category><![CDATA[bugs]]></category>
		<category><![CDATA[Cloud Education]]></category>
		<category><![CDATA[Crash]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[developers]]></category>
		<category><![CDATA[Docker]]></category>
		<category><![CDATA[Environment]]></category>
		<category><![CDATA[Features]]></category>
		<category><![CDATA[framework]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[means]]></category>
		<category><![CDATA[name]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[Open]]></category>
		<category><![CDATA[Operations]]></category>
		<category><![CDATA[port]]></category>
		<category><![CDATA[proxies]]></category>
		<category><![CDATA[Python]]></category>
		<category><![CDATA[reloading]]></category>
		<category><![CDATA[secure]]></category>
		<category><![CDATA[Server Management]]></category>
		<category><![CDATA[servers]]></category>
		<category><![CDATA[SSH]]></category>
		<category><![CDATA[stack overflow]]></category>
		<category><![CDATA[streaming]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[Web Design and Development]]></category>
		<category><![CDATA[Web Servers]]></category>
		<category><![CDATA[website]]></category>
		<category><![CDATA[X]]></category>
		<category><![CDATA[yes]]></category>
		<guid isPermaLink="false">https://massive.news/how-to-set-up-an-nginx-reverse-proxy-for-node-js-python-go-apps/</guid>

					<description><![CDATA[There is a significant difference between an application that runs on localhost:3000 and one that is...]]></description>
										<content:encoded><![CDATA[<div class="video-container"><iframe width="560" height="315" src="https://www.youtube.com/embed/B62QSbPhh1s" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></div>
<p class="wp-block-paragraph">There is a significant difference between an application that runs on localhost:3000 and one that is ready for public traffic.&nbsp;</p>
<p><cms-inline-toc tocs="[{&quot;id&quot;:&quot;#what-an-nginx-reverse-proxy-actually-does-and-why-you-need-one&quot;,&quot;name&quot;:&quot;What an NGINX Reverse Proxy Actually Does (And Why You Need One)&quot;,&quot;tagName&quot;:&quot;h2&quot;},{&quot;id&quot;:&quot;#ssl-termination-port-consolidation-and-http2-to-the-client&quot;,&quot;name&quot;:&quot;SSL termination, port consolidation, and HTTP/2 to the client&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#why-put-nginx-in-front-of-your-application&quot;,&quot;name&quot;:&quot;Why Put NGINX in Front of Your Application?u00a0&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#reverse-proxy-vs-forward-proxy-vs-load-balancer&quot;,&quot;name&quot;:&quot;Reverse proxy vs forward proxy vs load balancer&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#before-you-configure-the-reverse-proxy&quot;,&quot;name&quot;:&quot;Before You Configure the Reverse Proxy&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#example-nginx-reverse-proxy-configuration&quot;,&quot;name&quot;:&quot;Example NGINX Reverse Proxy Configurationu00a0&quot;,&quot;tagName&quot;:&quot;h2&quot;},{&quot;id&quot;:&quot;#example-https-reverse-proxy-configuration&quot;,&quot;name&quot;:&quot;Example HTTPS Reverse Proxy Configurationu00a0&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#configure-multiple-upstream-application-instances&quot;,&quot;name&quot;:&quot;Configure Multiple Upstream Application Instancesu00a0&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#reverse-proxy-a-nodejs-app-with-pm2&quot;,&quot;name&quot;:&quot;Reverse Proxy a Node.js App (with PM2)&quot;,&quot;tagName&quot;:&quot;h2&quot;},{&quot;id&quot;:&quot;#run-the-nodejs-app-with-pm2-on-port-3000&quot;,&quot;name&quot;:&quot;Run the Node.js App with PM2 on Port 3000u00a0&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#the-proxypass--headers-config-for-node&quot;,&quot;name&quot;:&quot;The proxy_pass + headers config for Node&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#zerodowntime-reload-pattern&quot;,&quot;name&quot;:&quot;Zero-downtime reload pattern&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#reverse-proxy-a-python-app&quot;,&quot;name&quot;:&quot;Reverse Proxy a Python Appu00a0&quot;,&quot;tagName&quot;:&quot;h2&quot;},{&quot;id&quot;:&quot;#gunicorn-on-a-unix-socket-vs-tcp-port&quot;,&quot;name&quot;:&quot;Gunicorn on a Unix socket vs TCP port&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#the-nginx-upstream-config-for-unix-sockets&quot;,&quot;name&quot;:&quot;The NGINX upstream config for Unix sockets&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#disable-proxy-buffering-for-streaming-responses&quot;,&quot;name&quot;:&quot;Disable Proxy Buffering for Streaming Responsesu00a0&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#reverse-proxy-a-go-app&quot;,&quot;name&quot;:&quot;Reverse Proxy a Go App&quot;,&quot;tagName&quot;:&quot;h2&quot;},{&quot;id&quot;:&quot;#the-minimal-proxypass-for-a-go-binary&quot;,&quot;name&quot;:&quot;The minimal proxy_pass for a Go binary&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#configure-websocket-proxying-in-nginx&quot;,&quot;name&quot;:&quot;Configure WebSocket Proxying in NGINXu00a0&quot;,&quot;tagName&quot;:&quot;h2&quot;},{&quot;id&quot;:&quot;#increase-the-websocket-read-timeout&quot;,&quot;name&quot;:&quot;Increase the WebSocket Read Timeoutu00a0&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#how-to-set-up-an-nginx-reverse-proxy-in-runcloud&quot;,&quot;name&quot;:&quot;How to Set Up an NGINX Reverse Proxy in RunCloud&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#troubleshooting-common-nginx-reverse-proxy-problems&quot;,&quot;name&quot;:&quot;Troubleshooting Common NGINX Reverse Proxy Problems&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#manage-reusable-nginx-configurations-with-runcloud-templates&quot;,&quot;name&quot;:&quot;Manage Reusable NGINX Configurations with RunCloud Templatesu00a0&quot;,&quot;tagName&quot;:&quot;h2&quot;},{&quot;id&quot;:&quot;#wrapping-up&quot;,&quot;name&quot;:&quot;Wrapping Up&quot;,&quot;tagName&quot;:&quot;h2&quot;},{&quot;id&quot;:&quot;#faqs&quot;,&quot;name&quot;:&quot;FAQs&quot;,&quot;tagName&quot;:&quot;h2&quot;},{&quot;id&quot;:&quot;#what-is-the-difference-between-nginx-and-apache-as-a-reverse-proxy&quot;,&quot;name&quot;:&quot;What is the difference between NGINX and Apache as a reverse proxy?&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#should-i-use-caddy-or-traefik-instead-of-nginx&quot;,&quot;name&quot;:&quot;Should I use Caddy or Traefik instead of NGINX?&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#why-does-my-websocket-disconnect-every-60-seconds-behind-nginx&quot;,&quot;name&quot;:&quot;Why does my WebSocket disconnect every 60 seconds behind NGINX?&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#how-do-i-pass-the-real-client-ip-through-nginx-and-cloudflare&quot;,&quot;name&quot;:&quot;How do I pass the real client IP through NGINX and Cloudflare?&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#can-nginx-do-load-balancing-between-multiple-nodejs-processes&quot;,&quot;name&quot;:&quot;Can NGINX do load balancing between multiple Node.js processes?&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#does-nginx-http2-work-with-the-upstream-backend&quot;,&quot;name&quot;:&quot;Does NGINX HTTP/2 work with the upstream backend?&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#what-is-the-cleanest-way-to-add-ssl-to-a-nodejs-app&quot;,&quot;name&quot;:&quot;What is the cleanest way to add SSL to a Node.js app?&quot;,&quot;tagName&quot;:&quot;h3&quot;}]"></cms-inline-toc></p>
<p class="wp-block-paragraph">When it is time to go live, you need SSL, a custom domain, and a secure way to route traffic to your backend. If you are like most developers, you probably grab the top NGINX reverse proxy snippet from Stack Overflow, paste it into your server, and call it a day.</p>
<p class="wp-block-paragraph">Then the weird bugs start.</p>
<p class="wp-block-paragraph">Your real-time WebSockets silently disconnect every 60 seconds. You check your application logs, only to realize every single visitor’s IP address is logged as a Cloudflare server or your own local proxy’s IP. Then a user tries to upload a basic 2MB image and gets slammed with a frustrating 413 Request Entity Too Large error.</p>
<p class="wp-block-paragraph">We have all been there.</p>
<p class="wp-block-paragraph">Instead of relying on incomplete configuration snippets, we will show you a more complete NGINX reverse proxy setup that you can adapt to your application and server environment. This will help you prevent common WebSocket timeout problems, preserve the correct client connection information, and terminate SSL cleanly before forwarding requests to your application.&nbsp;</p>
<h2 class="wp-block-heading" id="what-an-nginx-reverse-proxy-actually-does-and-why-you-need-one"><strong>What an NGINX Reverse Proxy Actually Does (And Why You Need One)</strong></h2>
<p class="wp-block-paragraph">If you are using NGINX for the first time, you can read our NGINX configuration basics guide first. But in short, a reverse proxy sits in front of your application server (like Node, Python, or Go) and intercepts all incoming internet traffic.</p>
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="526" src="https://massive.news/wp-content/uploads/2026/10/how-to-set-up-an-nginx-reverse-proxy-for-node-js-python-go-apps.jpg" alt class="wp-image-14238" role="none"></figure>
<p class="wp-block-paragraph">This proxy handles several important tasks, such as:</p>
<h3 class="wp-block-heading" id="ssl-termination-port-consolidation-and-http2-to-the-client"><strong>SSL termination, port consolidation, and HTTP/2 to the client</strong></h3>
<p class="wp-block-paragraph">When people visit a website, they expect secure https:// traffic on port 443 served via modern HTTP/2 protocols. Your application is probably served via plain HTTP/1.1 on port 3000.&nbsp;</p>
<p class="wp-block-paragraph">In this setup, NGINX “terminates” the SSL connection, meaning it handles the heavy lifting of decryption and HTTP/2 multiplexing, and passes plain, unencrypted traffic to your app locally. This will allow you to centralize your certificate management.</p>
<h3 class="wp-block-heading" id="why-put-nginx-in-front-of-your-application"><strong>Why Put NGINX in Front of Your Application?&nbsp;</strong></h3>
<p class="wp-block-paragraph">You can technically configure a Node.js or Go application to listen directly on port 443 and manage its own TLS certificates. In many production environments, it is simpler to place NGINX in front of the application instead.</p>
<p class="wp-block-paragraph">NGINX can handle TLS termination, connection management, request limits, compression, logging, and other web-server responsibilities while your application remains focused on handling application requests.</p>
<h3 class="wp-block-heading" id="reverse-proxy-vs-forward-proxy-vs-load-balancer"><strong>Reverse proxy vs forward proxy vs load balancer</strong></h3>
<p class="wp-block-paragraph">When you are deciding between web servers and reverse proxies, you need to understand the terminology. A <strong>forward proxy</strong> sits between clients and external services and sends requests on the clients’ behalf. A <strong>reverse proxy</strong> sits in front of one or more backend servers and receives requests on their behalf. NGINX can also act as a <strong>load balancer</strong> by distributing requests across multiple backend instances.&nbsp;</p>
<h3 class="wp-block-heading" id="before-you-configure-the-reverse-proxy"><strong>Before You Configure the Reverse Proxy</strong></h3>
<p class="wp-block-paragraph">Before setting up NGINX, make sure:</p>
<ul class="wp-block-list">
<li>Your application is already running.</li>
<li>You know the local port or Unix socket used by the application.</li>
<li>The application is not unnecessarily exposed on a public interface.</li>
<li>Your domain points to the server.</li>
<li>Ports 80 and 443 are reachable if you are serving the application publicly.</li>
<li>Your SSL certificate is already available if you use the HTTPS configuration shown below.</li>
</ul>
<p class="wp-block-paragraph">You can test a TCP-based application locally before configuring NGINX. For example:</p>
<pre><code v-pre>curl http://127.0.0.1:3000</code></pre>
<p class="wp-block-paragraph">If the application does not respond locally or if you see an error message saying “Failed to connect”, then you must fix the application or service first. NGINX cannot proxy successfully to an upstream service that is not running.</p>
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="634" src="https://massive.news/wp-content/uploads/2026/10/how-to-set-up-an-nginx-reverse-proxy-for-node-js-python-go-apps.png" alt="Check application accessible via CURL" class="wp-image-14235"></figure>
<h2 class="wp-block-heading" id="example-nginx-reverse-proxy-configuration"><strong>Example NGINX Reverse Proxy Configuration&nbsp;</strong></h2>
<p class="wp-block-paragraph">Most tutorials give you only the basic proxy configuration and leave you to handle features such as WebSockets, client IP forwarding, upload limits, and timeouts separately. The following example provides a more complete starting point that you can adapt to your application and server environment.&nbsp;</p>
<h3 class="wp-block-heading" id="example-https-reverse-proxy-configuration"><strong>Example HTTPS Reverse Proxy Configuration&nbsp;</strong></h3>
<p class="wp-block-paragraph">The map directive must be defined in the NGINX http context, outside the server block. The server block can then use the resulting $connection_upgrade variable when forwarding WebSocket requests.&nbsp;</p>
<pre><code v-pre>map $http_upgrade $connection_upgrade { 
    default upgrade; 
    '' close; 
} 
server {
    listen 443 ssl;
    http2 on;
    server_name myapp.com;
    # SSL Configuration
    ssl_certificate /etc/letsencrypt/live/myapp.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/myapp.com/privkey.pem;
    # Example upload limit
    client_max_body_size 50M; 
    location / {
        # Proxy pass to your application
        proxy_pass http://127.0.0.1:3000;


        # Support HTTP/1.1 and WebSocket upgrades 
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;


        # Forward the original host and client connection details
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;


        # Connection timeouts
        proxy_read_timeout 300;
        proxy_send_timeout 300; 
    }
}</code></pre>
<p class="wp-block-paragraph">If NGINX receives traffic directly from the client, $remote_addr contains the client’s IP address. If your site sits behind another proxy or CDN such as Cloudflare, you must also configure NGINX to trust that proxy and restore the original client IP. Otherwise, $remote_addr will contain the proxy’s IP address instead.</p>
<p class="wp-block-paragraph">If you use RunCloud, you can create and manage reverse proxy configurations from the RunCloud dashboard rather than manually editing generated NGINX configuration files.</p>
<h3 class="wp-block-heading" id="configure-multiple-upstream-application-instances"><strong>Configure Multiple Upstream Application Instances&nbsp;</strong></h3>
<p class="wp-block-paragraph">If you run multiple instances of your application, you can define an upstream block outside the server block. NGINX can then distribute requests across those application instances.</p>
<pre><code v-pre>upstream my_nodejs_app {
    server 127.0.0.1:3000;
    server 127.0.0.1:3001;
}</code></pre>
<p class="wp-block-paragraph">You would then change your location block to use <code v-pre>proxy_pass http://my_nodejs_app</code>.</p>
<h2 class="wp-block-heading" id="reverse-proxy-a-nodejs-app-with-pm2"><strong>Reverse Proxy a Node.js App (with PM2)</strong></h2>
<p class="wp-block-paragraph">When you deploy a long-running Node.js application on a VPS, you will usually run it under a process manager or service manager so that it can restart after a crash or server reboot. PM2 is a common option.&nbsp;</p>
<h3 class="wp-block-heading" id="run-the-nodejs-app-with-pm2-on-port-3000"><strong>Run the Node.js App with PM2 on Port 3000&nbsp;</strong></h3>
<p class="wp-block-paragraph">For an application that accepts a -p port argument, you could start it with PM2 on port 3000:</p>
<pre><code v-pre>pm2 start server.js --name "my-app" -- -p 3000</code></pre>
<p class="wp-block-paragraph">The exact command depends on how your application accepts its host and port settings.</p>
<p class="wp-block-paragraph">Many Node.js frameworks use the Host and X-Forwarded-Proto headers when determining the original hostname and protocol. Forwarding these headers allows the application to identify that the original client connection used HTTPS even though NGINX communicates with the application over local HTTP.</p>
<p class="wp-block-paragraph">Depending on your framework, you may also need to configure the application to trust the reverse proxy before it uses forwarded headers.</p>
<p class="wp-block-paragraph"><em>If you</em> manage the application with RunCloud<em>, you can create the reverse proxy from the RunCloud dashboard. Set the web application’s stack to Native NGINX + Custom Config, then use the predefined Proxy configuration under NGINX Config and set it to the port used by your application.&nbsp;</em></p>
<h3 class="wp-block-heading" id="zerodowntime-reload-pattern"><strong>Zero-downtime reload pattern</strong></h3>
<p class="wp-block-paragraph">After changing a standard NGINX configuration, test the configuration before reloading the service:</p>
<pre><code v-pre>nginx -t &amp;&amp; systemctl reload nginx</code></pre>
<p class="wp-block-paragraph">A graceful reload applies valid configuration changes without unnecessarily interrupting active connections.</p>
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="633" src="https://massive.news/wp-content/uploads/2026/10/how-to-set-up-an-nginx-reverse-proxy-for-node-js-python-go-apps-1.png" alt="Check NGINX config syntax" class="wp-image-14236"></figure>
<p class="wp-block-paragraph">If your server is managed by RunCloud, use the NGINX Config tools in the RunCloud dashboard to configure web applications. RunCloud uses its own NGINX package and configuration structure, so generic nginx service commands and paths may not match a RunCloud-managed server.&nbsp;</p>
<h2 class="wp-block-heading" id="reverse-proxy-a-python-app"><strong>Reverse Proxy a Python App&nbsp;</strong></h2>
<p class="wp-block-paragraph">Python applications handle concurrency differently than Node.js, usually relying on WSGI (Gunicorn) or ASGI (Uvicorn) servers.</p>
<h3 class="wp-block-heading" id="gunicorn-on-a-unix-socket-vs-tcp-port"><strong>Gunicorn on a Unix socket vs TCP port</strong></h3>
<p class="wp-block-paragraph">Gunicorn can listen either on a local TCP port, such as <code v-pre>127.0.0.1:8000</code>, or on a Unix socket. Unix sockets can be useful when NGINX and Gunicorn run on the same server because access can be controlled through filesystem permissions.</p>
<p class="wp-block-paragraph">For example:</p>
<pre><code v-pre>gunicorn --bind unix:/tmp/myapp.sock wsgi:app</code></pre>
<h3 class="wp-block-heading" id="the-nginx-upstream-config-for-unix-sockets"><strong>The NGINX upstream config for Unix sockets</strong></h3>
<p class="wp-block-paragraph">To point NGINX to a Unix socket instead of a TCP port, specify the socket path using NGINX’s Unix-domain socket syntax:</p>
<pre><code v-pre>proxy_pass http://unix:/tmp/myapp.sock:;</code></pre>
<h3 class="wp-block-heading" id="disable-proxy-buffering-for-streaming-responses"><strong>Disable Proxy Buffering for Streaming Responses&nbsp;</strong></h3>
<p class="wp-block-paragraph">NGINX buffers proxied responses by default. For applications that depend on incremental delivery, such as Server-Sent Events or streamed application responses, buffering can delay data reaching the client.</p>
<p class="wp-block-paragraph">You can disable proxy response buffering for the relevant location:</p>
<pre><code v-pre>proxy_buffering off;</code></pre>
<h2 class="wp-block-heading" id="reverse-proxy-a-go-app"><strong>Reverse Proxy a Go App</strong></h2>
<p class="wp-block-paragraph">Go’s <code v-pre>net/http</code> package can serve HTTP traffic directly without requiring a separate web server. Placing NGINX in front of a Go application can simplify TLS termination, compression, rate limiting, logging, and other HTTP-level configuration. NGINX includes gzip support, while Brotli requires Brotli module support in the NGINX build.&nbsp;</p>
<h3 class="wp-block-heading" id="the-minimal-proxypass-for-a-go-binary"><strong>The minimal proxy_pass for a Go binary</strong></h3>
<p class="wp-block-paragraph">If your Go application is listening on 127.0.0.1:8080, set proxy_pass to that address:</p>
<p class="wp-block-paragraph">proxy_pass http://127.0.0.1:8080;</p>
<p class="wp-block-paragraph">You can then add the required forwarding headers, timeout settings, and WebSocket configuration for your application.</p>
<h2 class="wp-block-heading" id="configure-websocket-proxying-in-nginx"><strong>Configure WebSocket Proxying in NGINX&nbsp;</strong></h2>
<p class="wp-block-paragraph">If you are running real-time applications like chat servers or automating workflows by hosting n8n behind Docker and NGINX, you need WebSockets. But WebSockets break easily behind NGINX if you miss three critical details.</p>
<p class="wp-block-paragraph">Older NGINX versions default to HTTP/1.0 when proxying HTTP requests to upstream servers. NGINX 1.29.7 and later default to HTTP/1.1.</p>
<p class="wp-block-paragraph">Explicitly setting the proxy version remains useful when you need compatibility with older NGINX installations and makes the WebSocket requirement clear:</p>
<pre><code v-pre>proxy_http_version 1.1;</code></pre>
<p class="wp-block-paragraph">A WebSocket connection begins as an HTTP request containing an Upgrade header. NGINX needs to pass the relevant upgrade information to the upstream application.</p>
<p class="wp-block-paragraph">A reusable configuration can define the appropriate Connection value with a map:</p>
<pre readability="4"><code v-pre readability="2">map $http_upgrade $connection_upgrade {<p>&nbsp;&nbsp;&nbsp;&nbsp;default upgrade;</p><p>&nbsp;&nbsp;&nbsp;&nbsp;''&nbsp; &nbsp; &nbsp; close;</p><p>}</p></code></pre>
<p class="wp-block-paragraph">Then use:</p>
<pre readability="4"><code v-pre readability="2">proxy_set_header Upgrade $http_upgrade;<p>proxy_set_header Connection $connection_upgrade;</p></code></pre>
<p class="wp-block-paragraph">This sends <code v-pre>Connection: upgrade</code> only when an upgrade has been requested.</p>
<h3 class="wp-block-heading" id="increase-the-websocket-read-timeout"><strong>Increase the WebSocket Read Timeout&nbsp;</strong></h3>
<p class="wp-block-paragraph">The default <code v-pre>proxy_read_timeout</code> is 60 seconds. If the upstream server sends no data during that period, NGINX can close the connection.</p>
<p class="wp-block-paragraph">For long-lived WebSocket connections, you can increase the timeout:</p>
<pre><code v-pre>proxy_read_timeout 86400;</code></pre>
<p class="wp-block-paragraph">This example allows up to 24 hours between successive read operations. Applications can also use WebSocket ping/pong messages or other heartbeat traffic to prevent idle connections from reaching the timeout.</p>
<h3 class="wp-block-heading" id="how-to-set-up-an-nginx-reverse-proxy-in-runcloud"><strong>How to Set Up an NGINX Reverse Proxy in RunCloud</strong></h3>
<p class="wp-block-paragraph">If your server is managed by RunCloud, you can configure the reverse proxy from the dashboard without manually editing the generated NGINX configuration files.</p>
<ol class="wp-block-list">
<li>Log in to the RunCloud dashboard and select your server.</li>
<li>Open Web Applications and select the application you want to configure.</li>
<li>Open Settings and change the Web Application Stack to Native NGINX + Custom Config.</li>
<li>Open NGINX Config and select Add a New Config.</li>
<li>Choose Predefined Config and select the Proxy configuration.</li>
<li>Set the proxy destination to the port used by your Node.js, Python, or Go application.</li>
<li>Configure options such as proxy buffering or WebSocket support if your application requires them.</li>
<li>Select Run and Debug to validate the NGINX configuration.</li>
<li>Once the configuration passes validation, select Create Config.</li>
<li>Test the application through its public URL or with curl.</li>
</ol>
<p class="wp-block-paragraph">RunCloud recommends creating and editing custom NGINX configuration through the dashboard. Generated application configuration files should not be edited manually because RunCloud manages those files.</p>
<h3 class="wp-block-heading" id="troubleshooting-common-nginx-reverse-proxy-problems"><strong>Troubleshooting Common NGINX Reverse Proxy Problems</strong></h3>
<h4 class="wp-block-heading" id="bad-gateway"><strong>502 Bad Gateway</strong></h4>
<p class="wp-block-paragraph">A 502 error usually means NGINX cannot connect to the upstream application.</p>
<p class="wp-block-paragraph">Check that the application is running and listening on the address or socket configured in <code v-pre>proxy_pass</code>.</p>
<p class="wp-block-paragraph">For a TCP-based application, test the upstream directly:</p>
<pre><code v-pre>curl http://127.0.0.1:3000</code></pre>
<p class="wp-block-paragraph">Also, confirm that the port in <code v-pre>proxy_pass</code> matches the port used by the application.</p>
<h4 class="wp-block-heading" id="request-entity-too-large"><strong>413 Request Entity Too Large</strong></h4>
<p class="wp-block-paragraph">If uploads fail with a 413 response, increase <code v-pre>client_max_body_size</code> to a value appropriate for your application:</p>
<pre><code v-pre>client_max_body_size 50M;</code></pre>
<p class="wp-block-paragraph">Avoid setting a much larger limit than your application actually needs.</p>
<h4 class="wp-block-heading" id="websockets-disconnect-or-fail-to-connect"><strong>WebSockets Disconnect or Fail to Connect</strong></h4>
<p class="wp-block-paragraph">Check that WebSocket upgrade headers are passed to the application and that the proxy uses HTTP/1.1 where required for compatibility.</p>
<p class="wp-block-paragraph">If connections close after periods of inactivity, review <code v-pre>proxy_read_timeout</code> and your application’s WebSocket heartbeat behavior.</p>
<h4 class="wp-block-heading" id="redirect-loops"><strong>Redirect Loops</strong></h4>
<p class="wp-block-paragraph">If NGINX terminates HTTPS but the application believes the request arrived over HTTP, the application may repeatedly redirect the request to HTTPS.</p>
<p class="wp-block-paragraph">Make sure NGINX forwards:</p>
<pre><code v-pre>proxy_set_header X-Forwarded-Proto $scheme;</code></pre>
<p class="wp-block-paragraph">You may also need to configure your framework to trust the reverse proxy.</p>
<h4 class="wp-block-heading" id="incorrect-client-ip-addresses"><strong>Incorrect Client IP Addresses</strong></h4>
<p class="wp-block-paragraph">If NGINX sits directly behind the client, $remote_addr represents the client address. If another proxy, such as Cloudflare, sits in front of NGINX, configure trusted proxy ranges and the appropriate real-IP header before relying on $remote_addr.</p>
<h2 class="wp-block-heading" id="manage-reusable-nginx-configurations-with-runcloud-templates"><strong>Manage Reusable NGINX Configurations with RunCloud Templates&nbsp;</strong></h2>
<div class="runcloud-alert" readability="8.4421487603306">
<p><em><strong>Note:</strong> Use the web application’s NGINX Config tools when configuring a reverse proxy for an individual application. NGINX Templates are useful when you want to reuse and centrally manage the same configuration across multiple applications.&nbsp;</em></p>
</div>
<p class="wp-block-paragraph">If you manage the same NGINX rules across several web applications, repeatedly copying configuration files makes those configurations harder to maintain consistently.</p>
<p class="wp-block-paragraph">RunCloud NGINX Templates let you create reusable configuration files in your workspace and link them to multiple web applications. You can manage these templates centrally from Settings &gt; NGINX Templates rather than manually editing each application’s configuration over SSH.</p>
<p class="wp-block-paragraph">RunCloud provides two template areas:</p>
<ul class="wp-block-list">
<li>My Templates contains templates created or duplicated into your workspace.</li>
<li>Public Templates contains read-only templates provided by RunCloud and approved community members. You can duplicate a Public Template into your workspace before editing or installing it.</li>
</ul>
<p class="wp-block-paragraph">This provides several benefits for server management:&nbsp;</p>
<ul class="wp-block-list">
<li><strong>Centralized configuration:</strong> Link a template to multiple web applications and manage the configuration from one place.</li>
<li><strong>Reusable templates:</strong> Create your own templates or duplicate a Public Template into your workspace as a starting point.</li>
<li><strong>Configuration testing:</strong> Test a template against an existing web application before installing it.</li>
<li><strong>Controlled propagation:</strong> When you update a linked template, RunCloud lets you propagate the new configuration to the selected web applications.</li>
<li><strong>Safer deployment:</strong> RunCloud checks the NGINX configuration before applying it. If validation fails, the invalid configuration is not activated.</li>
</ul>
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="554" src="https://massive.news/wp-content/uploads/2026/10/how-to-set-up-an-nginx-reverse-proxy-for-node-js-python-go-apps-2.png" alt="RunCloud NGINX template dashboard for creating reverse proxy" class="wp-image-14237"></figure>
<p class="wp-block-paragraph">This makes NGINX Templates useful when the same configuration needs to be maintained across several applications without manually updating each one.&nbsp;</p>
<h2 class="wp-block-heading" id="wrapping-up"><strong>Wrapping Up</strong></h2>
<p class="wp-block-paragraph">An NGINX reverse proxy gives you a central place to handle HTTPS, route requests to your application, forward request information, and configure features such as WebSocket support and upload limits.</p>
<p class="wp-block-paragraph">The exact configuration depends on your application, whether another proxy or CDN sits in front of NGINX, and which NGINX version you are running. Testing each configuration change before applying it is therefore essential.</p>
<p class="wp-block-paragraph">RunCloud provides dashboard tools for managing NGINX configuration without manually editing generated application configuration files. You can create reverse proxy configurations, validate them before applying them, and manage reusable configurations through NGINX Templates.</p>
<p class="wp-block-paragraph">This gives you a safer way to manage reverse proxy configuration across your applications while retaining control over application-specific settings such as ports, WebSockets, buffering, and forwarded headers.</p>
<p class="wp-block-paragraph"><strong>If you want to manage your NGINX reverse proxy and web applications from a central dashboard,</strong> sign up for RunCloud and deploy your next application<strong>.&nbsp;</strong></p>
<h2 class="wp-block-heading" id="faqs"><strong>FAQs</strong></h2>
<div id="rank-math-faq" class="rank-math-block">
<div class="rank-math-list ">
<div id="faq-question-1788510917507" class="rank-math-list-item" readability="8.5">
<h3 class="rank-math-question " id="what-is-the-difference-between-nginx-and-apache-as-a-reverse-proxy"><strong>What is the difference between NGINX and Apache as a reverse proxy?</strong></h3>
<div class="rank-math-answer " readability="12">
<p>Both NGINX and Apache can act as reverse proxies. NGINX uses an event-driven architecture and is commonly used as a dedicated reverse proxy in front of application servers. Apache supports reverse proxying through modules such as mod_proxy and offers several Multi-Processing Modules with different connection-handling models.<br />The better choice depends on your existing server stack, configuration requirements, and operational preferences.</p>
</div>
</div>
<div id="faq-question-1788510928295" class="rank-math-list-item" readability="10">
<h3 class="rank-math-question " id="should-i-use-caddy-or-traefik-instead-of-nginx"><strong>Should I use Caddy or Traefik instead of NGINX?</strong></h3>
<div class="rank-math-answer " readability="15">
<p>Caddy and Traefik are alternatives worth considering depending on your environment. Caddy focuses heavily on simple configuration and automatic HTTPS, while Traefik is commonly used with container and service-discovery workflows.<br />NGINX remains a good choice when you need detailed control over proxying, routing, headers, caching, or load balancing.</p>
</div>
</div>
<div id="faq-question-1788510939990" class="rank-math-list-item" readability="8">
<h3 class="rank-math-question " id="why-does-my-websocket-disconnect-every-60-seconds-behind-nginx"><strong>Why does my WebSocket disconnect every 60 seconds behind NGINX?</strong></h3>
<div class="rank-math-answer " readability="11">
<p>NGINX uses a default <code v-pre>proxy_read_timeout</code> of 60 seconds. If the upstream sends no data during that period, NGINX can close the connection.<br />You can increase <code v-pre>proxy_read_timeout</code> for long-lived WebSocket connections or use application-level ping/pong messages or other heartbeat traffic to keep the connection active.</p>
</div>
</div>
<div id="faq-question-1788510954640" class="rank-math-list-item" readability="8.5">
<h3 class="rank-math-question " id="how-do-i-pass-the-real-client-ip-through-nginx-and-cloudflare"><strong>How do I pass the real client IP through NGINX and Cloudflare?</strong></h3>
<div class="rank-math-answer " readability="12">
<p>If Cloudflare sits in front of NGINX, configure NGINX’s real-IP module to trust only Cloudflare’s published proxy IP ranges and use the appropriate <code v-pre>client-IP header</code>. This allows NGINX to replace the Cloudflare proxy address with the original visitor address before forwarding it to your application.<br />Do not trust forwarded client-IP headers from arbitrary sources, because clients can otherwise supply forged values.</p>
</div>
</div>
<div id="faq-question-1788510967691" class="rank-math-list-item" readability="8.5">
<h3 class="rank-math-question " id="can-nginx-do-load-balancing-between-multiple-nodejs-processes"><strong>Can NGINX do load balancing between multiple Node.js processes?</strong></h3>
<div class="rank-math-answer " readability="12">
<p>Yes. NGINX can distribute traffic across multiple Node.js instances using an upstream block. The available load-balancing methods include the default round-robin behavior as well as methods such as <code v-pre>least_conn</code> and <code v-pre>ip_hash</code>.<br />Choose the method according to how your application handles sessions, connection duration, and backend capacity.</p>
</div>
</div>
<div id="faq-question-1788510980515" class="rank-math-list-item" readability="8.5">
<h3 class="rank-math-question " id="does-nginx-http2-work-with-the-upstream-backend"><strong>Does NGINX HTTP/2 work with the upstream backend?</strong></h3>
<div class="rank-math-answer " readability="12">
<p>The protocol used between the client and NGINX is separate from the protocol NGINX uses to communicate with an upstream application. For normal HTTP reverse proxying, NGINX can proxy requests to HTTP upstream servers independently of whether the client connected using HTTP/2 or HTTP/3.<br />If your application uses a protocol such as gRPC, use the corresponding NGINX proxy module and configuration rather than the standard HTTP <code v-pre>proxy_pass</code> configuration.</p>
</div>
</div>
<div id="faq-question-1788510994096" class="rank-math-list-item" readability="7.5">
<h3 class="rank-math-question " id="what-is-the-cleanest-way-to-add-ssl-to-a-nodejs-app"><strong>What is the cleanest way to add SSL to a Node.js app?</strong></h3>
<div class="rank-math-answer " readability="10">
<p>A common production approach is to terminate TLS at NGINX and proxy requests to the Node.js application over a local connection. This centralizes certificate management and allows the application to run without managing its own public TLS listener.<br />You can obtain and renew certificates with a tool such as Certbot or use your server-management platform’s SSL tools.</p>
</div>
</div>
</div>
</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>How to Enable HTTP/3 on NGINX</title>
		<link>https://massive.news/how-to-enable-http-3-on-nginx/</link>
		
		<dc:creator><![CDATA[wiredgorilla]]></dc:creator>
		<pubDate>Sat, 02 May 2026 09:00:02 +0000</pubDate>
				<category><![CDATA[Technology and Science]]></category>
		<category><![CDATA[access]]></category>
		<category><![CDATA[browsers]]></category>
		<category><![CDATA[Crash]]></category>
		<category><![CDATA[databases]]></category>
		<category><![CDATA[Environment]]></category>
		<category><![CDATA[Features]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[memory]]></category>
		<category><![CDATA[name]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[Open]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[port]]></category>
		<category><![CDATA[reloading]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Server Management]]></category>
		<category><![CDATA[SSH]]></category>
		<category><![CDATA[Ubuntu]]></category>
		<category><![CDATA[Web Servers]]></category>
		<category><![CDATA[X]]></category>
		<category><![CDATA[yes]]></category>
		<guid isPermaLink="false">https://massive.news/how-to-enable-http-3-on-nginx/</guid>

					<description><![CDATA[If you’re running NGINX on a modern server, you’re likely leaving performance on the table by...]]></description>
										<content:encoded><![CDATA[<div class="video-container"><iframe width="560" height="315" src="https://www.youtube.com/embed/qxj-cfVgtNY" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></div>
<p>If you’re running NGINX on a modern server, you’re likely leaving performance on the table by sticking with HTTP/2.</p>
<p><cms-inline-toc tocs="[{&quot;id&quot;:&quot;#stepbystep-instructions-for-enabling-http3-on-nginx&quot;,&quot;name&quot;:&quot;Step-by-Step Instructions for Enabling HTTP/3 on NGINX&quot;,&quot;tagName&quot;:&quot;h2&quot;},{&quot;id&quot;:&quot;#step-1-ensure-you-meet-prerequisites-for-http3&quot;,&quot;name&quot;:&quot;Step 1: Ensure You Meet Prerequisites for HTTP/3&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#step-2-open-udp-port-443-on-your-firewall&quot;,&quot;name&quot;:&quot;Step 2: Open UDP Port 443 on Your Firewall&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#step-3-add-the-quic-listener-and-http3-directives-to-your-server-block&quot;,&quot;name&quot;:&quot;Step 3: Add the QUIC Listener and HTTP/3 Directives to Your Server Block&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#step-4-test-and-reload-nginx&quot;,&quot;name&quot;:&quot;Step 4: Test and Reload NGINX&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#step-5-verify-http3-is-active&quot;,&quot;name&quot;:&quot;Step 5: Verify HTTP/3 Is Active&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#enable-http3-without-touching-config-via-runcloud&quot;,&quot;name&quot;:&quot;Enable HTTP/3 Without Touching Config via RunCloud&quot;,&quot;tagName&quot;:&quot;h2&quot;},{&quot;id&quot;:&quot;#wrapping-up&quot;,&quot;name&quot;:&quot;Wrapping Up&quot;,&quot;tagName&quot;:&quot;h2&quot;},{&quot;id&quot;:&quot;#faqs&quot;,&quot;name&quot;:&quot;FAQs&quot;,&quot;tagName&quot;:&quot;h2&quot;},{&quot;id&quot;:&quot;#does-enabling-http3-break-http2-or-http11&quot;,&quot;name&quot;:&quot;Does enabling HTTP/3 break HTTP/2 or HTTP/1.1?&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#why-does-curl-http3-work-but-chrome-still-shows-http2&quot;,&quot;name&quot;:&quot;Why does curl u2013http3 work but Chrome still shows HTTP/2?&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#is-http3-on-nginx-productionsafe&quot;,&quot;name&quot;:&quot;Is HTTP/3 on NGINX production-safe?&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#how-do-i-disable-http3-on-nginx-if-needed&quot;,&quot;name&quot;:&quot;How do I disable HTTP/3 on NGINX if needed?&quot;,&quot;tagName&quot;:&quot;h3&quot;},{&quot;id&quot;:&quot;#do-i-need-a-special-ssl-certificate-for-http3&quot;,&quot;name&quot;:&quot;Do I need a special SSL certificate for HTTP/3?&quot;,&quot;tagName&quot;:&quot;h3&quot;}]"></cms-inline-toc></p>
<p><em>HTTP/3 changes how browsers connect to your server. It reduces latency, improves performance on unstable networks, and can noticeably speed up real-world page loads – especially for mobile users.</em></p>
<p>The problem is that enabling HTTP/3 on NGINX isn’t straightforward. It requires the right version, specific modules, firewall changes, and careful configuration. One small mistake can stop NGINX from restarting.</p>
<p>In this guide, you’ll learn exactly how to enable HTTP/3 on NGINX step by step – from checking compatibility to verifying that it’s working correctly.</p>
<h2 class="wp-block-heading" id="stepbystep-instructions-for-enabling-http3-on-nginx"><strong>Step-by-Step Instructions for Enabling HTTP/3 on NGINX</strong></h2>
<p>Use the steps below to enable and verify HTTP/3 on your Ubuntu server.</p>
<h3 class="wp-block-heading" id="step-1-ensure-you-meet-prerequisites-for-http3"><strong>Step 1: Ensure You Meet Prerequisites for HTTP/3</strong></h3>
<p>Before enabling HTTP/3 (QUIC) on your Ubuntu server, ensure your environment meets the prerequisites. Since HTTP/3 works over UDP rather than TCP, your underlying web server, network firewall, and encryption standards must support it.</p>
<h4 class="wp-block-heading" id="nginx-version-supports-http3"><strong>NGINX Version Supports HTTP/3</strong></h4>
<p>The most important requirement for enabling HTTP/3 is having a compatible NGINX version. According to the official NGINX QUIC documentation, support for QUIC and HTTP/3 was officially introduced in <strong>NGINX version 1.25.0</strong>. In these newer releases, the required ngx_http_v3_module is included in the official Linux binary packages by default.</p>
<p><strong>How to Check Your Current Version:</strong> Run the following command to check your NGINX version and its compiled modules:</p>
<pre><code v-pre>nginx -V 2&gt;&amp;1 | grep --color -- --with-http_v3_module</code></pre>
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="588" src="https://massive.news/wp-content/uploads/2026/05/how-to-enable-http-3-on-nginx.webp" alt="nginx server compile flags" class="wp-image-14014"></figure>
<p>Look for <code v-pre>nginx version: nginx/1.25.0</code> (or higher) and ensure that <code v-pre>--with-http_v3_module</code> is present in the configure arguments.</p>
<p>If your Ubuntu repository ships older “stable” releases (like 1.18.x or 1.24.x) that do not include HTTP/3 support out of the box. Then you can install the <strong>Mainline</strong> version from the official NGINX repositories.</p>
<p>Run the following commands to install the necessary dependencies:</p>
<ol class="wp-block-list">
<li><strong>Install prerequisite packages:</strong></li>
</ol>
<pre><code v-pre>sudo apt update
sudo apt install curl gnupg2 ca-certificates lsb-release ubuntu-keyring</code></pre>
<ol start="2" class="wp-block-list">
<li><strong>Import the official NGINX GPG signing key:</strong></li>
</ol>
<pre><code v-pre>curl https://nginx.org/keys/nginx_signing.key | gpg --dearmor | sudo tee /usr/share/keyrings/nginx-archive-keyring.gpg &gt;/dev/null</code></pre>
<ol start="3" class="wp-block-list">
<li><strong>Add the NGINX Mainline repository for Ubuntu:</strong></li>
</ol>
<pre><code v-pre>echo "deb[signed-by=/usr/share/keyrings/nginx-archive-keyring.gpg] 
http://nginx.org/packages/mainline/ubuntu `lsb_release -cs` nginx" 
| sudo tee /etc/apt/sources.list.d/nginx.list</code></pre>
<ol start="4" class="wp-block-list">
<li><strong>Prioritize NGINX packages (APT Pinning):</strong> This ensures Ubuntu prioritizes the official NGINX repository over its own default repositories.</li>
</ol>
<pre><code v-pre>echo -e "Package: *nPin: origin nginx.orgnPin-Priority: 900n" | sudo tee /etc/apt/preferences.d/99nginx</code></pre>
<ol start="5" class="wp-block-list">
<li><strong>Install the latest NGINX version:</strong></li>
</ol>
<pre><code v-pre>sudo apt update
sudo apt install nginx</code></pre>
<p><strong><em>Suggested read: </em></strong>How to Set Up a Hetzner Server with RunCloud<em>&nbsp;</em></p>
<h4 class="wp-block-heading" id="ssl-certificates-are-configured-http3-requires-tls-13"><strong>SSL Certificates are Configured (HTTP/3 Requires TLS 1.3)</strong></h4>
<p>Unlike older HTTP versions, where HTTPS was a secondary layer, <strong>HTTP/3 inherently requires encryption via QUIC</strong>. You cannot run HTTP/3 over unencrypted http:// connections. Additionally, the QUIC protocol mandates the use of <strong>TLS 1.3</strong> to enable faster 0-RTT (Zero Round Trip Time) handshakes and better security.</p>
<p>Before proceeding, you must ensure:</p>
<ol class="wp-block-list">
<li><strong>You have a valid domain name pointing</strong> to your Ubuntu server’s IP address.</li>
<li><strong>An SSL/TLS Certificate is configured.</strong> A free certificate from Let’s Encrypt (using Certbot) is perfect for this.</li>
<li><strong>TLS 1.3 is enabled in your config.</strong> Verify that your existing NGINX server block contains TLSv1.3 in the ssl_protocols directive.</li>
</ol>
<p>Your current HTTPS block should look something like this before adding HTTP/3:</p>
<pre><code v-pre>server {
    listen 443 ssl;
    server_name example.com;


    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;


    # TLS 1.3 MUST be included for QUIC/HTTP/3 to function
    ssl_protocols TLSv1.2 TLSv1.3;
}</code></pre>
<h4 class="wp-block-heading" id="root-or-sudo-access-to-edit-nginx-config"><strong>Root or Sudo Access to Edit NGINX Config</strong></h4>
<p>Finally, you will need <strong>root or sudo access</strong> to your Ubuntu server. Upgrading to HTTP/3 requires modifying core NGINX configuration files, tweaking firewall rules, and restarting system services.</p>
<h3 class="wp-block-heading" id="step-2-open-udp-port-443-on-your-firewall"><strong>Step 2: Open UDP Port 443 on Your Firewall</strong></h3>
<p>Unlike HTTP/1.1 and HTTP/2 which rely on TCP, HTTP/3 uses the QUIC protocol, which operates entirely over <strong>UDP</strong>. If you don’t explicitly open UDP port 443 on your firewall, client requests will never reach your NGINX HTTP/3 listener, and browsers will silently downgrade back to HTTP/2 over TCP.</p>
<h4 class="wp-block-heading" id="ufw-ubuntu"><strong>UFW (Ubuntu)</strong></h4>
<p>If you are using Uncomplicated Firewall (UFW), which comes standard on Ubuntu, simply run:</p>
<pre><code v-pre>sudo ufw allow 443/udp
sudo ufw reload</code></pre>
<h4 class="wp-block-heading" id="iptables"><strong>iptables</strong></h4>
<p>If you manage your firewall directly using <code v-pre>iptables</code>, run the following to append the UDP rule:</p>
<pre><code v-pre>sudo iptables -A INPUT -p udp --dport 443 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT</code></pre>
<p>After making the changes, you need to save your iptables rules using <code v-pre>netfilter-persistent save</code> or <code v-pre>iptables-save</code>, depending on your server setup</p>
<h4 class="wp-block-heading" id="cloud-firewall-hetzner-gcp-digitalocean"><strong>Cloud Firewall (Hetzner, GCP, DigitalOcean)</strong></h4>
<p>If your server is hosted on a cloud provider, local firewall rules (UFW/iptables) are often overridden or supplemented by cloud-level security groups. The exact steps will vary depending on your cloud provider:</p>
<ul class="wp-block-list">
<li><strong>Hetzner Cloud:</strong> Go to your server’s “Firewalls” tab and add an Inbound rule for Protocol: UDP, Port: 443.</li>
<li><strong>Google Cloud Platform (GCP):</strong> Go to VPC Network &gt; Firewall. Create a new ingress rule targeting your instance, select UDP, and specify port 443.</li>
<li><strong>DigitalOcean:</strong> Navigate to Networking &gt; Firewalls. Add an Inbound Rule for Custom UDP on port 443.</li>
</ul>
<p><strong><em>Pro Tip:</em></strong><em> If you are using RunCloud to manage your infrastructure, our official server setup guides for providers like </em>Hetzner <em>and </em>GCP <em>cover this firewall step in great detail.</em></p>
<h3 class="wp-block-heading" id="step-3-add-the-quic-listener-and-http3-directives-to-your-server-block"><strong>Step 3: Add the QUIC Listener and HTTP/3 Directives to Your Server Block</strong></h3>
<p>Now it’s time to tell NGINX to actually listen for QUIC traffic and advertise HTTP/3 capabilities to the browser.</p>
<p>Open your website’s NGINX configuration file (e.g., <code v-pre>sudo nano /etc/nginx/conf.d/example.com.conf</code> or <code v-pre>/etc/nginx/sites-available/default</code>).</p>
<p>Here is a complete, copy-paste-ready server block configured for HTTP/3:</p>
<pre><code v-pre>server {
    # 1. Standard TCP listener for HTTP/1.1 and HTTP/2 (Fallback)
    listen 443 ssl;
    
    # 2. UDP listener for QUIC and HTTP/3
    listen 443 quic reuseport;


    server_name example.com www.example.com;


    # 3. SSL/TLS Certificates
    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;


    # 4. Enable TLS 1.3 (Required for HTTP/3)
    ssl_protocols TLSv1.2 TLSv1.3;


    # 5. Core HTTP/3 Directives
    http3 on;
    quic_retry on;
    ssl_early_data on;


    # 6. Advertise HTTP/3 to clients via the Alt-Svc header
    add_header Alt-Svc 'h3=":443"; ma=86400' always;


    # The rest of your location blocks go here...
    location / {
        try_files $uri $uri/ =404;
    }
}</code></pre>
<p>Each directive below controls a specific part of how HTTP/3 works in NGINX. Here’s what each one does and why it matters.</p>
<p><code v-pre><strong>listen 443 quic reuseport;</strong><br /></code>Tells NGINX to listen for UDP traffic on port 443 and distributes the processing load across multiple worker processes.</p>
<p><code v-pre><strong>http3 on;</strong><br /></code>enables the HTTP/3 protocol decoding for the current server block.</p>
<p><code v-pre><strong>ssl_protocols TLSv1.3;</strong><br /></code>Configures the use of TLS 1.3, the strict encryption standard required by the QUIC protocol.</p>
<p><code v-pre><strong>quic_retry on;</strong><br /></code>Defends against UDP spoofing attacks by requiring clients to validate their IP address during the handshake.</p>
<p><code v-pre><strong>ssl_early_data on;</strong><br /></code>Enables 0-RTT (Zero Round Trip Time), allowing returning clients to resume encrypted connections instantly without handshake delays.</p>
<p><code v-pre><strong>add_header Alt-Svc 'h3=":443"; ma=86400' always;</strong><br /></code>Tells connecting web browsers, “Hey! I support HTTP/3 on port 443, remember this for the next 86,400 seconds (1 day).”</p>
<p>If you host <strong>multiple websites</strong> (virtual hosts) on the same NGINX server, you need to be careful with the reuseport parameter. <strong>You can only define </strong><strong>reuseport</strong><strong> once per IP and port combination.</strong></p>
<p>For your primary website, use: listen 443 quic reuseport;</p>
<p>For all <strong>other</strong> websites on the same server, omit reuseport: listen 443 quic; If you put reuseport in multiple server blocks, NGINX will throw an error and refuse to start.</p>
<p><strong><em>Suggested read: </em></strong>How to Set Up a Google Cloud Server to Host Your Websites<em>&nbsp;</em></p>
<h3 class="wp-block-heading" id="step-4-test-and-reload-nginx"><strong>Step 4: Test and Reload NGINX</strong></h3>
<p>Whenever you alter NGINX configurations, you must test the syntax before applying the changes to prevent your live server from crashing.</p>
<p>Run a configuration test to confirm your changes are valid before reloading NGINX:</p>
<pre><code v-pre>sudo nginx -t</code></pre>
<p>If the output says nginx: configuration file /etc/nginx/nginx.conf test is successful, apply the changes instantly without dropping active connections by reloading NGINX:</p>
<pre><code v-pre>sudo nginx -s reload</code></pre>
<h3 class="wp-block-heading" id="step-5-verify-http3-is-active"><strong>Step 5: Verify HTTP/3 Is Active</strong></h3>
<p>You can use a web-based testing tool like http3check.net to check your setup is working as expected. Simply type your website’s domain name into the search bar and click “Check”. The tool will attempt a QUIC connection from its own servers and confirm whether UDP port 443 is open, TLS 1.3 is functioning, and your NGINX instance is successfully serving HTTP/3.</p>
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="632" src="https://massive.news/wp-content/uploads/2026/05/how-to-enable-http-3-on-nginx-1.webp" alt class="wp-image-14015"></figure>
<p><strong><em>Suggested read: </em></strong>How to Fix ERR_SSL_VERSION_or_CIPHER_MISMATCH<em>&nbsp;</em></p>
<h2 class="wp-block-heading" id="enable-http3-without-touching-config-via-runcloud"><strong>Enable HTTP/3 Without Touching Config via RunCloud</strong></h2>
<p>Managing NGINX configurations manually can quickly become a headache, especially as your server scales. One typo in your <code v-pre>nginx.conf</code>, forgetting to open a UDP port, or accidentally duplicating the reuseport directive across multiple server blocks can crash your entire web server.</p>
<p>If you have just completed all the manual steps above, you might be wondering: <em>Is there an easier way to do this for my next server?</em></p>
<p>The answer is ‘<strong>yes</strong>’, and the solution is <strong>RunCloud</strong>.</p>
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="602" src="https://massive.news/wp-content/uploads/2026/05/how-to-enable-http-3-on-nginx-2.webp" alt="enable http3 in runcloud nginx" class="wp-image-14016"></figure>
<p>With <strong>RunCloud</strong>, you can skip the command line entirely, instead enabling HTTP/3 for each web application directly from your dashboard with a single toggle.</p>
<p><strong>Here’s how RunCloud simplifies the process:</strong></p>
<ul class="wp-block-list">
<li><strong>No SSH Required:</strong> You never have to log in to your server’s terminal to edit configuration files.</li>
<li><strong>No </strong><strong>reuseport</strong><strong> Management:</strong> RunCloud’s automated NGINX stack intelligently handles the listen 443 quic reuseport rule across multiple domains. You never have to worry about conflicting server blocks.</li>
<li><strong>One-Click Toggles:</strong> Simply navigate to your Web Application settings, toggle HTTP/3 on, and RunCloud safely reloads your NGINX server in the background.</li>
</ul>
<p>For more details on how effortlessly this works, check out the official RunCloud documentation on enabling HTTP/3.</p>
<h2 class="wp-block-heading" id="wrapping-up"><strong>Wrapping Up</strong></h2>
<p>In this post, we have discussed the steps required to enable HTTP/3 on an NGINX server. As you can see, the manual process requires several intricate steps: checking NGINX versions, configuring firewalls for UDP port 443, and carefully modifying server block directives.</p>
<p>While the benefits of HTTP/3 are worth the effort, manual configuration is tedious and prone to human error. <strong>You don’t have to do it this way.</strong></p>
<p>You can completely skip the command line and complex configuration files by using <strong>RunCloud</strong>.</p>
<p>RunCloud is a server management dashboard for PHP and web applications. It provides a visual interface for configuring firewalls, managing databases, deploying code via Git, and enabling features like HTTP/3 without editing configuration files.</p>
<p><strong>If you want to avoid manual setup and reduce the risk of configuration errors, </strong>sign up for RunCloud <strong>and enable HTTP/3 in a few clicks.</strong></p>
<h2 class="wp-block-heading" id="faqs"><strong>FAQs</strong></h2>
<div id="rank-math-faq" class="rank-math-block">
<div class="rank-math-list ">
<div id="faq-question-1776770627853" class="rank-math-list-item" readability="9">
<h3 class="rank-math-question " id="does-enabling-http3-break-http2-or-http11"><strong>Does enabling HTTP/3 break HTTP/2 or HTTP/1.1?</strong></h3>
<div class="rank-math-answer " readability="13">
<p>No, enabling HTTP/3 does not break older protocols because it runs on UDP port 443, while HTTP/2 and HTTP/1.1 operate over TCP. Modern web servers and browsers use a “fallback” mechanism that ensures that if a client doesn’t support QUIC (the foundation of HTTP/3), the connection seamlessly reverts to HTTP/2 without the user noticing.</p>
</div>
</div>
<div id="faq-question-1776770635135" class="rank-math-list-item" readability="8.5">
<h3 class="rank-math-question " id="why-does-curl-http3-work-but-chrome-still-shows-http2"><strong>Why does curl –http3 work but Chrome still shows HTTP/2?</strong></h3>
<div class="rank-math-answer " readability="12">
<p>Command-line tools like curl can be forced to use a specific protocol, but Chrome requires the server first to send an Alt-Svc (Alternative Services) header to “discover” that HTTP/3 is available. Because HTTP/3 runs over UDP, Chrome often completes the initial handshake over TCP (HTTP/2) and switches to HTTP/3 only for subsequent requests or after the protocol is cached in the browser’s memory.</p>
</div>
</div>
<div id="faq-question-1776770641265" class="rank-math-list-item" readability="9.5">
<h3 class="rank-math-question " id="is-http3-on-nginx-productionsafe"><strong>Is HTTP/3 on NGINX production-safe?</strong></h3>
<div class="rank-math-answer " readability="14">
<p>Yes, HTTP/3 is considered production-safe and is officially supported in the NGINX mainline releases, though you should monitor your server’s CPU usage closely. Because QUIC handles encryption and packet loss at the application level rather than the kernel level, it can be more CPU-intensive than HTTP/2, especially during high-traffic spikes.</p>
</div>
</div>
<div id="faq-question-1776770648553" class="rank-math-list-item" readability="9.5">
<h3 class="rank-math-question " id="how-do-i-disable-http3-on-nginx-if-needed"><strong>How do I disable HTTP/3 on NGINX if needed?</strong></h3>
<div class="rank-math-answer " readability="14">
<p>To disable HTTP/3, simply remove the quic and reuseport parameters from your listen 443 directives, and delete the add_header Alt-Svc line from your configuration file. Once you run nginx -s reload, the server will stop advertising QUIC capabilities and will no longer accept connections over UDP port 443, forcing all traffic back to standard TCP.</p>
</div>
</div>
<div id="faq-question-1776770654979" class="rank-math-list-item" readability="8.5">
<h3 class="rank-math-question " id="do-i-need-a-special-ssl-certificate-for-http3"><strong>Do I need a special SSL certificate for HTTP/3?</strong></h3>
<div class="rank-math-answer " readability="12">
<p>No, your standard SSL/TLS certificate (such as a free Let’s Encrypt certificate) will work perfectly. However, the QUIC protocol explicitly requires <strong>TLS 1.3</strong>, so your NGINX configuration must enable TLS 1.3.</p>
</div>
</div>
</div>
</div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>After 25 years, Valve reworks Counter-Strike&#8217;s reload system</title>
		<link>https://massive.news/after-25-years-valve-reworks-counter-strikes-reload-system/</link>
		
		<dc:creator><![CDATA[wiredgorilla]]></dc:creator>
		<pubDate>Thu, 19 Mar 2026 17:00:15 +0000</pubDate>
				<category><![CDATA[Technology and Science]]></category>
		<category><![CDATA[BASIC]]></category>
		<category><![CDATA[Counter-Strike]]></category>
		<category><![CDATA[CS2]]></category>
		<category><![CDATA[Gaming]]></category>
		<category><![CDATA[Popular]]></category>
		<category><![CDATA[realism]]></category>
		<category><![CDATA[reddit]]></category>
		<category><![CDATA[reloading]]></category>
		<category><![CDATA[Valve]]></category>
		<category><![CDATA[Weapons]]></category>
		<category><![CDATA[WHO]]></category>
		<guid isPermaLink="false">https://massive.news/after-25-years-valve-reworks-counter-strikes-reload-system/</guid>

					<description><![CDATA[But Counter-Strike 2 is somewhat unique in changing its reload system mid-stream, forcing the change on...]]></description>
										<content:encoded><![CDATA[<div><img decoding="async" src="https://massive.news/wp-content/uploads/2026/03/after-25-years-valve-reworks-counter-strikes-reload-system.png" class="ff-og-image-inserted"></div>
<p>But <em>Counter-Strike 2</em> is somewhat unique in changing its reload system mid-stream, forcing the change on players who have become acclimated to reflexively reloading whenever it’s safe. This is the kind of sudden change that could have major ripple effects on casual and pro players alike, turning reloads from an almost unconscious act into a tactical cost-benefit decision players have to spend mental resources on.</p>
<p>It’s not hard to find players who have been instantly incensed by the decision, of course. One popular Reddit post is already demanding that Valve revert the reload changes, asserting that “no one in the community asked for this… CS has had its reload behavior for decades, and suddenly we’re changing a fundamental mechanic that nobody had an issue with.”</p>
<p>Even in the comments of that Reddit thread, though, you can find players supporting the change by arguing that “we should reward ammo management” or pointing out that “now players who take a few potshots are actively reducing their effectiveness in a group fight by having less bullets.”</p>
<p>Other players say the new era of <em>CS2</em>&nbsp;<span>ammo awareness already reminds them of the old days of&nbsp;<em>Counter-Strike 1.6</em>, when</span>&nbsp;players had to explicitly purchase their limited ammo. “Ammo scarcity is actually a very basic, rudimentary, and forgotten theme in CS,” as one Redditor put it. “Why even have an ammo system in games if you don’t have to manage it?” another asked on gaming forum ResetEra.</p>
<p>Many players seem to be reserving judgment until they’ve had more chance to play with the rebalanced reload system. But even casual <em>Counter-Strike</em> onlookers are absorbing the impact of such a sudden and major change to a long-running and ultra-popular shooter. “As someone who hasn’t played CS in a very long time this hit me like if they changed the rules of chess,” one such player wrote on ResetEra.</p>
<div class="video-container"><iframe width="560" height="315" src="https://www.youtube.com/embed/23iz6uS_kQ0" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></div>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
