# Synchronisation failed while server reports sync 200 OK

**URL:** <https://vaultwarden.discourse.group/t/synchronisation-failed-while-server-reports-sync-200-ok/3194>\
**Category:** Help\
**Created:** [December 18, 2023, 12:49pm UTC](https://vaultwarden.discourse.group/t/synchronisation-failed-while-server-reports-sync-200-ok/3194 "2023-12-18T12:49:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Teapet](https://avatars.discourse-cdn.com/v4/letter/t/ba9def/32.png) [@Teapet](https://vaultwarden.discourse.group/u/Teapet)\
**Post date:** [December 18, 2023, 12:49pm UTC](https://vaultwarden.discourse.group/t/synchronisation-failed-while-server-reports-sync-200-ok/3194/1 "2023-12-18T12:49:38Z")

</div>

I’m using Vaultwarden Docker version 1.30.1 with NPM (Nginx Proxy Manager) and the latest version of Chrome & Firefox Bitwarden addons.

The browser addons report ‘synchronisation failed’ while Vaultwarden reports ‘200 OK’;  
[2023-12-18 13:40:27.425][start][INFO] Rocket has launched from [http://0.0.0.0:80](http://0.0.0.0:80)  
[2023-12-18 13:40:43.550][request][INFO] POST /identity/connect/token  
[2023-12-18 13:40:43.562][response][INFO] (login) POST /identity/connect/token =\> 200 OK  
[2023-12-18 13:40:43.868][request][INFO] GET /api/sync  
[2023-12-18 13:40:43.971][response][INFO] (sync) GET /api/sync?\<data…\> =\> 200 OK  
[2023-12-18 13:41:11.228][request][INFO] POST /identity/connect/token  
[2023-12-18 13:41:11.248][response][INFO] (login) POST /identity/connect/token =\> 200 OK  
[2023-12-18 13:41:11.537][request][INFO] GET /api/sync  
[2023-12-18 13:41:11.695][response][INFO] (sync) GET /api/sync?\<data…\> =\> 200 OK  
[2023-12-18 13:42:40.628][request][INFO] GET /notifications/hub?access\_token=xxxx  
[2023-12-18 13:42:40.628][vaultwarden::api::notifications][INFO] Accepting Rocket WS connection from 192.168.1.19  
[2023-12-18 13:42:40.629][response][INFO] (websockets\_hub) GET /notifications/hub?\<data…\> =\> 200 OK  
[2023-12-18 13:42:40.645][request][INFO] GET /api/accounts/revision-date  
[2023-12-18 13:42:40.647][response][INFO] (revision\_date) GET /api/accounts/revision-date =\> 200 OK  
[2023-12-18 13:44:31.897][request][INFO] GET /notifications/hub?access\_token=xxx  
[2023-12-18 13:44:31.897][vaultwarden::api::notifications][INFO] Accepting Rocket WS connection from 192.168.1.19  
[2023-12-18 13:44:31.898][response][INFO] (websockets\_hub) GET /notifications/hub?\<data…\> =\> 200 OK  
[2023-12-18 13:44:31.932][request][INFO] GET /api/accounts/revision-date  
[2023-12-18 13:44:31.934][response][INFO] (revision\_date) GET /api/accounts/revision-date =\> 200 OK

the NPM config file looks like this;

```auto
#------------------------------------------------------------

# The `upstream` directives ensure that you have a xxxx/1.1 connection
# This enables the keepalive option and better performance
#
# Define the server IP and ports here.
upstream 192.168.1.17 {
  zone 192.168.1.17 64k;
  server 192.168.1.17;
  keepalive 2;
}

map $http_upgrade $connection_upgrade {
    default upgrade;
    '' "";
}

server {
  set $forward_scheme http;
  set $server "192.168.1.17";
  set $port 80;

  listen 80;
listen [::]:80;

listen 443 ssl http2;
listen [::]:443 ssl http2;

  server_name vault.xxx;

  # Let's Encrypt SSL
  include conf.d/include/letsencrypt-acme-challenge.conf;
  include conf.d/include/ssl-ciphers.conf;
  ssl_certificate /etc/letsencrypt/live/npm-2/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/npm-2/privkey.pem;

  # Block Exploits
  include conf.d/include/block-exploits.conf;

    # Force SSL
    include conf.d/include/force-ssl.conf;

proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $http_connection;
proxy_xxxx_version 1.1;

  access_log /data/logs/proxy-host-2_access.log proxy;
  error_log /data/logs/proxy-host-2_error.log warn;

location / {
    proxy_pass http://192.168.1.17;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
  }

location /notifications/hub {
    proxy_pass http://192.168.1.17:3012;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
  }

  location /notifications/hub/negotiate {
    proxy_pass http://192.168.1.17:80;
  }

  # Custom
  include /data/nginx/custom/server_proxy[.]conf;
}
```

Is something wrong in the NPM configuration?

---

<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:** [December 18, 2023, 7:26pm UTC](https://vaultwarden.discourse.group/t/synchronisation-failed-while-server-reports-sync-200-ok/3194/2 "2023-12-18T19:26:14Z")

</div>

Fully logout and back in again. That should solve your issue.

---

<div class="post-metadata">

**Author:** ![Teapet](https://avatars.discourse-cdn.com/v4/letter/t/ba9def/32.png) [@Teapet](https://vaultwarden.discourse.group/u/Teapet)\
**Post date:** [December 19, 2023, 7:37pm UTC](https://vaultwarden.discourse.group/t/synchronisation-failed-while-server-reports-sync-200-ok/3194/3 "2023-12-19T19:37:35Z")

</div>

Thanks, that solved the issue.

I used this guide for NPM configuration, the earlier config didn’t work. (for others that read this afterwards)  
[Vaultwarden and Nginx Proxy Manager - #3 by hannesfrater](https://vaultwarden.discourse.group/t/vaultwarden-and-nginx-proxy-manager/1307/3)