# Ver 1.15 requires ssl for web vault

**URL:** <https://vaultwarden.discourse.group/t/ver-1-15-requires-ssl-for-web-vault/137>\
**Category:** Help\
**Created:** [June 6, 2020, 4:46am UTC](https://vaultwarden.discourse.group/t/ver-1-15-requires-ssl-for-web-vault/137 "2020-06-06T04:46:20Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![gerootech](https://avatars.discourse-cdn.com/v4/letter/g/7ea924/32.png) [@gerootech](https://vaultwarden.discourse.group/u/gerootech)\
**Post date:** [June 6, 2020, 4:46am UTC](https://vaultwarden.discourse.group/t/ver-1-15-requires-ssl-for-web-vault/137/1 "2020-06-06T04:46:20Z")

</div>

Hi,

I have bitwarden\_rs running only on my home network and not really accessible through the internet, so i was good with using it on http, however after i have upgraded to ver 1.15 and i was trying to access to web vault, it is says it requires ssl.

Is there a way to disable this requirement ?? and just use http for now ??

---

<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:** [June 6, 2020, 12:41pm UTC](https://vaultwarden.discourse.group/t/ver-1-15-requires-ssl-for-web-vault/137/2 "2020-06-06T12:41:04Z")

</div>

Hello @gerootech,

Welcome to the forum.  
Unfortunately no, since this is not something we can control.  
It’s the browsers which are getting more restrictive about using encryption on non https enabled sites. This also would effect the older version, so it will not help going back.

Best thing would be to create a self-signed certificate.  
You could try [https://github.com/FiloSottile/mkcert](https://github.com/FiloSottile/mkcert) to create one. That would be enough for home usage.

---

<div class="post-metadata">

**Author:** ![gerootech](https://avatars.discourse-cdn.com/v4/letter/g/7ea924/32.png) [@gerootech](https://vaultwarden.discourse.group/u/gerootech)\
**Post date:** [June 7, 2020, 4:22am UTC](https://vaultwarden.discourse.group/t/ver-1-15-requires-ssl-for-web-vault/137/3 "2020-06-07T04:22:18Z")

</div>

Thanks for the quick reply, however i can use other local hosted applications without SSL. Also the error attached seems to be coming from the bitwardenrs web console not from my firefox. ![bw_ssl_error](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/be21afbbf946886bb7f869f43cc6dfe41be387b3.png)

However i can access it using the regular Edge Browser (non Chromium) so i will look into implementing a self signed cert.

---

<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:** [June 7, 2020, 6:38am UTC](https://vaultwarden.discourse.group/t/ver-1-15-requires-ssl-for-web-vault/137/4 "2020-06-07T06:38:36Z")

</div>

It’s has to do with the JavaScript encryption api. Chromium based browsers and since one of the latest Firefox versions do not allow the usage of the encryption api on non ssl connections.

The reason you see a bitwarden\_rs message is because we changed the default error which wasn’t clear at all.

Internet Explorer does indeed work, but the latest edge on chromium based will fall.

---

<div class="post-metadata">

**Author:** ![compros](https://avatars.discourse-cdn.com/v4/letter/c/919ad9/32.png) [@compros](https://vaultwarden.discourse.group/u/compros)\
**Post date:** [January 6, 2023, 1:11pm UTC](https://vaultwarden.discourse.group/t/ver-1-15-requires-ssl-for-web-vault/137/5 "2023-01-06T13:11:33Z")

</div>

I know this is older but I have this set up on a Synology NAS and have reverse proxy set up and a Cert from Let’s Encrypt set up for it. I have a DNS name. Everything works from the public side but am getting the same message as above about HTTP. Any other ideas that can help? I am hitting the docker container from the hostname and external port so all the plumbing to the docker seems right.

---

<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:** [January 6, 2023, 9:59pm UTC](https://vaultwarden.discourse.group/t/ver-1-15-requires-ssl-for-web-vault/137/6 "2023-01-06T21:59:59Z")

</div>

And you do connect via https?? That should just work fine.
