This article consolidates answers to the most common Midjourney issues involving login, permissions, and image generation. If you get stuck, go through the checklist in order. Many Midjourney “errors” aren’t actually that it’s “broken,” but are caused by using the wrong account, the wrong channel, or a congested queue.
Can’t log in to Midjourney: endless loading spinner or authorization failure
Midjourney’s web app usually logs in via Discord authorization. First, make sure your browser isn’t blocking third-party cookies, scripts, or pop-ups. If Midjourney keeps getting stuck on the authorization page, try again in an incognito window, or temporarily disable ad-blocking extensions.
If you have multiple Discord accounts, it’s easy to “log into the wrong one” during Midjourney authorization. The most reliable approach is to log out of all accounts in Discord Web, keep only the one you want to use, then return to Midjourney and authorize again.
Permission denied: can’t see the bot or can’t use /imagine
To use Midjourney in Discord, you must operate in a server and channel where you have permission; in a new DM or an unsupported channel, you may not see the commands. If you see messages like “You don’t have permission to use this bot,” it usually means application commands are disabled in that channel—ask an admin to enable the Midjourney bot’s permissions.
Another very common cause is that the subscribed account doesn’t match the current Discord account: you purchased Midjourney on account A, but you’re sending commands with account B. Go to Midjourney’s account page to verify the linked Discord, then return to the channel with the same account and test /imagine.


