GoHighLevel Not Working? 8 Fixes for Common Problems (2026)

GoHighLevel not working is one of the most searched phrases among agencies and operators on the platform. Before spending an hour inside the settings, the first question to answer is whether the issue is your configuration or a GoHighLevel platform event. This guide covers the 8 most common causes and how to resolve each one.

Is GoHighLevel down right now?

The fastest diagnostic step is to rule out a platform-wide outage before troubleshooting locally.

How to check the official GoHighLevel status page

GoHighLevel maintains a public status dashboard at status.gohighlevel.com. The page shows real-time status for every service layer: Contacts, Conversations, Payments, Automation, Sites, Marketing, and AI features. Incidents are logged with timestamps, impact descriptions, and resolution updates.

As of July 26, 2026, all GoHighLevel services are operational. The most recent platform incidents were three issues resolved on July 23, 2026: a Voice AI call processing disruption, course page latency and loading timeouts, and sub-account switching problems. GoHighLevel resolved all three the same day they were reported, and the status page reflected the resolution in real time.

Bookmarking status.gohighlevel.com is worth doing. When a reported problem matches an open incident on the status page, waiting for the resolution is faster than any local fix.

How to check for sub-account-specific issues vs platform-wide outages

If the status page shows all systems operational but a feature is still failing, the issue is sub-account-specific. The most reliable way to confirm this is to log into a different sub-account or ask a team member on a different GHL account to test the same feature. If it works in the other account, the problem is in your sub-account configuration.

Sub-account failures are almost always one of the following: a misconfigured SMTP or Mailgun connection, an unverified domain, a workflow in draft state, or a missing A2P 10DLC registration for SMS. Each has a direct fix covered in the sections below.

Why is GoHighLevel not sending emails?

Email delivery failures are the most commonly reported non-outage issue on GoHighLevel. The two root causes are almost always a broken SMTP or Mailgun connection, or missing DNS records on the sending domain.

The SMTP and Mailgun configuration checklist

GoHighLevel sends email through one of three routes: LC Email (the built-in Mailgun-based system), a connected Mailgun account, or a custom SMTP provider. In all three cases, the connection credentials need to be current.

To check your email integration, go to Settings > Email Services inside the sub-account. Verify the following:

• The API key for your Mailgun account is entered correctly and has not expired.
• The sending domain in Mailgun matches the domain you are sending from inside GHL.
• If using a custom SMTP, the host, port, username, and password are all current.

A common failure point is an expired Mailgun API key. Mailgun does not notify you when a key expires; emails simply stop sending and log as failed in the conversation history. Regenerating the key in Mailgun and updating it in GHL's Email Services settings resolves this immediately.

For a full email delivery diagnostic walkthrough, see the GoHighLevel email deliverability guide.

SPF, DKIM, and DMARC -- what is missing from your DNS records

If the Mailgun connection looks correct but emails are bouncing or landing in spam, the problem is almost always the DNS records on your sending domain.

GoHighLevel email requires three DNS records to authenticate outbound mail:

SPF (Sender Policy Framework): A TXT record that tells receiving mail servers which IPs are authorized to send on behalf of your domain. Mailgun provides the SPF record value in your Mailgun domain settings. If your domain does not have an SPF record that includes Mailgun, emails will fail authentication at many providers.

DKIM (DomainKeys Identified Mail): A cryptographic signature attached to outbound emails, verified via a TXT record in your DNS. Mailgun generates a DKIM key pair and provides the public key record to add to your DNS. Without DKIM, email authentication fails at most enterprise mail servers.

DMARC (Domain-based Message Authentication, Reporting, and Conformance): A policy record that tells receiving servers what to do with messages that fail SPF or DKIM. A basic DMARC record with p=none reports without rejecting; p=quarantine or p=reject will block emails that fail the upstream checks.

Check all three records in your DNS provider's dashboard. Mailgun shows the expected vs. actual record status under Domains in the Mailgun console. Most delivery failures trace back to a missing or outdated SPF record after a domain migration or a DNS provider change.

Why are GoHighLevel workflows not triggering?

Workflow failures are the second most common problem after email. In almost every case, the cause is one of three things.

Step 1: confirm the workflow is published

The most frequent cause of a workflow not running is that it is in Draft status. A workflow saved in draft mode does not execute, even if the trigger condition is fully met.

Go to Automation > Workflows in the sub-account. The status indicator next to each workflow shows Published or Draft. If the workflow is in Draft, click into it, review the trigger and actions, then toggle it to Published. Contacts who meet the trigger condition from that point forward will enter the workflow.

Step 2: confirm the trigger condition is being met

If the workflow is published but contacts are not entering it, the trigger condition is likely not being met. Common mismatches include:

• A tag-based trigger where the tag name has a typo or capitalization difference from the tag actually being applied.
• A form submission trigger where the form specified in the workflow is not the one the contact is submitting.
• A pipeline stage trigger where the stage move is happening in a different pipeline than the one specified.

To verify, manually check one contact who should have entered the workflow. Review their contact record and confirm that the event the trigger watches actually occurred. If it did not, the upstream action (the tagging, form submission, or stage move) is what needs fixing.

For a detailed look at GoHighLevel's workflow trigger library and how to configure each one, see the GoHighLevel automation workflows guide.

Step 3: check the contact history log

If the trigger condition is being met but the workflow is still not running, check the contact's workflow execution history. Inside any contact record, the Activity tab shows every workflow the contact has been enrolled in, including failed enrollment attempts and the reason for the failure.

Common failure reasons logged there include: "Contact already in workflow" (GoHighLevel does not re-enroll a contact already active in the same workflow unless re-entry is enabled), "Contact does not meet filter conditions" (if the workflow has additional filter conditions beyond the trigger), and "Workflow rate limit" at high volume.

Why is GoHighLevel login not working?

Login failures on GoHighLevel follow one of three patterns.

Incorrect sub-account URL. GoHighLevel users have separate login points: the main agency login and sub-account portals. If a team member or client is trying to access a sub-account using the agency login URL, they will see an error or land in a view they do not have access to. Confirm the correct login URL for the specific account.

Browser cache or session conflict. A stale browser session can prevent login from completing. Clear the browser cache, close all GoHighLevel tabs, and log in fresh. Opening an incognito or private browsing window isolates the session from cached credentials and usually resolves the issue immediately.

Two-factor authentication codes not arriving. If GoHighLevel is sending a 2FA code by email and the code is not arriving, check the spam folder first. If it is consistently missing, the issue is usually the email integration tied to the account, not a GHL platform failure.

Why is the GoHighLevel calendar not booking appointments?

Calendar booking failures most often trace back to availability settings and timezone configuration.

No availability slots published. A GoHighLevel calendar will not accept bookings if the availability schedule has no open slots. Go to Calendars in the sub-account, open the affected calendar, and review the Availability tab. Confirm that open time windows are set for the booking period the contact is trying to reach.

Timezone mismatch. If a contact in one timezone books with a user whose calendar is set to a different timezone, the available slots on the booking page can appear empty or display incorrect times. The calendar timezone setting is under Calendar Settings > General. Set it explicitly to the timezone where meetings are occurring, not to a default like UTC.

Calendar not published or embed code outdated. A calendar in draft state or one with an outdated embed code will show an error or blank page to visitors. Confirm the calendar is published, then regenerate the embed code from the calendar settings and replace the version on your site or funnel.

For a full setup and troubleshooting walkthrough, see the GoHighLevel calendar booking guide.

Why are GoHighLevel SMS messages not sending?

SMS failures in GoHighLevel are common, and the root cause is usually one of two things: an incomplete A2P 10DLC registration or a phone number configuration error.

A2P 10DLC registration not approved. In the United States, all business SMS traffic must be registered under the A2P 10DLC framework before carriers will deliver messages. If a GHL sub-account's A2P registration is pending, rejected, or was never submitted, outbound SMS messages will fail silently or be filtered by carriers. Check the registration status under Settings > Phone Numbers > A2P Registration. If the status is anything other than Approved, the registration process needs to be completed or resubmitted.

The GoHighLevel A2P registration guide covers the full registration process and how to resolve the most common rejection reasons.

Phone number not assigned to a message service. Even with an approved A2P registration, outbound SMS can fail if the Twilio phone number is not assigned to the correct messaging service. Verify in the sub-account's Phone Settings that the number is active and the messaging service is configured.

Why is the GoHighLevel chat widget not responding?

Chat widget failures are almost always a code placement or domain configuration issue.

Widget code not on the page. The chat widget requires a JavaScript snippet embedded in the site's <head> or before the closing </body> tag. If the widget was added via a tag manager, confirm the tag is firing on that specific page. If added manually, confirm the snippet is in the page source.

Domain mismatch in widget settings. Some GoHighLevel chat configurations restrict the widget to specific domains. If the widget is being tested on a staging domain or a different URL than the one configured, it will not load. Check the widget's domain settings in Sites > Chat Widget and add any domains where the widget should appear.

How do you contact GoHighLevel support?

If the steps above do not resolve the issue, GoHighLevel offers several support channels.

Live chat, ticketing, and community forum

GoHighLevel offers 24/7 live chat support accessible from the Help icon inside the platform. The chat connects to the support team and can escalate to a ticket if the issue requires deeper investigation.

For non-urgent issues, a support ticket can be submitted via the same Help menu. The ticketing system tracks the issue through resolution and sends email updates. Agencies on the Agency Pro (previously SaaS Pro) plan and those with a Premium Support add-on at $500 per month receive priority routing and faster response times.

The GoHighLevel community at community.gohighlevel.com is an active peer forum where many common configuration issues have been documented by experienced users. Searching the specific error message or feature name often surfaces a thread with a working fix.

If the issue is a feature gap rather than a bug, the ideas board at ideas.gohighlevel.com lets users upvote existing requests or submit new ones. The product team reviews high-vote items for roadmap planning.

For a broader look at how GoHighLevel performs across all its features, see the GoHighLevel review.