How to use https connection in local network? #62

Closed
opened 2025-11-07 06:20:59 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @ghost on GitHub (Aug 3, 2018).

My local vault is on 192.168.0.5:8123 (docker on my NAS), port 8123 is forwarded to 80, so no http.
How to use https connection to it? I know I need to set port binding 8123 to 443 but what about cert files?
Do I need to generate certs for 192.168.0.5?
Docs (https://hub.docker.com/r/mprasil/bitwarden/#enabling-https) say I need a domain but I don't have a domain, I want to use it only in my local network and over vpn but with https connection to it.

Thanks ;)

Originally created by @ghost on GitHub (Aug 3, 2018). My local vault is on 192.168.0.5:8123 (docker on my NAS), port 8123 is forwarded to 80, so no http. How to use https connection to it? I know I need to set port binding 8123 to 443 but what about cert files? Do I need to generate certs for 192.168.0.5? Docs (https://hub.docker.com/r/mprasil/bitwarden/#enabling-https) say I need a domain but I don't have a domain, I want to use it only in my local network and over vpn but with https connection to it. Thanks ;)
Author
Owner

@dani-garcia commented on GitHub (Aug 3, 2018):

I don’t think you need a domain for HTTPS, only for U2F authentication.

You can generate a self signed certificate for your IP, but you’ll probably need to import it in all your devices to avoid certificate warnings.

@dani-garcia commented on GitHub (Aug 3, 2018): I don’t think you need a domain for HTTPS, only for U2F authentication. You can generate a self signed certificate for your IP, but you’ll probably need to import it in all your devices to avoid certificate warnings.
Author
Owner

@ghost commented on GitHub (Aug 3, 2018):

Ok Thanks

@ghost commented on GitHub (Aug 3, 2018): Ok Thanks
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#62