What's new

Every change to ProxyForge, newest first. Several of these came straight from people's comments and questions.

Last updated 28 October 2026 · Something not working? See the FAQ or email admin@proxyforge.tech.

28 October 2026

• New tool: Basic Protection Generator. Blocks exposed .git and .env files, backups and known scanner tools, with an optional Nginx rate limit. It's basic protection, not a full WAF, and was tested on Nginx 1.27 and Apache 2.4. The docs now include Cloudflare WAF rules that pair with it.
• The contact email is now in the footer of every generator, and search engines and AI assistants now see one consistent name, ProxyForge, for each tool.

27 October 2026

• New FAQ answer: why nginx -s reload can say OK while Nginx keeps the old config. Reported on Indie Hackers, reproduced and confirmed in my Nginx 1.27 test lab before writing it up.

26 October 2026

• Two new FAQ answers, both suggested by people on Indie Hackers: 502 Bad Gateway and bind() ... Address already in use.

25 October 2026

• Small housekeeping: an extra security header that turns off camera, microphone, location and payment access the site never uses, icons that load once instead of on every page, and clearer page structure for screen readers.

22 October 2026

• Build a link to a ready-made config. The docs now explain every setting you can put in a ProxyForge link, so a script, a guide or an AI assistant can open a generator with the right options already filled in. See the link format.
• Clearer wording: the badges now say "Tested on Nginx 1.27 · Apache 2.4", which is exactly what was done during development.

19 October 2026

• Anonymous Copy counter: clicking Copy now also requests a tiny file, so I can see which generators people actually use. No cookies and nothing about you is recorded. The privacy page explains it.
• Tighter hosting: only the site's own files are served now, nothing else from the project folder.

18 October 2026

• Safer share links. Every field is now checked, so a crafted link can't slip extra lines into a config or the Certbot command. If a value isn't valid, you'll see a warning and the example value is used instead. Normal configs come out exactly the same.

15 October 2026

• New FAQ page with direct fixes for common errors: unknown directive "http2", Let's Encrypt renewals failing, ProxyPass in .htaccess, 413 errors, SSLStaplingCache, Cloudflare redirect loops and more. The generators link to the right answer.

13 October 2026

• Let's Encrypt renewals keep working behind the HTTPS redirect. The Config and Redirect generators now let /.well-known/acme-challenge/ through on port 80, so certbot renew doesn't fail about 60 days later.
• A 5-minute video tutorial (Nginx reverse proxy with HTTPS) is now in the how-to guide.

10 October 2026

• New Older Nginx (before 1.25.1) option on the Config and SSL generators. It uses listen 443 ssl http2; instead of http2 on;, so configs load on older distro packages like Ubuntu 22.04 and Debian 11. Suggested in a launch comment.

9 October 2026

• WebSocket support on Nginx now uses the standard map $http_upgrade $connection_upgrade pattern, so normal requests aren't sent with an "upgrade" header.

7 October 2026

• New Behind Cloudflare option on the Config Generator: restores real visitor IPs in your logs and explains the SSL setting that avoids redirect loops. Suggested in a launch comment.

Early October 2026

• Every output now ends with the commands to test the config and roll back if something goes wrong.

28 September 2026

• ProxyForge went live with four free generators: Config (reverse proxy, WordPress, static sites, PHP-FPM), Redirect, SSL / Let's Encrypt and Security Headers, for Nginx and Apache.

How to use ProxyForge · FAQ: common errors · About · Featured On · Privacy