Troubleshooting

Fixes for the most common problems. The exact error is always shown on the backup's detail page and in the alert email.

A server shows "Offline"

1. Check that the server is switched on and has internet access.
2. On the server, run sudo systemctl status flashbackup-agent. If it isn't running: sudo systemctl restart flashbackup-agent.
3. Look at the log: sudo journalctl -u flashbackup-agent -n 100.
4. If the log says "removed in the FlashBackup dashboard" or "Credentials rejected", create a new install command in the dashboard and run it again. Your encryption key is kept.
5. Make sure outbound HTTPS (port 443) is allowed by your firewall or cloud security group.

"Google Drive is not connected" / "access was revoked"

Go to Settings → Google Drive and click Connect or Reconnect. This happens if someone removed FlashBackup from the Google account, changed the Google password, or disconnected it.

"Your Google Drive is full"

Free up space in Google Drive, buy more Google storage, or lower Keep backups for in Settings. Then click Back up now.

"MySQL found but FlashBackup could not sign in"

MySQL's root user has a password. Create a backup user and add it to the agent config. See Database credentials.

"mysqldump exited with 2: Access denied … PROCESS / LOCK TABLES / EVENT"

The backup user is missing a permission. Run the GRANT command from Database credentials.

"The sqlite3 tool is needed"

Install it on the server: sudo apt install sqlite3 (Ubuntu/Debian) or sudo dnf install sqlite (RHEL/Amazon Linux).

A database is missing from the list

• Click Look for databases again on the server page and wait a minute.
• Run sudo flashbackup-agent scan on the server to see what the agent finds and why.
• SQLite files outside /home, /root, /var/www, /srv or /opt must be added in the config. See Database credentials.

"Lost contact with the server during the backup"

The server restarted, lost internet, or the agent was stopped while a backup was running. The next backup usually works. If it keeps happening on a very large database, check the server's memory and network in the log.

"The uploaded file could not be verified"

The upload finished but Google Drive reported a different size. This is rare and usually a temporary Google problem. Run the backup again.

Backups are slow

Backups run at low priority on purpose, so your website stays fast. Large databases (many GB) can take a while, mostly limited by upload speed. Choose a backup time when the server is quiet.

Still stuck?

Contact support at support@flashbackup.com.ng, and include the backup number (e.g. "Backup #1234") and the last lines of sudo journalctl -u flashbackup-agent -n 100.