Locked out, and your site is down

Your site is down and you cannot log in to fix it. You have no phone number to call and no chat window that answers. This guide covers what actually gets accounts back, and what to do while you wait.

Why prompting will not fix this

Your AI tool can write code. It cannot reset a password on a server it does not control. It cannot call your host's support team. It cannot prove you own the account. Locked-out access is not a code problem, so no prompt fixes it. Typing the same request into ChatGPT or Claude again will not help. This needs a human on the host's side to check your identity and unlock the account.

The real recovery routes

Try these in order. Most hosts solve lockouts through one of these three paths.

1. The host's community forum. Many hosts have staff who watch their public forum and respond faster there than through a ticket queue. Post your account email, your domain name, and the exact time the lockout started. Do not post your password.
2. A formal account recovery request. Every major host has a page for this, usually under "account recovery" or "regain access." Fill it out fully. Vague requests go to the back of the line.
3. The email on file. Check the inbox tied to the account, including spam. Hosts often send a security alert or a locked-account notice with a recovery link before you even notice the site is down.

What to include so you get a fast answer

Support staff move quicker when they do not have to ask follow-up questions. Include all of this in your first message:

• Your account email and username
• Your domain name exactly as it appears in your dashboard
• The date and time you first got locked out, with your timezone
• What error or message you see when you try to log in
• Whether the site is currently live, down, or showing an error page
• Any account or invoice ID from a past billing email

If you have two-factor authentication set up and lost access to it, say so directly. That changes which recovery path staff will use.

A prompt to use while you wait

You can still use your AI tool to prepare, as long as you keep it away from anything destructive. Use this prompt to get a clean support message ready, not to touch your live site:

The prevention: a copy that lives somewhere else

This kind of lockout is painful because your project only exists in one place: inside an account you cannot get into. If a copy of your code sits somewhere the host does not control, a lockout stops being a disaster and becomes an inconvenience. You wait for support, and meanwhile your project still exists.

Two ways to set that up:

• Keep your code in a version control system (a tool that saves every change you make, like a history you can rewind) such as GitHub, separate from your hosting account.
• Use a service that saves versions of your project automatically, outside the host, so one locked account never means one lost project.

Plyo saves every version automatically and lets you publish somewhere your host cannot lock you out of.

Either way, the fix is the same: never let your only copy live inside the account that just locked you out.