What Is a Reverse Proxy? In Plain English

You have more than one website or app on a server, and suddenly the simple question “where should this request go?” becomes the thing that breaks everything.

Short version: a reverse proxy is a front desk for your server. It receives visitors from the internet, looks at the domain name they used, and forwards each request to the correct website or app running behind it. Tools like Nginx, Caddy, and Traefik are commonly used as reverse proxies, especially when you want several projects, HTTPS, and clean domain routing on one server.

What does a reverse proxy actually do?

A reverse proxy sits between the public internet and your apps.

Think of your server like an office building. The building has one street address, but many rooms inside. One room may be your blog, another may be a dashboard, another may be a private file app.

Without a front desk, visitors would need to know exactly which room to knock on. That is awkward and unsafe. A reverse proxy is the front desk. It sees that someone asked for blog.example.com and sends them to the blog room. It sees app.example.com and sends them somewhere else.

The visitor does not need to know how the inside is arranged. They only see a normal website address. The reverse proxy handles the internal handoff.

In plain terms, it answers: “This request came in through this domain. Which app should receive it?”

How is a reverse proxy different from a regular proxy?

The word “proxy” just means “someone acts on behalf of someone else.” The direction is what changes.

A regular proxy usually acts for the person browsing the web. A reverse proxy acts for the websites and apps on your server.

So if your browser uses a proxy, the proxy hides or manages your outbound traffic. If your server uses a reverse proxy, it organizes inbound traffic before it reaches your apps.

That difference matters because most hosting problems involve inbound traffic: domains, HTTPS, ports, redirects, and errors like 502 Bad Gateway.

Why do websites and apps need a reverse proxy?

A reverse proxy becomes useful when one server has to do more than one thing.

For example, you might run WordPress on one domain, a Node.js app on another, and Nextcloud on a third. All of them need normal web addresses. All of them need HTTPS. All of them may run in different internal places on the server.

The reverse proxy makes that manageable. It can send example.com to one project and files.example.com to another without asking visitors to remember strange addresses or port numbers.

It also helps with HTTPS. Many setups put the certificate work at the reverse proxy layer, so the public connection is encrypted before traffic is passed inside the server. If you are still getting comfortable with certificates, this connects closely to getting free HTTPS on your server.

It also makes hosting multiple sites less messy. Instead of every app trying to own the front door, the reverse proxy owns the front door and gives each app a clear place behind it. That is the basic idea behind hosting multiple websites on one server.

What usually breaks with a reverse proxy?

Most reverse proxy problems are not mysterious. They are usually one of a few mix-ups.

A 502 Bad Gateway often means the reverse proxy answered the visitor, but could not reach the app behind it. The front desk is open, but the room it tried to call is empty, closed, or using a different internal address than expected.

A 404 Not Found can mean the request reached something, but not the thing you intended. It is like the receptionist sending a package to the wrong department.

HTTPS errors usually point to a certificate or domain mismatch. The browser expected a valid certificate for one name, but the server presented the wrong one, an expired one, or none at all.

Redirect loops are another common one. That is when the browser keeps being told to go from one address to another, then back again. It feels like walking between two doors where each sign points at the other.

When this happens, server logs are often the fastest way to see which layer answered and where the request got stuck. If logs feel unreadable, start with how to read server logs when something breaks.

FAQ

Is Nginx a reverse proxy? Yes. Nginx can serve websites directly, but it is also widely used as a reverse proxy in front of apps.

Is Caddy a reverse proxy? Yes. Caddy is often used as a reverse proxy and is known for making HTTPS certificate handling simpler.

Is a reverse proxy the same as a load balancer? Not exactly. A load balancer spreads traffic across multiple back-end servers. A reverse proxy may do that, but it can also simply route domains to the right app on one server.

Do I need a reverse proxy for one simple website? Maybe not. If one website owns the whole server, the setup can be simpler. The moment you add more apps, subdomains, or HTTPS routing, a reverse proxy starts to make sense.

The shortcut

Server Manager helps you keep the “front desk” understandable. Instead of ending up with hidden routing rules that only make sense on the day you wrote them, you can see which domain points to which project and what each public address is meant to reach.

That matters when the common failures show up: a domain going to the wrong app, a broken HTTPS certificate, a 502 Bad Gateway after a project moved, or one project accidentally disturbing another. The real benefit is not avoiding every problem forever; it is being able to understand the setup when something changes months later.

Your server stays easier to reason about. Each project has a visible place, and the route from domain to app does not become a private memory test.

What changes when traffic has one clear door?

A reverse proxy is not magic. It is a traffic guide.

Once you understand that, many hosting problems become less scary. Your domain points to the server. The reverse proxy receives the request. Then it sends the visitor to the right app.

That mental model gives you a calmer way to debug. Instead of “the site is broken,” you can ask: did the visitor reach the front door, did the front door choose the right room, and was the room open? That is the win: fewer mysteries, cleaner hosting, and a setup you can still understand later.