Step-by-Step Fix
-
Confirm the scope
- Try a different browser/device and a different network.
- If only one environment fails, the cause is usually local.
-
Refresh your session
- Sign out completely, then sign back in.
- Clear cache/cookies for the service domain.
- Try an incognito/private window with no extensions.
-
Check permissions and plan status
- Verify you’re using the correct account/workspace.
- Confirm your subscription/plan is active and assigned correctly.
-
Rule out network filtering
- Disable VPN/proxy temporarily.
- Pause ad blockers / privacy tools that may block requests.
- If you’re on a corporate network, test via hotspot.
-
Check service incidents
- Review the product status page or recent incident reports.
- If the service is degraded, wait and retry.
-
Collect evidence and escalate
- Save screenshots + exact error text + timestamps.
- Include environment details and repro steps in a support ticket.
Common Root Causes
- Expired/invalid session tokens
- Plan or permission mismatch
- Browser extensions interfering with requests
- Network blocks (VPN/proxy/firewall/DNS)
- Temporary outages
Prevention Tips
- Keep a clean browser profile for critical workflows
- Don’t stack multiple privacy extensions that rewrite requests
- Document workspace/team permissions and billing owners
- Export important settings regularly (when supported)
Why This Happens
Midjourney’s Discord bot looks up your account by matching your Discord user ID to a linked Midjourney subscription. When the bot fails to recognize your account, it is almost always because the Discord account you are currently using in the server is not the same one linked to your Midjourney subscription. This mismatch happens most often when someone has multiple Discord accounts (a personal and a work account) and purchased Midjourney with one but is trying to use it from the other. It can also happen when your subscription was purchased through the Midjourney web interface using Google login rather than Discord login — in that case, the Discord user ID may not be linked to the Midjourney account at all.
Common Mistakes to Avoid
- Logging into Discord with a different account than the one linked to your Midjourney subscription — this is the single most common cause; verify in Discord’s bottom-left corner which account you are currently using
- Purchasing a subscription via Google login and expecting Discord to recognize it automatically — Google-linked Midjourney accounts must be separately connected to Discord through midjourney.com/account settings
- Using Midjourney in a third-party Discord server where the bot is not properly configured — the official Midjourney server at discord.gg/midjourney always works; bot commands in third-party servers depend on that server’s bot setup
- Forgetting to join the Midjourney Discord server — you must be a member of the Midjourney Discord server to use the bot; simply having the bot in another server is not sufficient for all features
- Not running
/infoto confirm your subscription linkage — running/infoimmediately tells you whether the bot recognizes your account and shows your plan tier
FAQ
Q: How do I link my Midjourney account to my Discord account?
If you signed up for Midjourney using Google login rather than Discord, you need to connect the two accounts manually. Go to midjourney.com/account and sign in with your Google account. In your account settings, look for a Discord connection option and authorize it. Once connected, the Midjourney Discord bot will recognize your Discord account and show your subscription when you run /info in the Discord server.
Q: Why does the Midjourney bot say "not a member" even though I have an active subscription?
The "not a member" message from the Midjourney bot means the Discord account you are currently signed into is not linked to any active Midjourney subscription. This is separate from whether a subscription exists — it means the bot cannot find a subscription connected to your current Discord user ID. Confirm which Discord account your subscription is tied to by signing into midjourney.com using Discord login and checking which account it logs you in as.
Q: Can two Discord accounts share one Midjourney subscription?
No. Each Midjourney subscription is tied to a single Discord user ID (or Midjourney account). You cannot use one subscription from two different Discord accounts simultaneously. If multiple people need access, each person needs their own Midjourney subscription. Midjourney offers operator-API access for teams, but standard subscriptions are single-user.
Q: The Midjourney bot recognized my account before but now says it doesn’t — what changed?
Sudden account recognition failures that worked before are usually caused by a Discord token expiry or session issue. Sign out of Discord completely — close the app, not just the window — then sign back in on all devices. The bot uses your Discord session token to look up your account, and stale tokens cause lookup failures. If the problem persists after a fresh Discord login, check status.midjourney.com for any ongoing bot issues that may be affecting account lookups globally.
Q: Does using Midjourney in a private Discord server instead of the official server cause recognition issues?
Using Midjourney in a third-party or private Discord server can cause issues if that server’s bot configuration is incorrect. The Midjourney bot must be properly added to the server with the correct permissions. If the bot is responding but not recognizing your account, try the same /info command in the official Midjourney server at discord.gg/midjourney. If it works there, the problem is with the third-party server’s bot setup, not your account.
Related Issues
- Midjourney Discord Authorization Login Issues
- Midjourney Plan Not Reflecting After Upgrade
- Midjourney Login Page
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.
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.