Troubleshooting

🇩🇪 Deutsche Version

Troubleshooting

Forgot the admin password

The Admin password field in the Unraid template only applies on the very first start. To reset it, delete the stored password and restart the container – the template value then applies again.

1. In the Unraid template (Docker → TasmoBackup-py → Edit) enter the new password under Admin password and click Apply.
2. In the Unraid console (or via SSH):

   docker exec -u 99:100 TasmoBackup-py python -c "import sqlite3; c=sqlite3.connect('/data/tasmobackup.db'); c.execute(\"DELETE FROM settings WHERE key='admin_password_hash'\"); c.commit()"
   docker restart TasmoBackup-py

3. Log in with Admin user / Admin password from the template.

Outside Unraid, replace TasmoBackup-py with your container name and 99:100 with your PUID:PGID.

"backup failed (offline?)"

• Is the device reachable? Click the IP in the device list – does the Tasmota/WLED page open in your browser?
• New IP? A Scan subnet recognises the device by its MAC address and stores the new IP.
• Web password? If the device has a password, it must have been entered when adding it – or be set as default in TB_TASMOTA_USER / TB_TASMOTA_PASSWORD.

Change a device's credentials under Edit → Credentials. After saving, the app queries the device with them right away and tells you whether it answers.

Device is online, but the backup fails

Event log message: device did not deliver a config. The device answers but won't hand out its configuration. Common causes:

• Restricted web mode: Tasmota only hands out its configuration in admin mode (WebServer 2, the default). A device running WebServer 1 sends its start page instead of the file – the app detects this and does not store it as a backup. Fix: enter WebServer 2 in the Tasmota console.
• Wrong credentials (see above).

Update stuck on "minimal"

If a device shows a version with (minimal) after an update and stays there, Tasmota did not complete the second stage. The app retries once on its own. If that doesn't help:

• Click Update again.
• Check the OTA URL in the Tasmota interface under Firmware Upgrade.
• If free flash is very tight, a smaller firmware variant or an update via USB helps.

Permission problems with the data folder

On start the container changes every file in the data folder to PUID:PGID. If you copied files in by hand, a restart of the container is enough.

Key lost or changed

Without the original key (.secret_key in the data folder or TB_SECRET_KEY):

• you have to log in again,
• stored device and MQTT passwords can no longer be read – enter them again.

The backups themselves are not affected.

Moving to another server or a new container

1. Stop the old container.
2. Copy the complete data folder into the new appdata folder – including .secret_key. If the old installation used TB_SECRET_KEY, write its value as a single line into .secret_key in the new folder (or set TB_SECRET_KEY again).
3. Start the new container with this appdata folder. It fixes file ownership on its own.

Backup paths are stored container-internally in the database (/data/backups/…), so they keep working in the new folder.

Where are the logs?

In Unraid under Docker → TasmoBackup-py → Logs (or docker logs TasmoBackup-py). Scheduled runs, backups, updates and errors are listed there.

Something else?

Please open an issue on GitHub – with the version (shown at the top of the interface next to "TasmoBackup" and in the first log line), a description and the relevant log lines.