The Reverse Proxy Setup
A hardened front door for up to three applications you already run — HTTPS ends at the proxy, scanner probes are turned away, and traffic is balanced across your backends while the apps behind it stay exactly as they are.
Every application you expose to the internet is another door for attackers to try: another certificate to keep valid, another port answering strangers, another raw error page when a backend dies. Run three apps that way and you're defending three doors.
We put one reverse proxy — Caddy or nginx, your choice — in front of them all. Attackers meet a filtered entry point that answers only for the hostnames you publish; your visitors get fast, encrypted connections and a clean holding page on the rare occasion a backend drops. Your applications themselves don't change at all.
Our engineers build these front doors every week on the same two platforms, so the trade-off is explained to you straight before you book: Caddy fetches and renews its own HTTPS certificates, while nginx adds per-IP rate limiting with a certificate you supply. Either way, you get one entry point you can reason about instead of three exposures you can't.
What's included
HTTPS terminated at the proxy for up to three applications — Caddy obtains and renews its own certificates, or we install the certificate you supply on nginx
The probes that come before every break-in refused at the door: vulnerability scanners, requests for files like /.git and /.env, and request methods your app never uses
Per-IP rate limiting on nginx — gentle across the site, strict on your login page — plus IP allow and deny lists on either platform
Traffic balanced across up to three backends per application, with failing backends dropped from rotation and visitors shown a clean holding page instead of a raw error
WebSockets and live streams passed through correctly, so chat and dashboards keep working behind the proxy
A structured log of every request — who asked, for what, and how long your backend took — ready for whatever monitoring you adopt later
Recorded proof of every protection working, a plain-English operations sheet, and a snapshot you can roll back to
Before you order
Have these ready so we can start the moment you order. The delivery clock only runs while we have them.
SSH access with sudo or root to the machine the proxy will run on: a clean host, or one already running Caddy or nginx
Up to three applications that are already running, each with its hostname and the address and port of each backend
Your pick of Caddy or nginx
A certificate for each hostname, or on Caddy, DNS already pointing at the proxy with ports 80 and 443 open
How it works
Book it — pay the fixed price and tell us the target environment. No scoping call first.
We deliver — an experienced specialist runs our standard workflow for this exact task. You can watch progress and message them in the portal.
Hand-off — you get the deliverables, the documentation, a rollback snapshot, and a walkthrough if you want one.
Who does it
A salaried Support Resort specialist with more than ten years in the field, working from a runbook we've been refining since 2003 — supervised by senior management, never a marketplace contractor. You'll see who is assigned and can message them about this task directly in your portal.
FAQ
Ask about this task
Our assistant knows the scope document and runbook behind this service. Ask what's covered, what isn't, or whether it's the right task for your situation.
Answers come from our published scope documents. Prefer a person? Switch to the "Email us" tab — a senior manager replies personally, usually the same weekday.
Related services
The Virtual Domain Setup
Put a live domain on a web server you already run, pointed at your folders or apps (up to five paths), with its own logs and redirects, your SSL certificate installed, and PHP wired up where your site needs it. Priced per domain: book one, or as many as you need.
The Web Server Install
We turn a fresh Linux server into a secured, fast web server — Caddy, Nginx, or Apache — closed off to the exposures attackers scan for and sized to handle real traffic, ready for the sites you put on it next.
The Linux Server Hardening
One production Linux server closed off at the operating-system level to the break-in routes attackers rely on — with before-and-after evidence of every change we make.