Skip to main content

Fix Kajabi pages that won’t load or look broken

Find out why a page shows a 404 error, a login page, or broken formatting, and fix it in page settings, the browser, or the internet connection.

When a Kajabi page won’t load, loads with broken formatting, or shows a 404 error or a login page, the cause is usually one of four things: a page setting, the browser, security software on the device, or the internet connection.

Check the causes in order, starting with the quickest. First, check the page’s status, Member Visibility, and URL in Kajabi. Then check the browser, any antivirus or web protection software, and finally the internet connection.

If a page loads but one button or element does nothing when clicked, the cause is usually a Kajabi setting, not the browser. To find the setting, see Fix a page element that does nothing when clicked.


Common causes of pages that don't load properly

A page that loads with missing styles, stacked images, or unformatted text, usually means part of the page was blocked before it reached the browser. Web protection or antivirus software, a browser problem, or the internet connection can all cause this.
​

Fix pages that won't load in the Kajabi mobile app

If pages or content won't load in the Kajabi mobile app on iOS or Android, try these steps in order:

  1. Force-stop the app, then reopen it.

  2. Check the App Store or Google Play Store for an app update, and install it if one is available.

  3. Uninstall the app, then reinstall it.

If content still won't load after you reinstall the app, contact Kajabi Support.

Check the page status, visibility, and URL

Before you change anything in the browser, check the page's own settings in Kajabi. A Draft page, a members-only page, or a URL typo looks like a loading problem but has nothing to do with the browser or connection.

Confirm the page is published

A page set to Draft isn't available to visitors. In Kajabi, the Draft status reads Only you can see this page, so a Draft page can load for you while visitors get a 404 error. To check a page's status:

  1. From the Dashboard, click Website, then Website Pages or Landing Pages.

  2. Find the page in the list and check its status.

  3. If the status is Draft, change it to Published. The page is available to visitors at its URL.

Tip: To see a page the way visitors see it, open its URL in a private or incognito browser window, where you aren't signed in to Kajabi.

Check Member Visibility if visitors see a login page

If visitors see a login page instead of a Website Page, check the page's Member Visibility setting. When it's on, Only members can view this page, so visitors who aren't signed in are sent to log in first. Turn Member Visibility off if the page should be public.

Check the page URL

To rule out a URL problem, confirm the URL you're visiting or sharing matches the page's URL in Kajabi exactly, including capitalization. Kajabi only opens a page on an exact match, so /Free-Guide and /free-guide are different addresses.

If a Landing Page and a Website Page share the same URL, the address opens the Landing Page. Kajabi marks these pages Duplicate URL in the page list. To show the Website Page instead, give it a different URL.

If the page's status, Member Visibility, and URL are all correct and the page still won't load, the cause is likely the browser. Try another browser and clear the cache.

Try another browser and clear the cache

To rule out a browser problem, open the same page in a different browser, such as Chrome, Safari, Firefox, or Edge.

If the page loads normally there, clear the cache and cookies in the original browser, then reload the page:

For keyboard shortcuts and steps to flush the DNS cache as well, see Flush DNS and clear browser cache.

Check the browser console for blocked content

If the page still won't load in any browser, security software or a browser extension may be blocking parts of it. The browser console lists blocked content as red errors, so checking it tells you whether that's the cause.

Open the console in Chrome, Edge, or Firefox

To open the console in Chrome, Edge, or Firefox:

  1. Open the page that won't load properly, and right-click anywhere on it.

  2. Select Inspect.

  3. Click the Console tab.

  4. Look for red errors such as net::ERR_NETWORK_ACCESS_DENIED, net::ERR_BLOCKED_BY_CLIENT, or other errors that mention blocked or denied network access.

Chrome DevTools Console tab showing red errors for content blocked from loading


For more on the console, see Google's guide to the Chrome DevTools Console.

Open the console in Safari

Safari hides its developer tools until you turn them on. To open the console in Safari:

  1. Turn on the Develop menu by following Apple's guide to the Develop menu in Safari.

  2. With the page open, click the Develop menu, then select Show JavaScript Console.

  3. Look for red errors that mention blocked or denied network access.


Allow Kajabi in antivirus or web protection software

If the console shows blocked-content errors, antivirus or web protection software is likely stopping the page from loading. To fix it, allow Kajabi in that software, then reload the page.

McAfee is known to block Kajabi pages. If McAfee is installed, see McAfee's guide to turning Net Guard on or off.

For other antivirus software, ad blockers, or browser extensions, check that product's support site for how to allow a website.

Fix a page element that does nothing when clicked

If a page loads but a specific element doesn't work, the cause is usually a setting in Kajabi rather than the browser. Check the setting that controls that element:

  • Course modules: A module set to Drip (drop icon) or Scheduled (calendar icon) in the Course outline won't open until its release date, even for customers who own the Offer.

  • Checkout: Some payment methods need third-party cookies. If checkout doesn't respond, check that the browser allows third-party cookies.

  • Coaching bookings: If a booking page shows no available times, confirm availability is set for the Kajabi Scheduler. Click Manage availability in the Coaching program's scheduling settings.


Check custom code on the page

If the browser console shows errors from the site's own domain rather than blocked-content errors, custom code added to the page may be the cause. For example:

  • Custom CSS with incorrect values, such as negative margins, can place one element on top of another and block clicks on it.

  • Content saved in the visual editor may revert if a custom HTML block conflicts with the editor's code view.

To test custom code, temporarily remove or hide the custom code blocks on the page, then reload it. If the problem goes away, the custom code is the cause.

Rule out an internet connection or ISP routing issue

If the page fails in every browser and nothing is blocked on the device, the problem may be how the internet connection reaches Kajabi's servers. That's controlled by the internet service provider (ISP), not by Kajabi or the device.

A strong sign of an ISP issue is a page that loads on mobile data but stays slow or unavailable on a home or office connection. Run these tests in order:

  1. Tether to mobile data. Connect the computer to a phone's mobile hotspot and reload the page. If it loads normally, the ISP's connection to Kajabi's servers is the issue.

  2. Switch to a public DNS resolver. The ISP's Domain Name System (DNS) resolver may be routing incorrectly. Change the DNS setting to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google), flush the DNS cache, and reload the page. For steps, see Flush DNS and clear browser cache. If load times improve, the ISP's DNS was the cause.

  3. Turn off IPv6 temporarily. Some ISPs have routing problems between their IPv6 network and Kajabi's content delivery network (CDN). Turn off IPv6 in the network adapter or router settings, then reload the page. If the page loads with IPv6 off, contact the ISP so they can fix the routing.

  4. Compare the custom domain with the Kajabi subdomain. On the same connection, load the site at its Kajabi subdomain (for example, yoursite.mykajabi.com). If the subdomain loads quickly but the custom domain is slow, the problem is how the domain resolves. See Troubleshoot custom domain issues. If both are slow, the problem is ISP routing.

Note: If these tests point to the ISP, Kajabi's servers are working normally and the fix has to come from the ISP. When you contact them, say which test made a difference (the DNS change, turning off IPv6, or the mobile hotspot) to help them find the problem faster.

Contact Kajabi Support

If the page still won't load after these steps, contact Kajabi Support. To get help faster, include:

  • The full URL of the page

  • The browser and device you used

  • A screenshot of any red errors in the console

  • The steps in this article you've already tried

Did this answer your question?