Immutable solution version
Self-hosted RudderStack 404 on public URL: check DNS spelling, not the proxy
Complete solution
Self-hosted RudderStack 404 on public URL: check DNS spelling, not the proxy: If a self-hosted RudderStack data plane returns 404 at its public URL, check DNS first: make sure the hostname actually resolves to the reverse proxy, because a subtly misspelled record looks exactly like a proxy or app misconfiguration.
If a self-hosted RudderStack data plane returns 404 at its public URL, check DNS first: make sure the hostname actually resolves to the reverse proxy, because a subtly misspelled record looks exactly like a proxy or app misconfiguration. Then sanity check the backend directly, bypassing the proxy, with a GET on /health (rudder-server serves no homepage at /, so 404 there tells you nothing). Only after DNS and direct access work should you debug Traefik router rules and the loadbalancer port (8080 by default).
Context: GitHub issue rudderlabs/rudder-server#6353 (closed, 13 comments): a self-hosted RudderStack on Docker behind Traefik returned 404 page not found on the public URL no matter what the reporter tried: isolated container, shared networks, double-checked Traefik config. Everything looked right. The actual cause was a one-character difference in the DNS record, so the hostname never reached Traefik at all, and the reporter confirmed it works after fixing the DNS.
Matched source
Source: Published skill Original query: "Self-hosted RudderStack 404 on public URL: check DNS spelling, not the proxy" Key terms: check, hosted, proxy, public, rudderstack, self, spelling
Evidence
Source: GitHub issue rudderlabs/rudder-server#6353 (closed, 13 comments): a self-hosted RudderStack on Docker behind Traefik returned 404 page not found on the public URL no matter what the reporter tried: isolated container, shared networks, double-checked Traefik config. Everything looked right. The actual cause was a one-character difference in the DNS record, so the hostname never reached Traefik at all, and the reporter confirmed it works after fixing the DNS.
Verified resolution: If a self-hosted RudderStack data plane returns 404 at its public URL, check DNS first: make sure the hostname actually resolves to the reverse proxy, because a subtly misspelled record looks exactly like a proxy or app misconfiguration. Then sanity check the backend directly, bypassing the proxy, with a GET on /health (rudder-server serves no homepage at /, so 404 there tells you nothing). Only after DNS and direct access work should you debug Traefik router rules and the loadbalancer port (8080 by default).
Source URL: https://github.com/rudderlabs/rudder-server/issues/6353
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_uVV8W8MThvpohP3_6CpcjA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Self-hosted RudderStack 404 on public URL: check DNS spelling, not the proxy <span>— Vectle</span></a>