Step-by-Step Fix
1. Rule out cookies / cached sessions
- Open an incognito/private window and try logging in
- Clear cookies/site data for Midjourney
- Close all tabs, reopen, and try again
2. Disable blockers (very common for auth redirects)
- Temporarily disable ad blockers / privacy extensions
- Turn off VPN/proxy for the login attempt
- Allow pop-ups and cross-site cookies for the login domain (only if you trust it)
3. If you use Google/Apple login: re-authorize cleanly
- Start the login flow from the provider button again (don't mix email + OAuth)
- If the provider opens a blank/blocked page, try another browser
- Check you didn't switch accounts in the provider (wrong Google/Apple account)
4. Network sanity check
- Try mobile hotspot (rules out corporate/ISP filtering)
- If CAPTCHA never loads, your IP or extensions may be flagged — switch network
5. Confirm you are using the right login method
Midjourney accounts are tied to a specific OAuth provider. If you originally registered with Google, you must always log in with Google. Attempting to log in with your email address directly, or with Discord, will create or access a different account. On the login page, use the same provider button you used when you first signed up.
6. Force a full session reset
If you're stuck in a redirect loop:
- Clear all cookies for midjourney.com and auth.midjourney.com in your browser settings
- Restart the browser completely (not just close the tab)
- Navigate directly to midjourney.com/login and attempt fresh authentication
- If the loop persists, try a different browser entirely (switch from Chrome to Firefox or Safari)
7. Check if your account has been flagged or suspended
If you complete the login flow successfully but land on an error or empty dashboard, your account may be under review. Check the email address associated with your Midjourney account for any notification from the Midjourney trust and safety team. Suspended accounts typically receive an email explaining the reason and next steps.
Why This Happens
Midjourney's web login uses OAuth redirects through providers like Google, Discord, and Apple. This multi-step flow depends on cookies being written and read correctly across the midjourney.com domain and the OAuth provider's domain. Browser extensions that block cross-site cookies or tracking scripts, privacy-focused browsers with aggressive default settings, and VPNs that route traffic through flagged exit nodes all interfere with this flow. The login page appears to load but the final authentication step — where the OAuth token is exchanged for a Midjourney session — fails silently, causing the redirect loop. Session cookie expiry is another common cause: an older session token becomes invalid but the browser keeps sending it, blocking a fresh login from completing.
Common Mistakes to Avoid
- Mixing login methods — Using Google to log in when you registered via Discord creates a second, separate account. Both accounts are valid but empty in each other's context. Always identify which OAuth provider you used when you first subscribed.
- Not testing in incognito first — Incognito mode disables all extensions and starts with no cookies, making it the fastest way to isolate whether the problem is browser configuration. Skip this step and you may spend an hour troubleshooting the wrong thing.
- Entering an email address when you signed up via OAuth — If you registered with "Continue with Google," there is no email/password login option for your account. Entering your Google email in the email field will not work — you must click the Google button.
- Assuming the problem is account-level when it is browser-level — Most Midjourney login issues resolve immediately when tested in a different browser or with extensions disabled. Check the browser environment before contacting support.
- Using a VPN during login — VPN exit nodes, especially shared ones used by many users, are often flagged by authentication systems. Disable your VPN for the login step and re-enable it afterward if needed.
Related Issues
Additional FAQ
Q: What is the fastest way to diagnose a login problem? The fastest diagnostic is to open an incognito or private browser window and attempt to sign in there. Incognito windows run without extensions and use fresh cookies, which isolates the two most common causes: a browser extension interfering with authentication, or corrupted session cookies. If login works in incognito, the issue is your main browser profile. If it still fails, the problem is your network, your account, or a platform-side incident.
Q: Why does clearing browser cache fix login issues? Your browser caches session tokens and authentication cookies that prove you are logged in. If these become corrupted or expire mid-session, the browser may present an invalid token on each page load, causing the server to reject the session and redirect you to login. Clearing site-specific data forces the browser to request fresh tokens on the next login, which resolves most session-related loops without affecting your other browser data.
Q: Should I try a different browser if login keeps failing? Yes — testing in a second browser is one of the most useful steps. Different browsers use different cookie stores, extension ecosystems, and caching mechanisms. If login works in Browser B but fails in Browser A, the issue is specific to Browser A's state (likely extensions or corrupted profile data), not your account. You can continue working in Browser B while you troubleshoot the original browser.
Related Articles
- Midjourney not generating images
- Midjourney login not working
- Midjourney payment failed
- Midjourney rate limit exceeded
Additional FAQ
Q: What is the fastest way to diagnose a login problem? The fastest diagnostic is to open an incognito or private browser window and attempt to sign in there. Incognito windows run without extensions and use fresh cookies, which isolates the two most common causes: a browser extension interfering with authentication, or corrupted session cookies. If login works in incognito, the issue is your main browser profile. If it still fails, the problem is your network, your account, or a platform-side incident.
Q: Why does clearing browser cache fix login issues? Your browser caches session tokens and authentication cookies that prove you are logged in. If these become corrupted or expire mid-session, the browser may present an invalid token on each page load, causing the server to reject the session and redirect you to login. Clearing site-specific data forces the browser to request fresh tokens on the next login, which resolves most session-related loops without affecting your other browser data.
Related Articles
- Midjourney not generating images
- Midjourney login not working
- Midjourney payment failed
- Midjourney rate limit exceeded
Additional FAQ
Q: What is the fastest way to diagnose a login problem? The fastest diagnostic is to open an incognito or private browser window and attempt to sign in there. Incognito windows run without extensions and use fresh cookies, which isolates the two most common causes: a browser extension interfering with authentication, or corrupted session cookies. If login works in incognito, the issue is your main browser profile. If it still fails, the problem is your network, your account, or a platform-side incident.
Related Articles
- Midjourney not generating images
- Midjourney login not working
- Midjourney payment failed
- Midjourney rate limit exceeded
Additional FAQ
Q: What is the fastest way to diagnose a login problem? The fastest diagnostic is to open an incognito or private browser window and attempt to sign in there. Incognito windows run without extensions and use fresh cookies, which isolates the two most common causes: a browser extension interfering with authentication, or corrupted session cookies. If login works in incognito, the issue is your main browser profile. If it still fails, the problem is your network, your account, or a platform-side incident.