About ProxyForge

Last updated 22 October 2026

I'm Brent Alexis, an IT tech from Trinbago. ProxyForge is my one-person project - me, myself and I.

As I expanded into DevOps, I kept running into the same problem: config snippets from forums and old blog posts that look right but don't work. A directive that's been deprecated, one that isn't allowed in the file you put it in, or a missing line that only shows up when the server refuses to start. ProxyForge gives you a config that loads first time, and tells you what every line does.

How it's tested

Every generator's output was tested on real Nginx 1.27 and Apache 2.4 servers during development, in a test lab I run with Docker. Configs went through nginx -t or apachectl configtest, and where it mattered, real requests to check they actually behaved. That's how traps like SSLStaplingCache inside a <VirtualHost> (Apache won't start) or Let's Encrypt renewals failing behind an HTTPS redirect got caught and fixed. The testing happened during development, not live in your browser each time.

AI helped me build and test it. Thank goodness for AI. But nothing ships until a real server has passed it.

Built with feedback

Some of the best options came from people's comments - "Behind Cloudflare" and "Older Nginx" were both suggested in launch week. You can see every change on the What's new page.

Free, and how it pays its way

ProxyForge is free, with no signup, and it runs in your browser - what you type isn't sent anywhere. The site is supported by ads and a few affiliate links to hosting and tools. The privacy page has the details.

Get in touch

Config didn't work on your setup, or you'd like another generator? Email admin@proxyforge.tech with the error and your Nginx or Apache version. Real errors get added to the FAQ.

How to use ProxyForge · FAQ: common errors · What's new · Featured On · Privacy