Enabling Mobile Client push notification
Since version 1.29.0 of Vaultwarden, you can activate Mobile Client push notifications to automatically sync your personal vault between the mobile app, the web extension and the web vault without the need to sync manually.
-
Go to https://bitwarden.com/host/ insert your email address and you'll get an INSTALLATION ID and KEY.
-
Add the following settings to your
docker-compose.yml(and make sure you insert the correct ID and the KEY from the previous step):
environment:
- PUSH_ENABLED=true
- PUSH_INSTALLATION_ID=
- PUSH_INSTALLATION_KEY= Note
If you have requested an INSTALLATION ID and KEY for bitwarden.eu (European Union) in the previous step, you also have to set
- PUSH_RELAY_URI=https://api.bitwarden.eu
- PUSH_IDENTITY_URI=https://identity.bitwarden.eu- Recreate your container, e.g. with
docker compose up -d vaultwarden- Connect your app to your Vaultwarden instance.
Warning
If you have already connected your Bitwarden app before v1.30.2 push notifications will not work for your device (because the device token was never saved). You have to clear the app data of your mobile app (or reinstall the app) and connect your Vaultwarden account again to register the push token with Bitwarden's Azure Notification Hub.
Important
Push notifications will also only work on Bitwarden apps obtained from the official mobile stores (App Store, Google Play Store) or when using alternative clients for the Google Play Store (such as Aurora Store). Push notifications will not work using Bitwarden clients installed from F-Droid, Neo Store, or other alternative stores. Those apps have been built without support for Firebase Messaging. To ensure push notifications function properly, make sure firebaseinstallations.googleapis.com is not blocked, as it is required for the feature to work.
- Test if mobile push notifications work, for example by renaming a folder in the web vault and see if it changes after a few seconds in your mobile app.
Warning
Make sure you use the latest version 
To switch from one data region to the other you'll have to:
- deauthorize all sessions and also clear the app data on the mobile app
- repeat steps 1. to 5. from the previous section with the different data region
Alternatively to 1., you could also clear the push_uuid field of the devices table in the database, e.g.
UPDATE devices SET push_uuid = NULL;This should trigger your push devices to be re-registered on your next login with the device.