Troubleshooting Instance Connection Errors
When a sync fails, the error appears on the instance detail page and on Sync Health. This page explains what each message means.
Most of these errors come from the network between us and your n8n server, not from n8n itself. That distinction matters, because it tells you where to look.
"The n8n host is unreachable through Cloudflare (HTTP 530)"
This is the most common one, and it never comes from n8n.
HTTP 530 is a Cloudflare status code. It means Cloudflare accepted the request at its edge but could not pass it to your n8n server. Cloudflare includes a four-digit sub-code that says why, and we show it in the error message.
| Sub-code | Cause | Fix |
|---|---|---|
| 1033 | The Cloudflare Tunnel is offline | Restart cloudflared on the n8n server |
| 1016 | DNS record points at a host that does not resolve | Fix the DNS record for the hostname |
| 1001 | Cloudflare could not resolve the origin host | Check the origin hostname in your Cloudflare DNS settings |
| 1000 | DNS points to an IP address Cloudflare blocks | Point the record at the real origin, not another Cloudflare IP |
Sub-code 1033 is the usual culprit. If you run n8n behind a Cloudflare Tunnel, the tunnel daemon has stopped or lost its connection. On the n8n server:
sudo systemctl status cloudflared
sudo systemctl restart cloudflared
To confirm the problem yourself, run this from any machine:
curl -sv https://your-n8n-host/api/v1/workflows
Cloudflare's error page shows the sub-code. If curl returns 530 too, the problem is on your side and nothing in Administrate.dev will fix it.
Once the tunnel is back, click Sync Now on the instance.
"Authentication failed: 401" or "403"
Your n8n API key is wrong or has been revoked.
- Log into n8n
- Go to Settings → API
- Create a new key
- Paste it into the instance in Administrate.dev and save
A 403 can also mean an access proxy (Cloudflare Access, an IP allowlist, or a WAF rule) is blocking us before n8n sees the request. If the key is definitely current, check those rules next.
"Server error: 500"
n8n itself returned an error. We include n8n's own message after the status code, which usually points at the cause. Check the n8n container logs:
docker logs n8n --tail 100
We do not retry a 500, because it almost always means a real problem that a retry will repeat.
"Server error: 502", "503", or "504"
A proxy in front of n8n could not get a response. We retry these three automatically, up to three times with a growing delay, so a brief restart will not show up as a failure.
If you still see the error, n8n was down for more than about 15 seconds. Common causes:
- The n8n container is restarting or has crashed
- The server ran out of memory
- n8n is too slow to answer because of a very large execution history
"Connection error"
We could not open a connection at all. Check that:
- The base URL is correct, including
https:// - The hostname resolves in public DNS
- The server is reachable from the internet, not only from your office network
Instances on a private network or behind a VPN cannot be reached. n8n must be publicly reachable, or exposed through a tunnel.
"Rate limit exceeded"
n8n returned a 429. Something is sending too many requests to that instance. This is rare with our sync schedule, so check whether another tool is also polling the n8n API.
"The URL does not appear to be an n8n instance"
We got an HTML page where JSON should be. Almost always the base URL is wrong.
- Use the root URL, such as
https://n8n.yourcompany.com - Do not include
/api/v1or a workflow path - Do not point at a reverse proxy landing page
After 10 Failures
Sync pauses for an instance after 10 consecutive failures. Fix the underlying problem, then click Sync Now to resume.