Since version `1.29.0` of Vaultwarden, you can activate Mobile Client push notifications to [automatically sync](https://bitwarden.com/help/vault-sync/#automatic-sync) your personal vault between the mobile app, the web extension and the web vault without the need to sync manually.

### Enable Mobile Client push notification

1. Go to [https://bitwarden.com/host/](https://bitwarden.com/host/) insert your email address and you'll get an INSTALLATION ID and KEY.  

2. Add the following settings to your `docker-compose.yml` (and make sure you insert the correct ID and the KEY from the previous step):
```yaml
    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
```yaml
      - PUSH_RELAY_URI=https://api.bitwarden.eu
      - PUSH_IDENTITY_URI=https://identity.bitwarden.eu
```

3. Recreate your container, e.g. with

```bash 
docker compose up -d vaultwarden
```

4. Log out and log back in to your Bitwarden clients so they can retrieve the push configuration from the server.

> [!WARNING]
> If you have already connected your Bitwarden app before [v1.30.2](https://github.com/dani-garcia/vaultwarden/releases/tag/1.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](https://contributing.bitwarden.com/architecture/deep-dives/push-notifications/mobile/#self-hosted-implementation).

> [!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](https://mobileapp.bitwarden.com/fdroid/), 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.

5. 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.

### Switching from US to EU servers (or vice versa)
 
> [!WARNING]
> Make sure you use the latest version [![GitHub Release](https://img.shields.io/github/release/dani-garcia/vaultwarden.svg)](https://github.com/dani-garcia/vaultwarden/releases/latest) before doing that change.

To switch from one data region to the other you'll have to:
1. deauthorize all sessions and also clear the app data on the mobile app
2. 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.
```sql
UPDATE devices SET push_uuid = NULL;
```

This _should_ trigger your push devices to be re-registered on your next login with the device.