Failed update and rolling back
A failing update changes nothing, or returns to the previous version on its own; to undo the database too, restore the pre-update backup.
Updated on Oct 3, 2026, 6:39 p.m.
On this page
In short. Agora protects every update in three ways: a backup before anything else, migrations applied only if that backup is complete, and an automatic return to the previous version if the new one does not start within 3 minutes.
Read the message #
Administration → Agora shows the step and the cause, after "Failed:":
| Message | What happened | What to do |
|---|---|---|
| database backup impossible (…) | Nothing was downloaded or changed | Fix the cause (disk space, backup folder rights, database reachable), then try again |
| database backup impossible — no usable pg_dump… | Machine that is not Linux x86-64, or non-executable folders | Set AGORA_PG_BIN to a folder containing pg_dump 17 |
| … the PostgreSQL server (version N) is newer than pg_dump 17 | External database on PostgreSQL 18 or later | AGORA_PG_BIN to a pg_dump of the same version |
| database backup stopped before the end | The dump was discarded, nothing was changed | Try again; if it keeps happening, check disk space |
| downloaded file corrupted / incomplete | Download altered or cut | Try again; if it persists, open a ticket |
| download refused (HTTP …) / the update server returned an error (HTTP …) | Nothing was changed | Try again in a few minutes |
| invalid download address / file received larger than the announced size | Nothing was changed | Try again; if it keeps happening, contact support |
| downloaded version not found on disk / unreadable update request | Nothing was switched | Retry the update |
| this version requires version X first | An intermediate step is needed | Install version X first, then retry |
| the update could not complete (code …) | Unforeseen error | Try again; if it keeps happening, give this code to support |
| the database migrations failed | The previous version stays in service | Open a ticket; the backup is in Backups |
| the new version stopped at startup | Automatic return to the previous version | Open a ticket with the time and version |
| the new version started, but its database stayed unreachable for 3 minutes… | The database did not answer after the switch (stopped, network, credentials); automatic return to the previous version | Check that the database is running, then run the update again. On an older fallback version the screen only says "did not start": the panel console names the database |
| version refused: it is older than the most recent one this installation has already run | No going back (an old version keeps its flaws; migrations cannot be undone) | Nothing was changed; contact support |
| the proposed "fix" does not have the shape of a fix / the update server named a fix as the normal version | Inconsistent answer from the update server | Nothing was installed. Run a check again; if it persists, contact support |
| the previous update was interrupted | Restart during an update | Run the check again, then the update |
| an update is already running | Two clicks close together | Wait for it to finish |
| update server unreachable | No outbound HTTPS access | See License server unreachable |
The automatic return #
If the new version does not answer within 3 minutes, if its database stays unreachable during that time, or if it crashes right after the switch, Agora puts the previous version back in service. The screen says the new version did not start (or, when the database is the cause, that its database stayed unreachable) and it automatically returned to the previous one.
The return restores the application, not the database: if migrations were applied, the database stays in its new state.
Rolling back the database #
- Administration → Agora → Backups.
- Find the
pre-update-VERSION_DATE.sqlfile taken right before the update. - Restore, type
REMPLACER.
⚠ Everything written since the update (posts, applications…) is lost. Only do this on support's advice.
Going back to the old version on purpose #
There is no "go back" button: open a ticket on the support Discord. See Open a ticket. One exception: if support had you install a fix to test, Revert to the normal version removes it.
From the command line (Docker) #
docker logs -f agora shows the detail of each step. On a panel, it is the server console.
Was this article helpful?
Related articles
- One-click updates (and the beta channel)Administration → Agora backs up the database, downloads and verifies the new version, migrates, restarts, and rolls back on its own if it does not start.
- Backups and restoreBack up Agora's database from the admin area, download it off the server and restore it. A panel's file copy is not a backup.
- License or update server unreachableNothing shuts off right away: check the machine's outbound HTTPS access to lic1 and lic2.agorapanel.com, DNS and the firewall.
- Open a support ticketSupport works through tickets, on Agora's Discord, on the site or by email: a short form, a reply from the team, and the transcript when it closes.