Update button stuck? Start here
On some older versions, clicking Update starts a counter without actually sending the update command. Reboot and Shutdown may also appear to do nothing. This bug was fixed in v2.8.1, and the fix is included in newer releases.
This is a one-time workaround. Update to the latest version using either option below, then refresh the page. After that, you can use the normal Update button for future updates—you won't need to repeat this workaround.
A counter appearing briefly is normal. These instructions address the specific bug where the counter keeps running but the update never starts; they aren't a fix for every slow or failed update. If an update is already running, let it finish rather than starting another one.
Start the update from your browser
Open your BirdNET-Pi, then paste this into your browser's address bar:
http://birdnetpi.local/views.php?submit=update_birdnet.sh
If your BirdNET-Pi has a different address, change only the http://birdnetpi.local
part. Leave everything after it unchanged. You can find your station's address
in the address bar when you open BirdNET-Pi; keep https:// if that is what it uses.
Opening this address starts the update immediately, without a confirmation
dialog. Sign in with your station's administrator credentials if prompted.
Alternatively, use SSH or Web Terminal
Run these commands as your station's normal user:
cd ~/BirdNET-Pi
./scripts/update_birdnet.sh
Both methods run the existing updater, which normally switches to the main
branch and restarts services. Save any custom source-code edits first: the
updater resets local tracked-file changes. Detection and recording services
will be briefly interrupted. A current backup is always recommended.
Once it finishes, refresh the page (hard-refresh if necessary). You can use the
normal Update button for future updates. Do not use Clear or Restore to fix
this problem; no manual database changes are needed.
If neither method works, save the update output and report what happened in a
GitHub issue.
Remove passwords, tokens, and other private information before sharing logs.
See the latest release
for current release notes. This is recovery guidance for older installations,
not a request to reinstall or erase your station.
Update button stuck? Start here
On some older versions, clicking Update starts a counter without actually sending the update command. Reboot and Shutdown may also appear to do nothing. This bug was fixed in v2.8.1, and the fix is included in newer releases.
This is a one-time workaround. Update to the latest version using either option below, then refresh the page. After that, you can use the normal Update button for future updates—you won't need to repeat this workaround.
A counter appearing briefly is normal. These instructions address the specific bug where the counter keeps running but the update never starts; they aren't a fix for every slow or failed update. If an update is already running, let it finish rather than starting another one.
Start the update from your browser
Open your BirdNET-Pi, then paste this into your browser's address bar:
If your BirdNET-Pi has a different address, change only the
http://birdnetpi.localpart. Leave everything after it unchanged. You can find your station's address
in the address bar when you open BirdNET-Pi; keep
https://if that is what it uses.Opening this address starts the update immediately, without a confirmation
dialog. Sign in with your station's administrator credentials if prompted.
Alternatively, use SSH or Web Terminal
Run these commands as your station's normal user:
Both methods run the existing updater, which normally switches to the
mainbranch and restarts services. Save any custom source-code edits first: the
updater resets local tracked-file changes. Detection and recording services
will be briefly interrupted. A current backup is always recommended.
Once it finishes, refresh the page (hard-refresh if necessary). You can use the
normal Update button for future updates. Do not use Clear or Restore to fix
this problem; no manual database changes are needed.
If neither method works, save the update output and report what happened in a
GitHub issue.
Remove passwords, tokens, and other private information before sharing logs.
See the latest release
for current release notes. This is recovery guidance for older installations,
not a request to reinstall or erase your station.