medium
likely
Network · AGN-KB-NET-0006
HTTP or CDN error while fetching server content
This one is not certain. It is marked likely: the guidance is safe and reasonable, but the diagnosis is not proven for every case. If it does not match what you are seeing, stop and ask rather than pushing on.
The server that hands out AGN's files answered with an error. This one is almost certainly on our side.
What you see
- A numeric HTTP status appears in the connection or download error
- Often affects everyone joining at the same time
What usually causes it
- A misconfigured or missing file on the asset host
- A reverse proxy or CDN returning an error
- A rate limit being hit
Worth checking first
- Record the exact status number and the URL if one is shown (the tool redacts tokens from it)
- Ask whether other players see it at the same moment
Safe steps, one at a time
- Retry once — 502 and 503 are often momentary
- Send the report with the exact status code; this one is usually ours to fix, not yours
These are suggestions, not instructions. Do only what you are comfortable with, back up anything important first, and stop if a step does not match what is on your screen. Advice, risk and responsibility.
When to stop and ask staff
Escalate every 5xx and every 404 on an AGN host. These are server-side by definition.
Looks like
AGN server
What staff will need
- Exact status code
- The URL path if visible
- Timestamp
- Whether others are affected
Applies to
Applies to AGN-hosted asset and API endpoints behind Caddy.
Last reviewed Fri Sep 18.