A GoHighLevel page shows "404 not found", an integration fails with a 400 error, or the whole app won't load. Before you rebuild anything, find out which of three problems you have: GoHighLevel is down, something in your setup is wrong, or an integration is sending bad data. This guide shows how to tell them apart and how to fix each one.
1. Is GoHighLevel down, or is it just you?
Check this first, because during an outage nothing you change will help.
- Check the official status page:
status.gohighlevel.comlists current incidents and the parts affected (workflows, phone, email, funnels, payments). - Check an independent monitor such as StatusGator or IsDown, which also collect user reports and outage history.
- Test from somewhere else: a private/incognito window, another browser, your phone on mobile data, or the mobile app. If it works there, the problem is your browser, cache, extensions or network.
- Try another sub-account. If only one account is affected, it's usually that account's settings, domain or integrations, not a platform outage.
If GoHighLevel is down: don't edit or rebuild workflows, don't re-send campaigns, and note the time it started. Most incidents are resolved within minutes to a few hours. Afterwards, check what was missed (see section 6).
2. GoHighLevel 404 error on a funnel or website page
A 404 on your own domain almost always means the domain, the page path or the publishing setting is wrong. Go through these in order:
- Domain connected to the wrong funnel or website. In Settings → Domains, check the domain shows as verified and is linked to the right funnel or website.
- The page path changed. Renaming a step or page changes its URL, so old links, ads and QR codes now point nowhere. Restore the old path or add a redirect.
- The page or step isn't published, or was deleted or moved to another funnel.
- www vs root domain. If people sometimes see a 404, they may be using the other version (www or not). Connect both, with one redirecting to the other.
- No default page. If the bare domain (no path) shows a 404, set a default landing page for that domain.
- DNS records are wrong or conflicting. HighLevel's help docs give these values:
| Record | Host | Value |
|---|---|---|
| Root domain (A) | @ | 162.159.140.166 |
| Subdomain (CNAME) | e.g. www or offers | sites.ludicrous.cloud |
Add the record at the DNS provider your domain actually uses, delete any other A or CNAME records for the same host, and allow up to 24 hours for DNS to update. If your DNS is on Cloudflare and the domain still won't connect, try setting the record to "DNS only" (grey cloud), because the proxy can interfere with verification and SSL. Always check HighLevel's current domain article before changing records, as values can change.
SSL still pending? HighLevel issues the certificate automatically once the domain connects. It usually takes minutes; if it's stuck for hours, the DNS record is usually wrong or proxied.
Finally, set a custom 404 page. Create a simple page ("This page has moved" with links to your main pages and a contact form), then pick it as the default 404 page in the domain's settings. Visitors who hit a broken link become leads instead of leaving.
3. 404 errors inside the GoHighLevel app
- An old link or bookmark to a contact, workflow or opportunity that was deleted or merged.
- The wrong sub-account: the link belongs to a different location than the one you're logged into.
- Permissions: your user role can't see that feature or record, which can look like "not found".
- A feature that was moved or renamed in an update. Search for it from the main menu rather than using an old URL.
4. 400 errors in GoHighLevel integrations and the API
A 400 Bad Request means GoHighLevel received the request but didn't accept the data. It's nearly always the integration's fault, not an outage. Common causes when you use the API, webhooks, Zapier, Make or n8n:
- Missing or wrong
Versionheader on API calls. Each endpoint's docs show the value it expects. - Wrong or missing
locationId, or an ID copied from a different sub-account. - Badly formatted fields: phone numbers not in international format (+15555550123), dates in the wrong format, or text sent to a number field.
- Custom field keys or IDs that don't exist in that sub-account, often after cloning a snapshot.
- Required fields missing, such as a calendar or pipeline stage ID when creating an appointment or opportunity.
Other status codes you'll see:
| Code | Meaning | What to do |
|---|---|---|
| 401 | Token missing, expired or wrong | Refresh the OAuth token or check the Private Integration token |
| 403 | Token lacks the scope for this action | Add the scope, then create a new token |
| 404 | The record or endpoint doesn't exist | Check the ID, sub-account and URL path |
| 422 | Data is valid JSON but breaks a rule | Read the error message, which usually names the field |
| 429 | Rate limit hit | Slow down and retry with backoff |
| 500–504, 520–524 | Server or network problem | Retry later and check the status page |
The response body usually says which field is wrong, so log it. More detail is in the GoHighLevel API guide.
5. 500, 502 and 520 errors (server-side)
Errors in the 500s mean something failed on GoHighLevel's side or between you and it. They're usually temporary. Wait a few minutes, retry, and check the status page. If one specific page or action always fails while everything else works, report it to GoHighLevel support with the details below.
6. After an outage: what to check
- Workflow execution logs: find contacts that stopped mid-workflow or skipped a step, and re-enrol only those that need it, so nobody gets duplicate messages.
- Missed calls and messages during the outage window, and reply to them manually.
- Forms and bookings: compare submissions with what reached the CRM.
- Integrations: check Zapier, Make or n8n run history for failed runs, and replay them.
If workflows misbehave even when GoHighLevel is up, see why your GoHighLevel workflow isn't working.
7. GoHighLevel stability: how to protect your business
Every platform has incidents. These habits keep an outage or a broken link from costing you leads:
- Monitor your key pages (main funnel, booking page) with a free uptime monitor, so you hear about a 404 before customers do.
- Set a custom 404 page on every domain.
- Keep a record of your DNS settings and who has access to the domain registrar.
- Build integrations with retries and logging, so a failed call is repeated instead of lost.
- Have a manual fallback: a shared inbox or phone list your team can use if the CRM is down for an hour.
8. Contacting GoHighLevel support
Support can fix things much faster when you include:
- The sub-account (location) ID and the exact URL or feature
- The time it happened, with your time zone
- Screenshots or a short screen recording, plus the full error message
- For API errors: the endpoint, the request (without your token) and the response body
- What you've already tried
Need it fixed for you?
I'm Arslan Mumtaz, a software engineer who fixes GoHighLevel domains, broken funnels, failing integrations and workflows that stopped working, for businesses and agencies in the US, UK, Europe and Australia. Fixes are $20/hr, or start with a $97 audit. For ongoing help, see the GoHighLevel VA plans.