Host-your-account Debug Checklist

Midjourney HYA Debug Checklist

1.
When there is a problem with your Midjourney HYA service, please use this checklist to troubleshoot before contacting us.
2.
Most problems are related to using an invalid Discord Authorization Token. Thus, you can directly skip to step #5 to check whether your Discord Auth Token is valid.

1. Is your Midjourney set to use HYA or Pay-as-you-go(PAYG)?

Go to Workspace, and check whether your Midjourney API service is set to PAYG or HYA mode (see the toggle).

2. Are you using the correct API Key?

Go to https://piapi.ai/workspace/key and compare the first three numbers of the API Key shown on the dashboard to the API Key that you are using to make API calls. If they don't match that means you don't have the correct key. In that case, just reset the API Key and use the new one.

3. Is your account inactive right now?

Go to https://piapi.ai/workspace/midjourney and check for the active period setting of your Midjourney account(s).

Note: The time zone on the Dashboard is London UK time (UTC), please convert to your local time zone as needed.

4. Is your MJ account working normally?

Please log in to your Discord account with your valid Midjourney Subscription and type "/settings" to your Midjourney Bot.

Has your account been blocked?

If your task submitted was under fast mode, does your account still have fast hour left?

If your task submitted was under relax mode, does your account have relax hour left?
For example, the Basic Plan (the $10 Plan) does not have relaxed hour.

5. Is the Discord Token used to connect your Midjourney account valid?

First, you should record down the Discord Authorization Token that was used to connect your Midjourney account to the HYA seat when you were binding them; because if you don't record it then, you won't be able to see it after the binding process. In this case, you can only delete the account and rebind the Midjourney account.

Then, you could use a Google Chrome plug-in such as https://chrome.google.com/webstore/detail/discord-token-login/ealjoeebhfijfimofmecjcjcigmadcai to try to log into your Discord account with your recorded Discord Authorization Token, to verify whether the Token is valid.
If you are using the recommended plug-in mentioned above:

After installing the plug-in in Google Chrome, please use a new incognito window that has not been logged onto any discord account for this test.

Please make sure you are on https://discord.com/ before you try to use the plug-in to login to Discord.

After logging in to Discord, please make sure that you do not log out of the discord account as the discord auth token will change after logging out of Discord! Just use an incognito mode (such as Google Chrome Incognito) to login; and after you are done, just close the browser, you don't need to log out of Discord.

6. Can you successfully message the Midjourney bot to submit a job?

Please submit a task to Midjourney in Discord first. Is it working? If so, continue to the next step.

If you are submitting jobs to the Midjourney bot in Direct Message, then just fill out info below without needing to worry about the Channel ID and the Guild ID in the "advanced settings".

If you are submitting jobs to a Midjourney bot in a channel instead of Direct Message, then you would need to bind the appropriate Channel ID and Guild ID along with your Discord Authorization Token.

7. Last measures

If you followed all the steps above and made sure everything is fine (including the Midjourney account), and yet when you submit a job through API it still says:

"no active bot", please

change its [load weight] to something else and change it back to its original setting; and

change its [active period] to something random, and change it back to the desired, correct setting.

"Subscription expired", please

go to the corresponding Discord account and type '/info' prompt to the Midjourney Bot;

And try submitting another task through the API again. If it still does not work, please contact PiAPI in Discord.

Luma HYA Debug Checklist

My Luma account token gets reset very frequently, almost one reset per token, what can I do?

Potential cause 1 : your account was signed in somewhere else. If so, you could try changing the Google-related password to prevent this from happening.

Potential cause 2 : You've had the subscription associated with this account for a long time and Luma might have flagged this account for automation.

Host-your-account (HYA) | Debug Checklist

Midjourney HYA Debug Checklist#

1. Is your Midjourney set to use HYA or Pay-as-you-go(PAYG)?#

2. Are you using the correct API Key?#

3. Is your account inactive right now?#

4. Is your MJ account working normally?#

5. Is the Discord Token used to connect your Midjourney account valid?#

6. Can you successfully message the Midjourney bot to submit a job?#

7. Last measures#

Luma HYA Debug Checklist#