# Mobile client push not working

**URL:** https://vaultwarden.discourse.group/t/mobile-client-push-not-working/2767
**Category:** Help
**Created:** [July 9, 2023, 3:58pm UTC](https://vaultwarden.discourse.group/t/mobile-client-push-not-working/2767 "2023-07-09T15:58:20Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![kennymc.c](https://avatars.discourse-cdn.com/v4/letter/k/eb9ed0/32.png) [@kennymc.c](https://vaultwarden.discourse.group/u/kennymc.c)
#### Post date: [July 9, 2023, 3:58pm UTC](https://vaultwarden.discourse.group/t/mobile-client-push-not-working/2767/1 "2023-07-09T15:58:20Z")

</div>

I just updated the image to 1.29.0 to use the new mobile client push feature and set PUSH\_ENABLED to true and filled out PUSH\_INSTALLATION\_ID & KEY. But when I create a new item with the browser extension I can’t see in the mobile app. I still have to manually refresh/synchronize the app to see the new item.  
I’m running Vaultwarden behind a nginx proxy ([GitHub - linuxserver/docker-swag: Nginx webserver and reverse proxy with php support and a built-in Certbot (Let's Encrypt) client. It also contains fail2ban for intrusion prevention.](https://github.com/linuxserver/docker-swag)) and also not on port 443 or 80. I enabled debug logging but didn’t notice anything strange.

---

<div class="post-metadata">

### Author: ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)
#### Post date: [July 9, 2023, 4:15pm UTC](https://vaultwarden.discourse.group/t/mobile-client-push-not-working/2767/2 "2023-07-09T16:15:47Z")

</div>

I suggest to read [Using Bitwarden's push service · dani-garcia/vaultwarden · Discussion #2469 · GitHub](https://github.com/dani-garcia/vaultwarden/discussions/2469)

Maybe there is something there which can help or make it more clear on the workings.

---

<div class="post-metadata">

### Author: ![kennymc.c](https://avatars.discourse-cdn.com/v4/letter/k/eb9ed0/32.png) [@kennymc.c](https://vaultwarden.discourse.group/u/kennymc.c)
#### Post date: [July 9, 2023, 4:43pm UTC](https://vaultwarden.discourse.group/t/mobile-client-push-not-working/2767/3 "2023-07-09T16:43:03Z")

</div>

Re-installing the iOS app solved the problem. After logging in, I also got a message that push sync could now be activated.

---

<div class="post-metadata">

### Author: ![TKruzze](https://avatars.discourse-cdn.com/v4/letter/t/3da27b/32.png) [@TKruzze](https://vaultwarden.discourse.group/u/TKruzze)
#### Post date: [July 9, 2023, 11:27pm UTC](https://vaultwarden.discourse.group/t/mobile-client-push-not-working/2767/4 "2023-07-09T23:27:29Z")

</div>

Loving the new PUSH Sync on my devices! One thing I did encounter was that the feature doesn’t seem to be compatible with the F-Droid version of the Android app. Once I removed it and installed the Play Store version, everything worked perfectly.

---

<div class="post-metadata">

### Author: ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)
#### Post date: [July 10, 2023, 12:49pm UTC](https://vaultwarden.discourse.group/t/mobile-client-push-not-working/2767/5 "2023-07-10T12:49:27Z")

</div>

F-Droid versions doesn’t contain the Google Play libraries.

---

<div class="post-metadata">

### Author: ![paradeiser](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/paradeiser/32/1121_2.png) [@paradeiser](https://vaultwarden.discourse.group/u/paradeiser)
#### Post date: [July 13, 2023, 1:12pm UTC](https://vaultwarden.discourse.group/t/mobile-client-push-not-working/2767/6 "2023-07-13T13:12:34Z")

</div>

I couldn’t get it working on iOS. Even after uninstall, reboot, reinstall.  
Tho I get the pop-up on my iOS device after my first log-in to allow push notifications.  
But updates do not get pushed.

Is there some hint in the logs if the registration on the push server (using the Id & Key) is working at all?

Thanks,  
paradeiser

---

<div class="post-metadata">

### Author: ![floatingpurr](https://avatars.discourse-cdn.com/v4/letter/f/5f8ce5/32.png) [@floatingpurr](https://vaultwarden.discourse.group/u/floatingpurr)
#### Post date: [July 13, 2023, 2:43pm UTC](https://vaultwarden.discourse.group/t/mobile-client-push-not-working/2767/7 "2023-07-13T14:43:40Z")

</div>

I have 2 identical Valutwarden servers ver 1.29.0 registered on my iOS App. In the first push notifications work fine, in the second push notifications from App to Web work, **but not the other way around.** Something similar to the case reported by @kennymc.c

In my case, I’m running both servers behind two different Traefik reverse proxies. Logs do not show errors.

E.g., here is a create event from the browser:

```auto
vaultwarden | [2023-07-13 14:45:46.253][request][INFO] POST /api/ciphers
vaultwarden | [2023-07-13 14:45:46.340][response][INFO] (post_ciphers) POST /api/ciphers => 200 OK

```

Does anybody know how to troubleshoot this problem?

---

<div class="post-metadata">

### Author: ![j0g4](https://avatars.discourse-cdn.com/v4/letter/j/bbce88/32.png) [@j0g4](https://vaultwarden.discourse.group/u/j0g4)
#### Post date: [September 4, 2023, 8:21am UTC](https://vaultwarden.discourse.group/t/mobile-client-push-not-working/2767/8 "2023-09-04T08:21:53Z")

</div>

Facing more or less the same issue.

By creating an entry on my iOS devices, I can see the changes being reflected immediately on the web vault and chrome extension.  
Creating an entry within Chrome Extension/ Web Vault isn’t being reflected instant on my mobile devices.

I found the solution: [Using Bitwarden's push service · dani-garcia/vaultwarden · Discussion #2469 · GitHub](https://github.com/dani-garcia/vaultwarden/discussions/2469#discussioncomment-6585101)

you need to set up the host to US as location, to get push working correctly.
