rhino/vaultwarden
1
0
Fork 0
mirror of https://github.com/dani-garcia/vaultwarden.git synced 2026-03-22 09:49:20 -07:00
Code Issues Packages Projects Releases Wiki Activity

Execption router DNS rebind protection

Banshee350
2021-12-10 07:38:27 +01:00
parent d8d6c729f5
commit b309d0ee28
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Running-a-private-vaultwarden-instance-with-Let's-Encrypt-certs.md

@@ -59,6 +59,8 @@ export WEBSOCKET_ENABLED=true
You should now be able to reach your vaultwarden instance at https://my-vw.duckdns.org.
**Important:** If necessary, in some routers (e.g. FritzBox) an exception must be set for the domain (e.g., `my-vw.duckdns.org`) due to DNS rebind protection.
## Cloudflare setup
If you don't already have an account, create one at https://www.cloudflare.com/; you'll also have to go to your domain registrar to set your nameservers to the ones assigned to you by Cloudflare. Create a subdomain for your vaultwarden instance (e.g., `vw.example.com`), setting its IP to your vaultwarden host's private IP (e.g., `192.168.1.100`). For example:
@@ -111,6 +113,8 @@ export WEBSOCKET_ENABLED=true
You should now be able to reach your vaultwarden instance at https://vw.example.com.
**Important:** If necessary, in some routers (e.g. FritzBox) an exception must be set for the domain (e.g., `vw.example.com`) due to DNS rebind protection.
## Getting certs using the `lego` CLI
In the DuckDNS example above, Caddy used the `lego` library to get certs via DNS challenge.