Step-by-Step Fix
1. Check Midjourney's Status Page
Before spending time on local troubleshooting, visit status.midjourney.com to check for active incidents. If Midjourney is experiencing an outage, no local fix will help — wait for the incident to resolve.
2. Try Incognito / Private Mode First
Open an incognito or private browsing window and navigate to midjourney.com. This disables most extensions and bypasses cached data.
- If login works in incognito → the problem is a browser extension or cached data (continue to step 4)
- If login still fails in incognito → the problem is your network, account, or Midjourney's servers (skip to step 5)
3. Clear Cookies and Site Data
Stale or corrupted cookies are the single most common cause of login failures.
- Open your browser settings
- Navigate to Privacy → Clear browsing data
- Select Cookies and other site data and Cached images and files
- Set time range to All time
- Click Clear data
- Also clear cookies specifically for discord.com if you log in with Discord
- Reopen your browser and try logging in again
4. Disable Browser Extensions
Ad blockers, privacy tools, and script blockers frequently interfere with the OAuth redirect that Midjourney uses for login.
- In Chrome, go to chrome://extensions
- Toggle off all extensions — especially ad blockers and privacy tools
- Reload midjourney.com and try logging in
- If login works, re-enable extensions one at a time to identify the one causing the problem
Common culprits: uBlock Origin, Privacy Badger, Ghostery, DuckDuckGo Privacy Essentials.
5. Switch to a Different Browser or Network
If incognito mode did not resolve the issue, test with a completely different browser (for example, if you normally use Chrome, try Firefox or Edge). Also try switching networks — use a mobile hotspot instead of your home or office Wi-Fi.
If login works on a different network, your original network (firewall, VPN, or ISP) is blocking the OAuth redirect or Midjourney's authentication endpoints.
6. Re-authorize Discord or Google Login
If you sign in to Midjourney via Discord or Google, the connection can expire or become invalid.
For Discord:
- Log in to discord.com directly and confirm your Discord session is active
- Go to User Settings → Authorized Apps in Discord
- Find Midjourney and click Deauthorize
- Return to midjourney.com and go through the login flow again — this creates a fresh authorization
For Google:
- Go to myaccount.google.com → Security → Third-party apps with account access
- Find Midjourney and remove access
- Return to midjourney.com and log in again with Google, completing the OAuth prompt fully
7. Allow Pop-ups for Midjourney
Some browsers block the OAuth pop-up window that Midjourney uses for authorization.
- In Chrome: go to Settings → Privacy → Site settings → Pop-ups and redirects
- Add midjourney.com and discord.com to the Allow list
- Try logging in again
8. Contact Midjourney Support
If none of the above steps work, go to docs.midjourney.com and open a support ticket. Include:
- The exact error message you see
- Your browser and OS version
- Whether the issue occurs in incognito mode
- Whether the issue occurs on a different network
Why This Happens
Midjourney uses OAuth (through Discord or Google) to handle authentication, which involves multiple redirect steps between servers. Any interruption in that chain — from a browser extension blocking a redirect, a corrupted cookie holding an old session token, or a network policy preventing the OAuth callback — causes the login to fail. The fix is almost always to remove the old session data and start the authentication flow fresh.
Common Mistakes to Avoid
- Refreshing the login page repeatedly — Refreshing does not clear the corrupted session data. You must clear cookies and restart the browser to fix a login loop.
- Leaving VPN active during login — VPNs frequently break OAuth redirects because the IP changes mid-flow. Disable VPN before starting the login process.
- Not checking Midjourney's status first — If there is an active outage on Midjourney's or Discord's side, no amount of local troubleshooting will fix the login.
- Skipping the extension disable step — Ad blockers blocking the OAuth redirect is one of the top causes of Midjourney login failures, but many users overlook it.
- Using the same broken browser without trying incognito — Incognito mode is the fastest way to determine if the issue is local (extensions/cache) or systemic.
Related Issues
- Midjourney login with Discord issues
- Midjourney bot missing from Discord channel
- Midjourney account not recognized in Discord
- Midjourney login not working
Q: Can I log in to Midjourney if my Discord account is temporarily disabled? If your Discord account has been temporarily disabled by Discord (for example, following a terms of service issue on Discord's end), you will not be able to use Discord to log in to Midjourney during that period. As an alternative, try logging in with Google at midjourney.com — if you also have a Google account linked to Midjourney (or if you have never used Discord to register), Google login will still work. If you only registered via Discord and that account is disabled, contact Midjourney support at docs.midjourney.com explaining the situation.
Q: How do I know if Midjourney is down versus my login specifically being broken? The clearest diagnostic is to check status.midjourney.com for any active incidents. If the status page shows all systems operational, the issue is likely specific to your account or browser. A second check: ask a friend to try logging in or check social media (Twitter/X or Reddit's r/midjourney) to see if others are reporting the same problem at the same time. If only you are affected, it is a local or account issue; if many users are affected, it is a platform incident.
Q: Does Midjourney automatically log you out after a period of inactivity? Midjourney sessions on the web interface typically stay active for up to 30 days without requiring a new login. However, clearing your browser cookies, using incognito mode (which does not persist cookies), or switching browsers will end your session and require a new login. The mobile app session can also be cleared if you use iOS's "Offload App" feature or Android's "Clear Data" option. If you are repeatedly being logged out without taking any of those actions, it may indicate a session token conflict that clearing cookies and logging in fresh will resolve.
Q: What should I do if I get a 'Something went wrong' error during login? A generic "Something went wrong" error during the Midjourney login flow is almost always a transient error in the OAuth handshake. Try the login again from the beginning — do not refresh, instead navigate back to midjourney.com and start the sign-in process fresh. If it fails consistently, clear your cookies for midjourney.com and discord.com, open an incognito window, and try again. If the error message contains a specific code or more detail, include that exact text in a support ticket at docs.midjourney.com.
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.