Proxy says "Could not connect to default/fallback server" — how do I fix it?

"Could not connect to default/fallback server" means your proxy can't reach the backend it's trying to send players to. It's almost always a config or connectivity detail on the backend side.

What to check

1. In the proxy config, confirm each backend's IP:port is correct — use the backend's real connection address.
2. Make sure the backend server is actually online.
3. Confirm the backend is in offline-mode (online-mode=false) — a proxy can't hand off to an online-mode backend.
4. Verify the fallback/default server name in the config matches a listed server.

Tip: The most common culprits are a wrong IP:port and a backend left in online-mode. Check those two first.

Frequently asked questions

Why can't the proxy connect to an online-mode backend? The proxy performs authentication itself, so backends must be in offline-mode. Set online-mode=false on each backend (and secure them with BungeeGuard).

Where do I find the backend's real address? In the backend server's Console/connection details — that exact IP:port is what goes in the proxy config.

The fallback name doesn't work — why? The default/fallback server name in the proxy config must exactly match one of the servers you've listed.