Step-by-Step Fix
1. Check if the Bot is in Your Server
First, confirm whether the Midjourney bot is actually in your server or has been removed.
- Go to your Discord server
- Open Server Settings → Integrations → Bots and Apps
- Look for Midjourney Bot in the list
- Bot appears in the list → It is in your server but may have permission issues (go to step 2)
- Bot is not in the list → The bot has been removed and needs to be re-invited (go to step 4)
2. Check Channel-Level Permissions
If the bot is in the server but not appearing or responding in a specific channel:
- Right-click the channel → Edit Channel
- Click Permissions
- Scroll to find the Midjourney Bot role (or the role assigned to the bot)
- Ensure these are set to green (allowed):
- View Channel / Read Messages
- Send Messages
- Attach Files
- Embed Links
- Use Application Commands
- Save changes and test the /imagine command in that channel
3. Check Server-Level Role Permissions
Channel permissions can be overridden by server-level role settings:
- Go to Server Settings → Roles
- Find the role assigned to Midjourney Bot
- Under Text Channel Permissions, verify the same permissions listed in step 2 are enabled
- If a channel-level permission says "Denied" (red X), it overrides server permissions — fix it at the channel level
4. Re-invite the Midjourney Bot
If the bot was removed from your server:
- Log in to midjourney.com with the same account you use for Midjourney
- Navigate to the Discord bot invite page or check docs.midjourney.com for the current official invite link
- Select your server from the dropdown (you must be a server administrator)
- Review and approve the requested permissions
- The bot should reappear in your server's member list within seconds
5. Check the Audit Log
If the bot disappeared unexpectedly, check who removed it:
- Go to Server Settings → Audit Log
- Look for any entries about "Midjourney Bot" being removed or having roles changed
- If an admin accidentally removed it, re-invite as described in step 4
6. Verify Midjourney Status
Visit status.midjourney.com to check for any Discord integration outages. If Midjourney is having issues connecting to Discord's infrastructure, the bot may appear offline or unresponsive even in servers where it has correct permissions.
Why This Happens
Discord bots require explicit server membership and channel permissions. Unlike human users, bots cannot join servers on their own — they must be invited by a server administrator. If a bot is in a server but does not have channel-level permission to read and send messages, it appears invisible in that channel. Accidental permission changes during server reorganization are a frequent cause of bots "disappearing" from channels they were previously active in.
Common Mistakes to Avoid
- Inviting the bot to the wrong server — Make sure you select the correct server during the bot invite flow.
- Not granting Use Application Commands — Without this permission, /imagine and other slash commands will not work even if the bot is visible in the channel.
- Forgetting that channel permissions override server permissions — Even if the bot has broad server-level access, a channel-level "Deny" on a specific permission will block it in that channel.
- Not checking the audit log after unexpected disappearance — Another admin may have accidentally removed the bot or changed its role.
- Assuming a server restart will fix permission issues — Discord permissions are applied in real time; restarting Discord is not necessary and will not change permission configurations.
Related Issues
- Midjourney not allowed to use command in Discord
- Midjourney interaction failed / bot not responding
- Midjourney Discord authorization issues
For more Midjourney help, visit the Midjourney tools hub.
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.