URLs must use https for localhost

[shimpact003]

I set up a local vaultwarden instance as a systemd service on nixos with caddy as my reverse proxy. The reverse proxy works, since I can use bitwarden from my android phone as the client and can also visit the webvault on the machine, but when I try to connect to the instance with the browser extension on firefox using localhost, I get the error that urls must use https. I could add an exception to my dns server to not trigger rebind protection and just use the reverse proxy, but since I will carry my machine around, I would like the extension to work when I move it to other places and not have to rely on the webvault.

Any help appreciated

[shimpact003]

I just solved it by temporarily allowing unverified addons and setting the extension up using an older version from bitwardens repo, then upgrading to the latest version after adding my server.

[stefan0xC]

Since the clients now require HTTPS even on localhost you can enable HTTPS e.g. by using something like mkcert to generate a locally-trusted certificate.

[NegaScout]

Why it does not generate its own self signed certificates, if there are non provided? I just wanted to try it out and this suprised me and now I have to hassle and generate certs and I am lazy :D

[BlackDex]

Because self-signed certs do cause issues with some clients.
Also, if you are using a reverse proxy which handles the SSL stuff, than forcing HTTPS is also not needed.

Also, currently Rocket (The web-framework we use), doesn't support both HTTP and HTTPS at the same time without too much hassle.