# JetBackup shows a 500 error during a restore
Source: https://docs.webgee.com/en/backups/jetbackup-jetbackup-ui-showing-500-error



JetBackup returns a **500** or fatal error while a restore is running. Applies to
shared and reseller hosting.

**This is expected during a full account restore, and it resolves itself.**
Nothing is broken and the restore is not failing.

## Why it happens [#why-it-happens]

A full account restore **terminates the account first**, then recreates it from
the backup. Your cPanel session belongs to the account that has just been
terminated, so it is no longer valid — and the interface errors rather than
signing you out cleanly.

## What to do [#what-to-do]

1. **Leave the restore running.** Do not retry it, and do not start another.
2. Wait for it to finish. Larger accounts take longer.
3. Sign out of cPanel, then sign back in.

The new session belongs to the restored account, and JetBackup behaves normally.

<Callout type="warn">
  Do not start a second restore because the first appeared to fail. Two restores
  running against the same account at once is a genuinely bad state, and this
  error looks like failure when it is not.
</Callout>

## How to tell it is actually finished [#how-to-tell-it-is-actually-finished]

Sign back in and open **JetBackup 5 → Queue**. The job shows as complete. If the
queue is empty and your files are present, it finished.

## If the error persists after signing back in [#if-the-error-persists-after-signing-back-in]

That is not this problem. Open a ticket with your
[support PIN](/en/account-billing/support-pin), saying which backup date you
restored from and when.

## Related [#related]

* [Restore from a backup](/en/backups/jetbackup-how-to-restore-your-account-files-or-databases)
* [Restore a home directory or specific files](/en/backups/how-to-restore-a-home-directory-or-specific-files-using-jetbackup-5)