ProxyForgeNginx & Apache config generators
✓ Tested on Nginx 1.27 · Apache 2.4

Nginx & Apache Config Generator

ProxyForge is a free, browser-based Nginx and Apache config generator for reverse proxies, WordPress, static sites and PHP-FPM, tested on real servers. Fill in the details on the left and copy the result on the right. It's one of five free tools, along with the Redirect, SSL / Let's Encrypt, Security Headers and Basic Protection generators.

Why ProxyForge

  • Nginx and Apache in one place. One form for both servers. On Apache, choose a .htaccess file for shared hosting or a full virtual host for your own server.
  • Tested on real servers. The output was run on real Nginx 1.27 and Apache 2.4 servers during development, with nginx -t, apachectl configtest and real requests, not just read over. How it's tested
  • Errors linked to fixes. Common errors link to tested fixes in the FAQ and guides like Nginx rewrite vs return 301, and every config ends with test-and-rollback steps.
  • Free, no signup, runs in your browser. What you type isn't sent anywhere, and a shared link keeps your settings.

Most config generators produce something that looks right but breaks on a real server: a missing directive, one that isn't allowed in the file you put it in, or syntax a newer version has deprecated. The testing happened during development, not live each time you generate a config. See How to use ProxyForge for every setting and where the output goes.

How it works

STEP 1

Pick Nginx or Apache, and what you're setting up — a reverse proxy, WordPress, a static site, or a PHP-FPM app.

STEP 2

Fill in your domain and backend details. Toggle HTTPS, gzip, or WebSocket support as needed — the config updates live as you go.

STEP 3

Copy the result onto your server and test it before going live: nginx -t then reload on Nginx, or load a page and check the error log for Apache .htaccess. No signup, no accounts — everything runs in your browser.

Where your app is actually running.
Nginx's default is 1m — raise this if your site accepts larger uploads. PHP and WordPress also have PHP's own upload limits. Getting a 413 error?
Assumes a certificate is already issued (e.g. via Certbot).
Needed for live reload, sockets, or streaming APIs.
Restores real visitor IPs and warns about the HTTPS redirect loop. Seeing ERR_TOO_MANY_REDIRECTS?
E.g. the Ubuntu 22.04 and 24.04, Debian 12 and AlmaLinux 9 packages. Check yours with nginx -v. Changes the HTTPS block only. Seeing unknown directive "http2"?
Adds listen [::]:80 (and [::]:443 with HTTPS). Tick it if your server has a public IPv6 address (check with ip -6 addr) and your domain has an AAAA record. If IPv6 is disabled in the server's kernel, Nginx can refuse to start with these lines.
nginx.conf ✓ Tested on Nginx 1.27 

        

      

      

      
Common errors: 502 Bad Gateway · App gets /apifoo instead of /api/foo · ProxyPass not allowed in .htaccess · Reload said OK, change didn't apply · Upload fails on Apache · Too many redirects behind Cloudflare


      

        
Deploying this on a server?

        
A couple of things you'll likely need:

        

          
          
          

            
              UptimeRobot
              Free uptime monitoring — get alerted the moment your newly deployed site stops responding.
            
            Get started
          

          

            
              Vultr
              Simple cloud servers with a wide range of data center locations.
            
            Get started
          

          

            
              SSL.com
              Need a real certificate for the SSL block above? SSL.com issues them.
            
            Get started
          

        

        
Some links above are affiliate links — signing up through them may earn this site a small commission at no extra cost to you. See the privacy policy for details.