[GH-ISSUE #578] User registration yes, login no #380

Closed
opened 2026-03-03 01:28:33 +03:00 by kerem · 12 comments
Owner

Originally created by @blacknet76 on GitHub (Aug 17, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/578

Hi all,

I have a problem to get it to work. I can register a new user but I can't login with it. I got always this error "An error has occurred. An unexpected error occurred." (Is translatet from German output). I can't see also a entry in the bitwareden.log file.
I checked the MySQL DB and the new user is added.
I hope anyone can help and I forgot a stupid setting in my docker-compose file.

Here are my docker-compose.yml


networks:
  internal:
    external: false
  default:
    driver: bridge

services:
  mysql:
    container_name: mysql
    image: mysql:5.7
    ports:
      - 3306:3306
    networks:
      - internal
      - default
    environment:
      - MYSQL_ROOT_PASSWORD=totalsecure
      - MYSQL_DATABASE=bitwarden
      - MYSQL_USER=bitwarden
      - MYSQL_PASSWORD=bitwarden

  bitwarden:
    container_name: bitwarden
    image: bitwardenrs/server:latest
    restart: always
    depends_on:
      - mysql
    networks:
      - internal
      - default
    ports:
      - 80:80
      - 433:433
    volumes:
      - ${USERDIR}/.config/bw-data:/data
    environment:
      WEBSOCKET_ENABLED: "true" # Required to use websockets
      SIGNUPS_ALLOWED: "true" # set to false to disable signups
      SMTP_HOST: "smtp.gamil.com"
      SMTP_FROM: "xxxxxxx@gmail.com"
      SMTP_PORT: "465"
      SMTP_SSL: "true"
      SMTP_USERNAME: "xxxxxx@gamil.com"
      SMTP_PASSWORD: "xxxxxxx"
      LOG_FILE: "/data/bitwarden.log"
      RUST_BACKTRACE: 1
      DATABASE_URL: "mysql://bitwarden:bitwarden@mysql/bitwarden"
      ADMIN_TOKEN: "totalsecureto"
      ENABLE_DB_WAL: "false"

Originally created by @blacknet76 on GitHub (Aug 17, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/578 Hi all, I have a problem to get it to work. I can register a new user but I can't login with it. I got always this error "An error has occurred. An unexpected error occurred." (Is translatet from German output). I can't see also a entry in the bitwareden.log file. I checked the MySQL DB and the new user is added. I hope anyone can help and I forgot a stupid setting in my docker-compose file. Here are my docker-compose.yml ```version: "3.6" networks: internal: external: false default: driver: bridge services: mysql: container_name: mysql image: mysql:5.7 ports: - 3306:3306 networks: - internal - default environment: - MYSQL_ROOT_PASSWORD=totalsecure - MYSQL_DATABASE=bitwarden - MYSQL_USER=bitwarden - MYSQL_PASSWORD=bitwarden bitwarden: container_name: bitwarden image: bitwardenrs/server:latest restart: always depends_on: - mysql networks: - internal - default ports: - 80:80 - 433:433 volumes: - ${USERDIR}/.config/bw-data:/data environment: WEBSOCKET_ENABLED: "true" # Required to use websockets SIGNUPS_ALLOWED: "true" # set to false to disable signups SMTP_HOST: "smtp.gamil.com" SMTP_FROM: "xxxxxxx@gmail.com" SMTP_PORT: "465" SMTP_SSL: "true" SMTP_USERNAME: "xxxxxx@gamil.com" SMTP_PASSWORD: "xxxxxxx" LOG_FILE: "/data/bitwarden.log" RUST_BACKTRACE: 1 DATABASE_URL: "mysql://bitwarden:bitwarden@mysql/bitwarden" ADMIN_TOKEN: "totalsecureto" ENABLE_DB_WAL: "false" ```
kerem closed this issue 2026-03-03 01:28:34 +03:00
Author
Owner

@dani-garcia commented on GitHub (Aug 18, 2019):

If there aren't any errors in the logfile, can you check the web browsers console? Or maybe the network requests tab?

<!-- gh-comment-id:522339360 --> @dani-garcia commented on GitHub (Aug 18, 2019): If there aren't any errors in the logfile, can you check the web browsers console? Or maybe the network requests tab?
Author
Owner

@blacknet76 commented on GitHub (Aug 19, 2019):

In the logfile is no error reportet. In the browser console under network I get status 500 for token and for prelogin is the status 200

Header

Anfragemethode:POST
Externe Adresse:192.168.16.44:80
Status-Code:
500 Internal Server Error
Version:HTTP/1.1
Referrer Policy:same-origin


Date: Mon, 19 Aug 2019 13:12:35 GMT
Transfer-Encoding: chunked

Accept	
application/json
Accept-Encoding	
gzip, deflate
Accept-Language	
de-DE,en-US;q=0.7,en;q=0.3
Connection	
keep-alive
Content-Length	
240
Content-Type	
application/x-www-form-urlencoded; charset=utf-8
Cookie	
portainer.datatable_text_filte…freshRate%22%3A%2230%22%7D%7D
Device-Type	
10
Host	
192.168.16.44
Origin	
http://192.168.16.44
Referer	
http://192.168.16.44/
User-Agent	
Mozilla/5.0 (Windows NT 10.0; …) Gecko/20100101 Firefox/68.0

Parameters

username	xxxx@xxx.com
password	xxxxxxx
scope	api offline_access
client_id	web
deviceType	10
deviceIdentifier	0cxxxx4-abd4-4ed8-b3db-79xxxxxxx0
deviceName	firefox

In the docker log I get following

[2019-08-19 15:03:06][_][INFO] Matched: POST /api/accounts/prelogin (prelogin)
[2019-08-19 15:03:06][_][INFO] Outcome: Success
[2019-08-19 15:03:06][_][INFO] Response succeeded.
[2019-08-19 15:03:06][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8:
[2019-08-19 15:03:06][_][INFO] Matched: POST /identity/connect/token (login)
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Custom { kind: Other, error: "failed to lookup address information: Name or service not known" })', src/libcore/result.rs:1084:5
stack backtrace:
   0:     0x55e1f4bd602b - backtrace::backtrace::libunwind::trace::h0a49ebd6e6b617b0
                               at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.34/src/backtrace/libunwind.rs:88
   1:     0x55e1f4bd602b - backtrace::backtrace::trace_unsynchronized::h0938c45c18b11eef
                               at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.34/src/backtrace/mod.rs:66
   2:     0x55e1f4bd602b - std::sys_common::backtrace::_print::hd677aaf2ed0072ee
                               at src/libstd/sys_common/backtrace.rs:47
   3:     0x55e1f4bd602b - std::sys_common::backtrace::print::h6c6fcad352b2c3f5
                               at src/libstd/sys_common/backtrace.rs:36
   4:     0x55e1f4bd602b - std::panicking::default_hook::{{closure}}::hd274b9d6c771d68f
                               at src/libstd/panicking.rs:200
   5:     0x55e1f4bd5d06 - std::panicking::default_hook::h4d2e8e9936aa55b3
                               at src/libstd/panicking.rs:214
   6:     0x55e1f4bd679d - std::panicking::rust_panic_with_hook::h897a9451d2669ca8
                               at src/libstd/panicking.rs:477
   7:     0x55e1f4bd6322 - std::panicking::continue_panic_fmt::h35404537578c9893
                               at src/libstd/panicking.rs:384
   8:     0x55e1f4bd6206 - rust_begin_unwind
                               at src/libstd/panicking.rs:311
   9:     0x55e1f4bf7c3d - core::panicking::panic_fmt::h772cfe55da576359
                               at src/libcore/panicking.rs:85
  10:     0x55e1f4bf7d37 - core::result::unwrap_failed::h00271bebc73f1849
                               at src/libcore/result.rs:1084
  11:     0x55e1f44da7ad - bitwarden_rs::mail::send_email::hacb7a2ac0708d881
  12:     0x55e1f44cd05d - bitwarden_rs::api::identity::_password_login::h7ec4acf91fcb5dc5
  13:     0x55e1f44e63a6 - bitwarden_rs::api::identity::rocket_route_fn_login::haaf73a7f7d484766
  14:     0x55e1f4ab23ce - <F as rocket::handler::Handler>::handle::hacf7be7180576e3b
  15:     0x55e1f4aa1603 - rocket::rocket::Rocket::route_and_process::h19471d36366a8ee9
  16:     0x55e1f4a9f85e - <rocket::rocket::Rocket as hyper::server::Handler>::handle::hc394653f8ac3f461
  17:     0x55e1f4abbe85 - hyper::server::Worker<H>::handle_connection::h836d8ff738817548
  18:     0x55e1f4a7e87c - hyper::server::listener::spawn_with::{{closure}}::h9c3a55fae7b32ee5
  19:     0x55e1f4a7c2c7 - std::sys_common::backtrace::__rust_begin_short_backtrace::h2711a1cce1735ce0
  20:     0x55e1f4ac16a7 - std::panicking::try::do_call::hd35eb81f209594f8
  21:     0x55e1f4be00fa - __rust_maybe_catch_panic
                               at src/libpanic_unwind/lib.rs:80
  22:     0x55e1f4a844ae - core::ops::function::FnOnce::call_once{{vtable.shim}}::h26db022abdb10aa4
  23:     0x55e1f4bc5f0f - <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once::hd8f702020bfca7ea
                               at /rustc/2111aed0a38c819acb140c7153e9366964a37f2f/src/liballoc/boxed.rs:787
  24:     0x55e1f4bdf440 - <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once::h54ddf093dc220806
                               at /rustc/2111aed0a38c819acb140c7153e9366964a37f2f/src/liballoc/boxed.rs:787
  25:     0x55e1f4bdf440 - std::sys_common::thread::start_thread::h1381a08406ee1842
                               at src/libstd/sys_common/thread.rs:13
  26:     0x55e1f4bdf440 - std::sys::unix::thread::Thread::new::thread_start::hf3104e647102288b
                               at src/libstd/sys/unix/thread.rs:79
  27:     0x7f19671aa4a4 - start_thread
  28:     0x7f1966cd5d0f - __clone
  29:                0x0 - <unknown>
<!-- gh-comment-id:522570169 --> @blacknet76 commented on GitHub (Aug 19, 2019): In the logfile is no error reportet. In the browser console under network I get status 500 for token and for prelogin is the status 200 Header ```Angefragte Adresse:http://192.168.16.44/identity/connect/token Anfragemethode:POST Externe Adresse:192.168.16.44:80 Status-Code: 500 Internal Server Error Version:HTTP/1.1 Referrer Policy:same-origin Date: Mon, 19 Aug 2019 13:12:35 GMT Transfer-Encoding: chunked Accept application/json Accept-Encoding gzip, deflate Accept-Language de-DE,en-US;q=0.7,en;q=0.3 Connection keep-alive Content-Length 240 Content-Type application/x-www-form-urlencoded; charset=utf-8 Cookie portainer.datatable_text_filte…freshRate%22%3A%2230%22%7D%7D Device-Type 10 Host 192.168.16.44 Origin http://192.168.16.44 Referer http://192.168.16.44/ User-Agent Mozilla/5.0 (Windows NT 10.0; …) Gecko/20100101 Firefox/68.0 ``` Parameters ```grant_type password username xxxx@xxx.com password xxxxxxx scope api offline_access client_id web deviceType 10 deviceIdentifier 0cxxxx4-abd4-4ed8-b3db-79xxxxxxx0 deviceName firefox ``` In the docker log I get following ```[2019-08-19 15:03:06][rocket::rocket][INFO] POST /api/accounts/prelogin application/json; charset=utf-8: [2019-08-19 15:03:06][_][INFO] Matched: POST /api/accounts/prelogin (prelogin) [2019-08-19 15:03:06][_][INFO] Outcome: Success [2019-08-19 15:03:06][_][INFO] Response succeeded. [2019-08-19 15:03:06][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8: [2019-08-19 15:03:06][_][INFO] Matched: POST /identity/connect/token (login) thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Custom { kind: Other, error: "failed to lookup address information: Name or service not known" })', src/libcore/result.rs:1084:5 stack backtrace: 0: 0x55e1f4bd602b - backtrace::backtrace::libunwind::trace::h0a49ebd6e6b617b0 at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.34/src/backtrace/libunwind.rs:88 1: 0x55e1f4bd602b - backtrace::backtrace::trace_unsynchronized::h0938c45c18b11eef at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.34/src/backtrace/mod.rs:66 2: 0x55e1f4bd602b - std::sys_common::backtrace::_print::hd677aaf2ed0072ee at src/libstd/sys_common/backtrace.rs:47 3: 0x55e1f4bd602b - std::sys_common::backtrace::print::h6c6fcad352b2c3f5 at src/libstd/sys_common/backtrace.rs:36 4: 0x55e1f4bd602b - std::panicking::default_hook::{{closure}}::hd274b9d6c771d68f at src/libstd/panicking.rs:200 5: 0x55e1f4bd5d06 - std::panicking::default_hook::h4d2e8e9936aa55b3 at src/libstd/panicking.rs:214 6: 0x55e1f4bd679d - std::panicking::rust_panic_with_hook::h897a9451d2669ca8 at src/libstd/panicking.rs:477 7: 0x55e1f4bd6322 - std::panicking::continue_panic_fmt::h35404537578c9893 at src/libstd/panicking.rs:384 8: 0x55e1f4bd6206 - rust_begin_unwind at src/libstd/panicking.rs:311 9: 0x55e1f4bf7c3d - core::panicking::panic_fmt::h772cfe55da576359 at src/libcore/panicking.rs:85 10: 0x55e1f4bf7d37 - core::result::unwrap_failed::h00271bebc73f1849 at src/libcore/result.rs:1084 11: 0x55e1f44da7ad - bitwarden_rs::mail::send_email::hacb7a2ac0708d881 12: 0x55e1f44cd05d - bitwarden_rs::api::identity::_password_login::h7ec4acf91fcb5dc5 13: 0x55e1f44e63a6 - bitwarden_rs::api::identity::rocket_route_fn_login::haaf73a7f7d484766 14: 0x55e1f4ab23ce - <F as rocket::handler::Handler>::handle::hacf7be7180576e3b 15: 0x55e1f4aa1603 - rocket::rocket::Rocket::route_and_process::h19471d36366a8ee9 16: 0x55e1f4a9f85e - <rocket::rocket::Rocket as hyper::server::Handler>::handle::hc394653f8ac3f461 17: 0x55e1f4abbe85 - hyper::server::Worker<H>::handle_connection::h836d8ff738817548 18: 0x55e1f4a7e87c - hyper::server::listener::spawn_with::{{closure}}::h9c3a55fae7b32ee5 19: 0x55e1f4a7c2c7 - std::sys_common::backtrace::__rust_begin_short_backtrace::h2711a1cce1735ce0 20: 0x55e1f4ac16a7 - std::panicking::try::do_call::hd35eb81f209594f8 21: 0x55e1f4be00fa - __rust_maybe_catch_panic at src/libpanic_unwind/lib.rs:80 22: 0x55e1f4a844ae - core::ops::function::FnOnce::call_once{{vtable.shim}}::h26db022abdb10aa4 23: 0x55e1f4bc5f0f - <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once::hd8f702020bfca7ea at /rustc/2111aed0a38c819acb140c7153e9366964a37f2f/src/liballoc/boxed.rs:787 24: 0x55e1f4bdf440 - <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once::h54ddf093dc220806 at /rustc/2111aed0a38c819acb140c7153e9366964a37f2f/src/liballoc/boxed.rs:787 25: 0x55e1f4bdf440 - std::sys_common::thread::start_thread::h1381a08406ee1842 at src/libstd/sys_common/thread.rs:13 26: 0x55e1f4bdf440 - std::sys::unix::thread::Thread::new::thread_start::hf3104e647102288b at src/libstd/sys/unix/thread.rs:79 27: 0x7f19671aa4a4 - start_thread 28: 0x7f1966cd5d0f - __clone 29: 0x0 - <unknown> ```
Author
Owner

@blacknet76 commented on GitHub (Aug 30, 2019):

Can no one help?
Or can anyone give me a working docker-compose file to compare and check out?

<!-- gh-comment-id:526471324 --> @blacknet76 commented on GitHub (Aug 30, 2019): Can no one help? Or can anyone give me a working docker-compose file to compare and check out?
Author
Owner

@mprasil commented on GitHub (Aug 30, 2019):

Do you have any proxy in front of the bitwarden instance?

<!-- gh-comment-id:526527520 --> @mprasil commented on GitHub (Aug 30, 2019): Do you have any proxy in front of the bitwarden instance?
Author
Owner

@blacknet76 commented on GitHub (Aug 30, 2019):

@mprasil in my local test environment no, but I configure it on my production server and here I use traefik with the following labels

    labels:
      - "traefik.enable=true"
      - "traefik.backend=xxxxx"
      - "traefik.frontend.rule=Host:xxxx.${DOMAINNAME}"
      - "traefik.protocol=http"
      - "traefik.port=80"
      - "traefik.docker.network=traefik_proxy"
      - "traefik.frontend.headers.SSLRedirect=true"
      - "traefik.frontend.headers.STSSeconds=315360000"
      - "traefik.frontend.headers.browserXSSFilter=true"
      - "traefik.frontend.headers.contentTypeNosniff=true"
      - "traefik.frontend.headers.forceSTSHeader=true"
      - "traefik.frontend.headers.STSIncludeSubdomains=true"
      - "traefik.frontend.headers.STSPreload=true"
      - "traefik.frontend.headers.frameDeny=true"
<!-- gh-comment-id:526557731 --> @blacknet76 commented on GitHub (Aug 30, 2019): @mprasil in my local test environment no, but I configure it on my production server and here I use traefik with the following labels ``` labels: - "traefik.enable=true" - "traefik.backend=xxxxx" - "traefik.frontend.rule=Host:xxxx.${DOMAINNAME}" - "traefik.protocol=http" - "traefik.port=80" - "traefik.docker.network=traefik_proxy" - "traefik.frontend.headers.SSLRedirect=true" - "traefik.frontend.headers.STSSeconds=315360000" - "traefik.frontend.headers.browserXSSFilter=true" - "traefik.frontend.headers.contentTypeNosniff=true" - "traefik.frontend.headers.forceSTSHeader=true" - "traefik.frontend.headers.STSIncludeSubdomains=true" - "traefik.frontend.headers.STSPreload=true" - "traefik.frontend.headers.frameDeny=true" ```
Author
Owner

@mprasil commented on GitHub (Aug 30, 2019):

You might want to remove WEBSOCKET_ENABLED: "true". The websocket connection won't work without appropriately configured proxy and client will fail trying to access it. When that happens clients tend to misbehave in weird ways, this is why it's disabled by default. So as a first step to troubleshoot it, try to run the server without and see if you can log in.

<!-- gh-comment-id:526559225 --> @mprasil commented on GitHub (Aug 30, 2019): You might want to remove `WEBSOCKET_ENABLED: "true"`. The websocket connection won't work without appropriately configured proxy and client will fail trying to access it. When that happens clients tend to misbehave in weird ways, this is why it's disabled by default. So as a first step to troubleshoot it, try to run the server without and see if you can log in.
Author
Owner

@blacknet76 commented on GitHub (Aug 30, 2019):

No I can't login, same error and log entry as before

<!-- gh-comment-id:526572100 --> @blacknet76 commented on GitHub (Aug 30, 2019): No I can't login, same error and log entry as before
Author
Owner

@mprasil commented on GitHub (Aug 30, 2019):

Also to minimize the possible failure scenarios, can you try without DATABASE_URL? This will use local sqlite DB that will be gone once you restart the container, but that's good enough for test.

Also remove ENABLE_DB_WAL variable. It has no effect with MySQL and with sqlite the default is usually better option.

<!-- gh-comment-id:526581792 --> @mprasil commented on GitHub (Aug 30, 2019): Also to minimize the possible failure scenarios, can you try without `DATABASE_URL`? This will use local sqlite DB that will be gone once you restart the container, but that's good enough for test. Also remove `ENABLE_DB_WAL` variable. It has no effect with MySQL and with sqlite the default is usually better option.
Author
Owner

@blacknet76 commented on GitHub (Aug 30, 2019):

Same error as before, here now my config from docker.
I have also deactivate RUST_BACKTRACE but with the same result.
I have tesed with a windows 10, Linux and with my mobile phone with LTE to make sure that it is not a problem on my computer and/or network.
Are certain packages needed on the host machine?

version: "3.6"

networks:
  traefik_proxy:
    external:
      name: traefik_proxy
  internal:
    external: false
  default:
    driver: bridge

  bitwardenrs:
    container_name: bitwardenrs
    image: bitwardenrs/server:latest
#    image: bitwardenrs/server-mysql:latest
    restart: always
    depends_on:
#     - mariadb
     - traefik
    networks:
#     - internal
     - default
#    ports:
#      - 80:80
#      - 443:443
    volumes:
      - ${USERDIR}/.config/bwrs-data:/data
    environment:
      SIGNUPS_ALLOWED: "true" # set to false to disable signups
      SMTP_HOST: "smtp.gamil.com"
      SMTP_FROM: "xxxxxxxxx@gmail.com"
      SMTP_PORT: "465"
      SMTP_SSL: "true"
      SMTP_USERNAME: "xxxxxxxxx@gamil.com"
      SMTP_PASSWORD: "xxxxxxxx"
      LOG_FILE: "/data/bitwarden.log"
      RUST_BACKTRACE: "full"
#      DATABASE_URL: "mysql://bitwarden:xxxxxxx@mariadb/bitwarden"
      ADMIN_TOKEN: "xxxxxxxx"
#      ENABLE_DB_WAL: "false"
#    links:
#      - mariadb
    labels:
      - "traefik.enable=true"
      - "traefik.backend=xxxxxxxxxx"
      - "traefik.frontend.rule=Host:xxxxxxxxxx.${DOMAINNAME}"
      - "traefik.protocol=http"
      - "traefik.port=80"
      - "traefik.docker.network=traefik_proxy"
      - "traefik.frontend.headers.SSLRedirect=true"
      - "traefik.frontend.headers.STSSeconds=315360000"
      - "traefik.frontend.headers.browserXSSFilter=true"
      - "traefik.frontend.headers.contentTypeNosniff=true"
      - "traefik.frontend.headers.forceSTSHeader=true"
      - "traefik.frontend.headers.STSIncludeSubdomains=true"
      - "traefik.frontend.headers.STSPreload=true"
      - "traefik.frontend.headers.frameDeny=true"

docker logs

[2019-08-30 12:56:00][rocket::rocket][INFO] POST /api/accounts/prelogin application/json; charset=utf-8:
[2019-08-30 12:56:00][_][INFO] Matched: POST /api/accounts/prelogin (prelogin)
[2019-08-30 12:56:00][_][INFO] Outcome: Success
[2019-08-30 12:56:00][_][INFO] Response succeeded.
[2019-08-30 12:56:00][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8:
[2019-08-30 12:56:00][_][INFO] Matched: POST /identity/connect/token (login)
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Custom { kind: Other, error: "failed to lookup address information: Name or service not known" })', src/libcore/result.rs:1084:5

And here a screenshot from the ff console
Screenshot

<!-- gh-comment-id:526594094 --> @blacknet76 commented on GitHub (Aug 30, 2019): Same error as before, here now my config from docker. I have also deactivate RUST_BACKTRACE but with the same result. I have tesed with a windows 10, Linux and with my mobile phone with LTE to make sure that it is not a problem on my computer and/or network. Are certain packages needed on the host machine? ``` version: "3.6" networks: traefik_proxy: external: name: traefik_proxy internal: external: false default: driver: bridge bitwardenrs: container_name: bitwardenrs image: bitwardenrs/server:latest # image: bitwardenrs/server-mysql:latest restart: always depends_on: # - mariadb - traefik networks: # - internal - default # ports: # - 80:80 # - 443:443 volumes: - ${USERDIR}/.config/bwrs-data:/data environment: SIGNUPS_ALLOWED: "true" # set to false to disable signups SMTP_HOST: "smtp.gamil.com" SMTP_FROM: "xxxxxxxxx@gmail.com" SMTP_PORT: "465" SMTP_SSL: "true" SMTP_USERNAME: "xxxxxxxxx@gamil.com" SMTP_PASSWORD: "xxxxxxxx" LOG_FILE: "/data/bitwarden.log" RUST_BACKTRACE: "full" # DATABASE_URL: "mysql://bitwarden:xxxxxxx@mariadb/bitwarden" ADMIN_TOKEN: "xxxxxxxx" # ENABLE_DB_WAL: "false" # links: # - mariadb labels: - "traefik.enable=true" - "traefik.backend=xxxxxxxxxx" - "traefik.frontend.rule=Host:xxxxxxxxxx.${DOMAINNAME}" - "traefik.protocol=http" - "traefik.port=80" - "traefik.docker.network=traefik_proxy" - "traefik.frontend.headers.SSLRedirect=true" - "traefik.frontend.headers.STSSeconds=315360000" - "traefik.frontend.headers.browserXSSFilter=true" - "traefik.frontend.headers.contentTypeNosniff=true" - "traefik.frontend.headers.forceSTSHeader=true" - "traefik.frontend.headers.STSIncludeSubdomains=true" - "traefik.frontend.headers.STSPreload=true" - "traefik.frontend.headers.frameDeny=true" ``` docker logs ``` [2019-08-30 12:56:00][rocket::rocket][INFO] POST /api/accounts/prelogin application/json; charset=utf-8: [2019-08-30 12:56:00][_][INFO] Matched: POST /api/accounts/prelogin (prelogin) [2019-08-30 12:56:00][_][INFO] Outcome: Success [2019-08-30 12:56:00][_][INFO] Response succeeded. [2019-08-30 12:56:00][rocket::rocket][INFO] POST /identity/connect/token application/x-www-form-urlencoded; charset=utf-8: [2019-08-30 12:56:00][_][INFO] Matched: POST /identity/connect/token (login) thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Io(Custom { kind: Other, error: "failed to lookup address information: Name or service not known" })', src/libcore/result.rs:1084:5 ``` And here a screenshot from the ff console [Screenshot](https://imgur.com/XBzrXNA)
Author
Owner

@mprasil commented on GitHub (Aug 30, 2019):

Okay this is really shooting in the dark, but I've noticed you have typo in the SMTP_HOST (gamil instead of gmail) and the error logged says failed to lookup address information: Name or service not known. Could that be it?

Edit: same for SMTP_USERNAME

<!-- gh-comment-id:526599798 --> @mprasil commented on GitHub (Aug 30, 2019): Okay this is really shooting in the dark, but I've noticed you have typo in the `SMTP_HOST` (`gamil` instead of `gmail`) and the error logged says `failed to lookup address information: Name or service not known`. Could that be it? Edit: same for `SMTP_USERNAME`
Author
Owner

@blacknet76 commented on GitHub (Aug 30, 2019):

Thanks for the hint to the typo error.
I checked the admin page and changed all settings copy/paste. And now it works like a charm.
I think I have here also a typo error. Thanks for your support.

<!-- gh-comment-id:526608202 --> @blacknet76 commented on GitHub (Aug 30, 2019): Thanks for the hint to the typo error. I checked the admin page and changed all settings copy/paste. And now it works like a charm. I think I have here also a typo error. Thanks for your support.
Author
Owner

@mprasil commented on GitHub (Aug 30, 2019):

Glad you figured that out!

<!-- gh-comment-id:526618732 --> @mprasil commented on GitHub (Aug 30, 2019): Glad you figured that out!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vaultwarden#380
No description provided.