When using Midjourney, the easiest things to get stuck on are Discord authorization, command errors, and not being able to find your images. Below I break these high-frequency issues down clearly—follow the checks and you can usually get back to generating normally.
Discord authorization failure: can’t enter the channel or can’t use commands
If Midjourney suddenly stops responding in Discord, first confirm you’re logged into the same Discord account: many people get auto-switched by the browser and end up in an “empty channel.” In Discord, open your DM with the Midjourney Bot and try entering /info once—if it replies, your permissions are generally fine.
If there’s still no response, go to Discord’s “Authorized Apps” and revoke any Midjourney-related authorization, then re-bind Discord via the Midjourney website. After that, return to the original channel and enter /imagine again to test. This usually fixes cases where you can see the channel but can’t use Midjourney.
Commands send but you get a parameter error: most commonly caused by dirty characters from copy/paste
Midjourney is very sensitive to parameter formatting. The most common issue is that when copying from note-taking apps, you accidentally bring in full-width spaces, Chinese em dashes, or invisible line breaks. It’s best to retype the key parameters in plain text first, then add options like --ar and --stylize back one by one to pinpoint which part is causing Midjourney to error.
Also, use a half-width space between a parameter and its value, e.g., “--ar 16:9”. If you put multiple colons on the same line or have unmatched quotation marks, Midjourney may treat the whole segment as abnormal input and report a formatting issue.


