# Can\`t access to local site vaultwarden

**URL:** <https://vaultwarden.discourse.group/t/can-t-access-to-local-site-vaultwarden/867>\
**Category:** Help\
**Created:** [April 30, 2021, 9:58pm UTC](https://vaultwarden.discourse.group/t/can-t-access-to-local-site-vaultwarden/867 "2021-04-30T21:58:10Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rim13](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/rim13/32/323_2.png) [@Rim13](https://vaultwarden.discourse.group/u/Rim13)\
**Post date:** [April 30, 2021, 9:58pm UTC](https://vaultwarden.discourse.group/t/can-t-access-to-local-site-vaultwarden/867/1 "2021-04-30T21:58:10Z")

</div>

I use [Caddy with DNS challenge](for local using)  
Container “caddy” logs show me:

`"tls.obtain","msg":"certificate obtained successfully"`

Container “vaultwarden” logs show me:

```
FO] No .env file found.
[2021-04-30 21:35:41.315][vaultwarden][INFO] JWT keys don't exist, checking if OpenSSL is available...
OpenSSL 1.1.1d 10 Sep 2019
[2021-04-30 21:35:41.325][vaultwarden][INFO] OpenSSL detected, creating keys...
Generating RSA private key, 2048 bit long modulus (2 primes)
e is 65537 (0x010001)
writing RSA key
writing RSA key
[2021-04-30 21:35:41.624][vaultwarden][INFO] Keys created correctly.
Running migration 20180114171611
...
Running migration 20210315163412
[2021-04-30 21:35:41.764][parity_ws][INFO] Listening for new connections on 0.0.0.0:3012.
[2021-04-30 21:35:41.766][start][INFO] Rocket has launched from http://0.0.0.0:80

```

I go to server ip http : [//192.168.1.90/](https://192.168.1.90/) get redirect to https : [//192.168.1.90/](https://192.168.1.90/) and then get error `ERR_SSL_PROTOCOL_ERROR`

What have I done wrong?

---

<div class="post-metadata">

**Author:** ![Rim13](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/rim13/32/323_2.png) [@Rim13](https://vaultwarden.discourse.group/u/Rim13)\
**Post date:** [April 30, 2021, 10:07pm UTC](https://vaultwarden.discourse.group/t/can-t-access-to-local-site-vaultwarden/867/2 "2021-04-30T22:07:08Z")

</div>

```
version: '3'

services:
  vaultwarden:
    image: vaultwarden/server:latest
    container_name: vaultwarden
    restart: always
    environment:
      - WEBSOCKET_ENABLED=true # Enable WebSocket notifications.
    volumes:
      - ./vw-data:/data

  caddy:
    image: caddy:2
    container_name: caddy
    restart: always
    ports:
      - 80:80
      - 443:443
    volumes:
      - ./caddy:/usr/bin/caddy # Your custom build of Caddy.
      - ./Caddyfile:/etc/caddy/Caddyfile:ro
      - ./caddy-config:/config
      - ./caddy-data:/data
    environment:
      - DOMAIN=vaultwarden. *****.duckdns.org # Your domain.
      - EMAIL=r ******* @yandex.ru # The email address to use for ACME registration.
      - DUCKDNS_TOKEN=2 ********-**** - ****-**** - *********** 9 # Your Duck DNS token.
      - LOG_FILE=/data/access.log
```

---

<div class="post-metadata">

**Author:** ![Rim13](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/rim13/32/323_2.png) [@Rim13](https://vaultwarden.discourse.group/u/Rim13)\
**Post date:** [May 3, 2021, 8:17am UTC](https://vaultwarden.discourse.group/t/can-t-access-to-local-site-vaultwarden/867/3 "2021-05-03T08:17:22Z")

</div>

I find my error.

> **[dani-garcia/vaultwarden](https://github.com/dani-garcia/vaultwarden/wiki/Running-a-private-vaultwarden-instance-with-Let's-Encrypt-certs)**
>
> Running-a-private-vaultwarden-instance-with-Let's-Encrypt-certs

Need set up domain to local address 192.168.1.90 in DuckDNS settings.

---

<div class="post-metadata">

**Author:** ![damaskin](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/damaskin/32/306_2.png) [@damaskin](https://vaultwarden.discourse.group/u/damaskin)\
**Post date:** [May 3, 2021, 9:04pm UTC](https://vaultwarden.discourse.group/t/can-t-access-to-local-site-vaultwarden/867/4 "2021-05-03T21:04:10Z")

</div>

> [@Rim13](#):
>
> Need set up domain to local address 192.168.1.90 in DuckDNS settings.

Can you elaborate this, please?

---

<div class="post-metadata">

**Author:** ![Rim13](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/rim13/32/323_2.png) [@Rim13](https://vaultwarden.discourse.group/u/Rim13)\
**Post date:** [May 8, 2021, 11:47am UTC](https://vaultwarden.discourse.group/t/can-t-access-to-local-site-vaultwarden/867/5 "2021-05-08T11:47:32Z")

</div>

Only using this instruction.

> **[Using Docker Compose](https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker-Compose#caddy-with-dns-challenge)**
>
> Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden\_rs - dani-garcia/vaultwarden

And this topic say me duckdns settings.

> **[Running a private vaultwarden instance with Let's Encrypt certs](https://github.com/dani-garcia/vaultwarden/wiki/Running-a-private-vaultwarden-instance-with-Let's-Encrypt-certs)**
>
> Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden\_rs - dani-garcia/vaultwarden

> If you don’t already have an account, create one at [https://www.duckdns.org/](https://www.duckdns.org/). Create a subdomain for your vaultwarden instance (e.g., `my-vw.duckdns.org` ), setting its IP to your vaultwarden host’s private IP (e.g., `192.168.1.100` ). Make note of your account’s token (a string in [UUID](https://en.wikipedia.org/wiki/UUID) format). Caddy will need this token to solve the DNS challenge.

 ![Снимок экрана 2021-05-08 144554](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/91d4f3979fd41d55d0ac68afca63e893a886c7b0.png)  
ip address of my rasp pi with docker  
and now vaultwarden work in local network. no ssl error.

I can access to my vaultwarden only using this address '[https://vaultwarden](https://vaultwarden).\*\*\*\*\*.duckdns.org

If i use ip address [https://192.168.1.91](https://192.168.1.91) i got error ERR\_SSL\_PROTOCOL\_ERROR

---

<div class="post-metadata">

**Author:** ![masteryoda](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@masteryoda](https://vaultwarden.discourse.group/u/masteryoda)\
**Post date:** [May 10, 2021, 7:45pm UTC](https://vaultwarden.discourse.group/t/can-t-access-to-local-site-vaultwarden/867/6 "2021-05-10T19:45:03Z")

</div>

these are my settings and it works fine with caddy as reverse proxy. i use opnsense & add a host override in Unbound

```
services:
 vaultwarden:
  image: vaultwarden/server:latest
  container_name: bitwarden
  restart: always
  volumes:
      - /opt/bitwarden/newdata:/data/
  ports:
    - 8088:80
    - 3012:3012
  environment:
    LOG_FILE: '/opt/bitwarden/bitwarden.log'
    LOG_LEVEL: 'debug'
    EXTENDED_LOGGING: 'true'
    WEB_VAULT_ENABLED: 'true'
    WEBSOCKET_ENABLED: 'true'
    WEBSOCKET_PORT: '3012'
    ADMIN_TOKEN: 'xxx'
    SIGNUPS_ALLOWED: 'true'
    DATABASE_URL: "mysql://bitwarden_rs:12345@192.168.11.67:3306/bitwarden_rs"

```

CADDY SETTINGS

```
vaultwarden.foo.com {
  # The negotiation endpoint is also proxied to Rocket
  reverse_proxy /notifications/hub/negotiate 192.168.11.74:8088

  # Notifications redirected to the websockets server
  reverse_proxy /notifications/hub 192.168.11.74:3012

  # Proxy the Root directory to Rocket
  reverse_proxy 192.168.11.74:8088

  header {
       # Enable cross-site filter (XSS) and tell browser to block detected attacks
       X-XSS-Protection "1; mode=block"
       # Disallow the site to be rendered within a frame (clickjacking protection)
       X-Frame-Options "DENY"
       # Prevent search engines from indexing (optional)
       X-Robots-Tag "none"
       # Server name removing
       -Server
   }
}
```
