// SYS.ONLINE — 2501.AI COMMAND INTERFACE
[STATUS: ACTIVE]
2501/Agent specialties/Reverse Proxy Manager/Reverse proxy cannot reach the server behind it

SOLUTION //

Reverse Proxy Manager

Reverse proxy cannot reach the server behind it

The proxy is up but the site behind it is not. How 2501 tells a server that is really down from a routing mistake on nginx or Traefik, and fixes only the mistake.

A reverse proxy answering with an error because it still sends traffic to an old address serves the site again after 2501 corrects the route and applies it with a reload, keeping live connections open

ServiceNow or another ITSM

Your rules, confirmation and blacklists

Investigate only, with a person, or on its own

On-prem, cloud or hybrid

SOLUTION_BRIEFING

// HOW 2501 HANDLES IT

When a reverse proxy answers with an error instead of the site, restarting the proxy is the reflex, but it briefly takes every site on it offline and fixes nothing if the fault is in the server behind it. 2501 finds out whether that server is really down or the proxy is sending traffic to the wrong place, and fixes only what belongs to the proxy.

That server may have crashed, moved to a new address or dropped off the network, and from outside each of those looks the same.

What 2501 does

The Reverse Proxy specialty covers nginx, Traefik and similar proxies. It investigates before it changes anything, and tells a server that is genuinely down apart from a routing mistake in the proxy. A routing mistake, such as traffic still sent to an old address, is corrected with the smallest change that solves it, validated before it takes effect and applied with a reload. It then confirms the site answers through the proxy, and reports what it found and changed.

How 2501 handles a reverse proxy that cannot reach the server behind it: signal, tell a server that is really down from a routing mistake in the proxy, correct the route within your rules and apply it with a reload, confirm the site answers through the proxy

You stay in control

  • You choose the level: investigate only, act after a person confirms, or act on its own within your rules. The level is set per specialty, not per ticket.
  • Reload, not restart: the proxy is restarted only when it has stopped or a change truly needs it, so live connections stay open.
  • Some calls stay with a person: a server that is really down, fixes that need code or DNS changes, changes that affect several tenants on one proxy, and anything that looks deliberate, such as a maintenance page.
  • Your rules apply: which proxies and sites may change unattended, and which change windows apply.

Frequently asked

Does it fix the server behind the proxy? No. A server that is really down goes to a person with what the agent found, and a network or name resolution fault can be handed to the agent that covers it.

Can it diagnose without changing anything? Yes. In investigate-only mode it reports whether the fault is in the proxy or behind it, and the fix it would make, and changes nothing.

Related

> READY_TO_DEPLOY

SEE IT ON YOUR OWN INFRASTRUCTURE

Book a technical demo and walk through your own environment with the 2501 team.

REQUEST DEMO

CONTACT SALES