Sign-in loop: why it happens and how to escape

You keep getting sent back to the login page — here's why

You enter your email and password, hit Sign in, and then… you're back at the login page again. No error message. No dashboard. Just an endless loop that makes it feel like your account doesn't exist. This is one of the most frustrating authentication issues in any web app, and it almost always has a fixable root cause.

A sign-in loop on Coachful — where the platform keeps redirecting you to the login screen after you authenticate — is typically caused by a broken session cookie, an aggressive browser setting, a misconfigured custom domain, or a caching conflict. This guide walks you through every known cause and its fix, step by step.

TL;DR — Quick fixes to try first

• Clear your browser cookies and cache for coachful.co and your custom domain, then try again.
• Disable browser extensions (especially ad blockers, privacy shields, and password managers) and retry in an incognito/private window.
• Check that third-party cookies are enabled — Coachful's session tokens require them on certain browsers.
• Try a different browser or device to isolate whether it's a client-side issue.
• If you're on a custom domain, verify your DNS and SSL setup in your Coachful workspace settings.

What actually causes a sign-in loop?

Authentication in a modern SaaS platform like Coachful relies on a short-lived session token stored in a browser cookie. When you sign in successfully, the server issues that token, your browser stores it, and every subsequent request proves your identity. A loop happens when that handshake breaks at one of several points.

1. Blocked or expired session cookies

The most common culprit. If your browser is configured to block cookies — either globally or for third-party origins — the session token never gets stored. The server authenticates you, tries to redirect you to your dashboard, and when it checks for the token on the next request, it finds nothing. It sends you back to the login page. Repeat.

Privacy-focused browsers like Brave and Firefox with Enhanced Tracking Protection can silently block these cookies even when you think they're enabled. Safari's Intelligent Tracking Prevention (ITP) is a particularly common offender on iOS and macOS.

2. Corrupted or stale cache

A cached version of the Coachful login page or a stale service worker can intercept the redirect chain and send it back to /sign-in instead of /dashboard. This is more common after a platform update, since your browser may still be serving old JavaScript or routing logic.

3. Browser extensions interfering with requests

Ad blockers, VPNs, cookie managers, and some password managers modify HTTP headers or strip cookies mid-request. If an extension removes the Set-Cookie header before it's processed, the session is never established. The login form submits successfully, but the session token evaporates.

4. Custom domain or SSL misconfiguration

Coaches who use a custom domain (e.g., coaching.yourbrand.com) with Coachful can hit a loop if the domain's SSL certificate hasn't fully propagated or if there's a mismatch between the domain the cookie is issued on and the domain the browser is reading it from. This is a same-site cookie issue — the session token set on yourslug.coachful.co won't be sent automatically when the request originates from coaching.yourbrand.com.

5. Multiple accounts or role conflicts

If you have both a coach account and a client (member) account with the same email address — or if you belong to multiple Coachful organizations — the platform can sometimes struggle to determine which session context to load. This is rare but reproducible, especially if you've been bouncing between workspaces in the same browser tab.

6. Clock skew on your device

Session tokens carry an expiry timestamp. If your device clock is significantly off — even by a few minutes — the server may reject the token as already expired the moment it's issued. The result looks exactly like a sign-in loop. Check that your system clock is set to sync automatically.

Already using Coachful? If you're a coach experiencing this on your own branded workspace, sign in to your Coachful dashboard and check Settings → Custom Domain to confirm your domain and SSL status. Your clients won't be able to log in until the domain resolves cleanly.

Step-by-step fix: browser-side issues

Work through these in order. Most sign-in loops are resolved before you reach step 5.

1. Open an incognito or private window. In Chrome: Ctrl+Shift+N (Windows) or Cmd+Shift+N (Mac). In Firefox: Ctrl+Shift+P. Navigate to app.coachful.co/sign-in and try logging in. If it works here, the problem is in your main browser profile (cookies, cache, or extensions).
2. Clear cookies and site data specifically for Coachful. In Chrome, go to Settings → Privacy and security → Cookies and other site data → See all site data and permissions. Search for coachful.co, then delete all entries. Also delete entries for your custom domain if you use one. Repeat the sign-in attempt.
3. Hard-reload to bust the cache. On the Coachful sign-in page, press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac) to force a cache-bypassing reload. This clears stale service worker scripts.
4. Disable all browser extensions. Go to your browser's extension settings and turn everything off — especially ad blockers (uBlock Origin, AdGuard), privacy tools (Privacy Badger, Ghostery), and VPN extensions. Try signing in again. If it works, re-enable extensions one at a time to identify the offender. Whitelist coachful.co in that extension's settings.
5. Allow third-party cookies for Coachful. In Chrome: Settings → Privacy and security → Third-party cookies — add [*.]coachful.co to the "Sites that can always use cookies" list. In Safari: Preferences → Privacy — uncheck "Prevent cross-site tracking" temporarily. In Firefox: Settings → Privacy & Security → Enhanced Tracking Protection — set to "Standard" instead of "Strict" or add an exception for coachful.co.
6. Try a completely different browser. If Chrome is looping, try Firefox, Edge, or Safari. This eliminates every browser-specific variable in one step.
7. Restart your router or switch networks. Some corporate networks and ISPs intercept HTTPS responses in ways that corrupt cookies. Try signing in on mobile data (with Wi-Fi disabled) to rule this out.

Step-by-step fix: custom domain issues (coaches only)

If you're a coach and your clients are hitting the loop on your branded domain, the fix is in your workspace settings, not their browsers.

1. Log in to your Coachful coach dashboard via the direct URL: https://yourslug.coachful.co/sign-in (bypassing your custom domain). This confirms your credentials are valid.
2. Go to Settings → Website → Custom Domain.
3. Check the SSL status. It should show a green Active badge. If it shows Pending or Error, your certificate hasn't issued yet — DNS propagation can take up to 48 hours. Wait and check again.
4. Verify your DNS records match exactly what Coachful instructs. A CNAME record pointing to proxy.coachful.co is required. Any extra A records or conflicting CNAMEs will cause certificate errors that manifest as a sign-in loop.
5. Once SSL shows Active, test the sign-in flow from an incognito window using your custom domain. Share the fix with affected clients by directing them to clear cookies for your custom domain as described above.

Step-by-step fix: mobile app sign-in loop

If you're using the Coachful mobile app (available via app.coachful.co/mobile or installed natively on iOS/Android), the sign-in loop behaves slightly differently because the app uses a WebView shell.

1. Force-close the app completely (swipe it away from your recent apps), then reopen it.
2. On iOS: go to Settings → Safari → Advanced → Website Data, search for coachful, and delete all entries. On Android: go to Settings → Apps → Coachful → Storage → Clear Cache.
3. Uninstall and reinstall the app. This clears the entire WebView cookie jar and any stale service worker registrations.
4. If you're on iOS and using Safari-based WebKit, ensure Settings → Safari → Privacy & Security → Prevent Cross-Site Tracking is turned off (or check if the app has its own setting for this).
5. Still looping? Try signing in via a mobile browser (app.coachful.co/sign-in) rather than the installed app to confirm your credentials work, then reinstall.

Pro tips for coaches: prevent your clients from hitting this

If you manage a coaching practice on Coachful, proactively reducing sign-in friction for your clients means fewer support tickets and higher engagement with your programs.

Tip: Add a short "Getting started" note to your onboarding program week — something like "Use Chrome or Firefox for the best experience, and make sure cookies are enabled for [yourdomain]." A 12-week program with a strong Week 1 onboarding task dramatically reduces login-related drop-off.

• Use your Coachful subdomain as the fallback login URL. Even if you have a custom domain, share your yourslug.coachful.co/sign-in link in your welcome email so clients always have a working login path if your custom domain has DNS hiccups.
• Configure your welcome email (under Settings → Emails → Client welcome) to include browser setup tips and the direct sign-in link.
• Test sign-in from an incognito window yourself every time you change your custom domain settings. It takes 30 seconds and catches issues before your clients do.
• Ask Michelle, the built-in AI assistant in your coach dashboard, to walk you through domain or SSL troubleshooting. Just open the Michelle panel and type "my custom domain has a sign-in issue" — she can check your domain status and surface the right settings screen instantly.

Troubleshooting: common mistakes and edge cases

Mistake 1: Clearing history instead of cookies

Clearing your browsing history does nothing for a sign-in loop. You need to clear cookies and site data specifically. In most browsers, these are separate options in the "Clear browsing data" dialog. Make sure "Cookies and other site data" is checked, not just "Browsing history".

Mistake 2: Using the wrong sign-in URL

Coachful has two distinct sign-in entry points: app.coachful.co/sign-in (for coaches and clients accessing the main app) and your custom branded domain. Bookmarking a stale URL — e.g., an old redirect from a marketing email — can cause a loop if the path no longer exists. Always use https://app.coachful.co/sign-in as the canonical login URL unless you're intentionally using a custom domain.

Mistake 3: Assuming it's a password problem

A sign-in loop is not the same as a wrong password error. If you had the wrong password, you'd see an explicit error message on the login page. A loop means authentication succeeded but session establishment failed. Resetting your password will not fix this — but clearing cookies will.

Mistake 4: Logging in on multiple tabs simultaneously

Opening Coachful in two or more tabs and trying to sign in on both at once can create a race condition where each tab overwrites the other's session cookie. Close all tabs, then sign in from a single fresh tab.

Mistake 5: Device clock out of sync

If your laptop or phone clock is more than 5 minutes off from UTC, JWT session tokens can fail validation the moment they're issued. On Windows: Settings → Time & Language → Date & Time → Sync now. On Mac: System Settings → General → Date & Time → Set time automatically. On iOS/Android: Settings → General → Date & Time → Set Automatically.

Mistake 6: Corporate firewall or proxy stripping cookies

Some enterprise networks run SSL inspection proxies that intercept HTTPS traffic and strip or modify Set-Cookie headers. If you only experience the loop on your work network, this is almost certainly the cause. Ask your IT team to whitelist *.coachful.co, or use your mobile hotspot to confirm.

Still stuck? Contact support

If you've worked through every step above and you're still caught in a sign-in loop, the issue may be account-specific — for example, a corrupted session record on the server side, a role conflict across organizations, or an edge case in your custom domain configuration. Coachful's support team can investigate directly.

When you reach out, include the following so support can act fast:

• The exact URL you're trying to sign in at (your subdomain or custom domain)
• Your browser name and version
• Whether the loop happens in incognito mode as well
• A screenshot or screen recording of the loop (even a 10-second screen record helps enormously)
• Whether you are a coach, an admin, or a client/member

You can reach support via the chat widget on coachful.co or by emailing support from inside your dashboard.

Ready to get back into your Coachful workspace?

A sign-in loop is almost always a client-side issue — cookies, cache, extensions, or a device clock — and it's fully fixable in a few minutes with the steps above. Start with the incognito test. If that works, clear your cookies for coachful.co. If you're a coach on a custom domain, check your SSL status in Settings → Website → Custom Domain. Nine times out of ten, you'll be back in your dashboard before you finish reading this sentence.

Once you're in, explore the rest of the Coachful help center for guides on setting up your programs, configuring your booking availability, and getting your clients onboarded smoothly. Or, if you're new here, start your free trial and see why thousands of coaches run their entire practice on Coachful.