# Synology updated - broke API

**URL:** <https://vaultwarden.discourse.group/t/synology-updated-broke-api/991>\
**Category:** Help\
**Created:** [July 7, 2021, 11:16am UTC](https://vaultwarden.discourse.group/t/synology-updated-broke-api/991 "2021-07-07T11:16:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cathodeinmytea](https://avatars.discourse-cdn.com/v4/letter/c/c37758/32.png) [@cathodeinmytea](https://vaultwarden.discourse.group/u/cathodeinmytea)\
**Post date:** [July 7, 2021, 11:16am UTC](https://vaultwarden.discourse.group/t/synology-updated-broke-api/991/1 "2021-07-07T11:16:43Z")

</div>

I had everything working lovely on my Synology in docker, and then I updated my operating system to DSM 7 but now vaultwarden wont start in docker and gives me error of API. How do I get this working again without losing my persistant data?

---

<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 7, 2021, 2:52pm UTC](https://vaultwarden.discourse.group/t/synology-updated-broke-api/991/2 "2021-07-07T14:52:51Z")

</div>

Have you checked the Synology forums for similar issues with Docker images?

Also, noting that it gives an error of API isn’t very useful. Do you maybe have a better error message, the exact message for example, or a screenshot or something?

---

<div class="post-metadata">

**Author:** ![cathodeinmytea](https://avatars.discourse-cdn.com/v4/letter/c/c37758/32.png) [@cathodeinmytea](https://vaultwarden.discourse.group/u/cathodeinmytea)\
**Post date:** [July 7, 2021, 7:43pm UTC](https://vaultwarden.discourse.group/t/synology-updated-broke-api/991/3 "2021-07-07T19:43:08Z")

</div>

thank you for reply. I did another reboot, and the container now starts and I can open up to a login page on http but it now doesn’t want to work on https.  
 ![image](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/051911898947c2ea9c2e643a403337ac09b7f38d.png)  
[http://local:5151](http://local:5151) presents login. When submit credentials gives error it must be https.  
I try [https://local:5151](https://local:5151) and no page loads.

The only change to working configuration was the OS upgrade, it may have done something to nginx??? If so, any ideas where to go?