Valtwarden Kontoanmeldung schlägt fehl

[dargon]

Den Cache und Verlauf des Browser habe ich eben nochmal gelöscht. Einen anderen Browser hatte ich auch schon ausprobiert. Hat beides nicht funktioniert.

 

[dargon]

Es hat jetzt geklappt, habe noch einmal alles durch gestartet (NAS, Router, PC)

 

[LORDNIKON1]

Hallo zusammen, auch bei mir gibt es leider Probleme. Ich hatte in der Vergangenheit einen Bitwarden Container, den ich über Portainer habe updaten wollen. Danach ließ er sich leider nicht mehr starten. Zum Glück konnte ich aus der App heraus noch den Tresor mit den Passwörtern exportieren, so dass jetzt nicht alles weg ist.

Bei der Neuinstallation kann ich aber nun beim Erstzugriff kein Admin Account anlegen. Habe auch anhand der Anleitung von Marius gearbeitet (diese hier: https://mariushosting.com/how-to-install-bitwarden-on-your-synology-nas/), läuft alles durch. Stack wird erfolgreich deployed, dann komme ich beim Aufruf meiner (Sub-) Domain zum Anmeldescreen - da denkt man ja, alles ist gut. Wenn ich dann aber versuche den Admin User anzulegen bekomme ich nur das hier zu sehen:



Ich habe den Verdacht, dass das mit SMTP zu tun hat, kann es aber nicht greifen. Im Stack Editor habe ich genau so gearbeitet wie Marius es beschrieben hat - leider ohne Erfolg.

Mir ist schon klar, dass das "App Passwort" nicht das Passwort zum Account ist (das ist oben glaube ich einmal verwechselt worden), sondern das von GMail für SMTP vergebene App-Passwort, das ich zuvor angelegt habe.

Was die Einstellung "zulassen von Nutzerregistrierungen" anbetrifft: Im Stack Editor sehe ich in Zeile 42 den Eintrag "- globalSettings__disableUserRegistration=false". Das bezieht sich nach meinem Verständnis aber auch nicht auf die Anlage des Admin Users, sondern weiterer Unser.

Hat irgendwer eine Idee?

 

[plang.pl]

Container Logs mal gecheckt?

 

[LORDNIKON1]

Bin Docker Container mäßig leider nicht sehr bewandert. Wüsste noch nicht einmal wo ich die Logs dort fände. In Portainer gibt es "Authentication logs". Ist das damit gemeint? Scheint jedenfalls Gegenstand der "Business Edition" zu sein.

 

[LORDNIKON1]

Habe bei Github das hier gefunden: https://github.com/bitwarden/server/issues/121

Ich habe die beiden Container beim Neuversuch komplett gelöscht und auch die dazugehörigen Images. Können sonst noch irgendwo Bestandteile rumfliegen, die die Neuinstallation beeinflussen?

 

[LORDNIKON1]

OK. Ich habe jetzt sicher zum 10ten Mal die Container wieder platt gemacht und alles komplett neu aufgesetzt - einschließlich neuer IDs von Bitwarden. Jetzt reicht es mir langsam. Ich komme nicht weiter.

 

[plang.pl]

In Portainer den Container anklicken und auf "Logs" dürcken

 

[LORDNIKON1]

Ah ok. Also beim Hauptcontainer (nicht dem DB Container findet sich da das nachstehende)

2023-02-10 09:32:46,828 INFO success: nginx entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:32:46,828 INFO success: notifications entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:32:57,966 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:32:58,969 INFO spawned: 'admin' with pid 151
2023-02-10 09:33:14,629 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:33:23,920 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:33:24,923 INFO spawned: 'admin' with pid 185
2023-02-10 09:33:39,945 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:33:51,792 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:33:52,795 INFO spawned: 'admin' with pid 221
2023-02-10 09:34:07,815 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:34:17,759 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:34:18,762 INFO spawned: 'admin' with pid 253
2023-02-10 09:34:33,785 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:34:43,722 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:34:44,725 INFO spawned: 'admin' with pid 284
2023-02-10 09:34:59,746 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:35:06,366 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:35:07,369 INFO spawned: 'admin' with pid 314
2023-02-10 09:35:22,388 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:35:32,036 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:35:33,039 INFO spawned: 'admin' with pid 348
2023-02-10 09:35:48,064 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:35:57,000 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:35:58,003 INFO spawned: 'admin' with pid 370
2023-02-10 09:36:13,025 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:36:22,955 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:36:23,959 INFO spawned: 'admin' with pid 400
2023-02-10 09:36:38,981 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:36:47,890 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:36:48,893 INFO spawned: 'admin' with pid 430
2023-02-10 09:37:03,917 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:37:12,855 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:37:13,858 INFO spawned: 'admin' with pid 460
2023-02-10 09:37:28,878 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:37:37,846 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:37:38,848 INFO spawned: 'admin' with pid 493
2023-02-10 09:37:53,867 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:38:03,843 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:38:04,845 INFO spawned: 'admin' with pid 523
2023-02-10 09:38:19,869 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:38:29,909 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:38:30,912 INFO spawned: 'admin' with pid 543
2023-02-10 09:38:45,936 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:38:55,896 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:38:56,899 INFO spawned: 'admin' with pid 574
2023-02-10 09:39:11,920 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:39:20,836 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:39:21,839 INFO spawned: 'admin' with pid 605
2023-02-10 09:39:36,860 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:39:45,814 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:39:46,818 INFO spawned: 'admin' with pid 634
2023-02-10 09:40:01,836 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:40:08,454 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:40:09,457 INFO spawned: 'admin' with pid 666
2023-02-10 09:40:24,477 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:40:33,448 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:40:34,451 INFO spawned: 'admin' with pid 689
2023-02-10 09:40:49,472 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:40:59,412 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:41:00,415 INFO spawned: 'admin' with pid 717
2023-02-10 09:41:15,435 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:41:24,474 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:41:25,477 INFO spawned: 'admin' with pid 748
2023-02-10 09:41:40,501 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:41:50,461 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:41:51,465 INFO spawned: 'admin' with pid 777
2023-02-10 09:42:06,485 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:42:16,414 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:42:17,416 INFO spawned: 'admin' with pid 806
2023-02-10 09:42:32,438 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:42:41,373 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:42:42,376 INFO spawned: 'admin' with pid 836
2023-02-10 09:42:57,396 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:43:06,321 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:43:07,324 INFO spawned: 'admin' with pid 857
2023-02-10 09:43:22,343 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:43:31,263 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:43:32,265 INFO spawned: 'admin' with pid 887
2023-02-10 09:43:47,283 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:43:57,266 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:43:58,268 INFO spawned: 'admin' with pid 916
2023-02-10 09:44:13,291 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:44:22,229 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:44:23,232 INFO spawned: 'admin' with pid 944
2023-02-10 09:44:38,253 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:44:47,196 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:44:48,198 INFO spawned: 'admin' with pid 975
2023-02-10 09:45:03,218 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:45:09,904 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:45:10,906 INFO spawned: 'admin' with pid 997
2023-02-10 09:45:25,925 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:45:34,927 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:45:35,930 INFO spawned: 'admin' with pid 1029
2023-02-10 09:45:50,949 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:45:59,918 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:46:00,921 INFO spawned: 'admin' with pid 1060
2023-02-10 09:46:15,943 INFO success: admin entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
2023-02-10 09:46:25,933 INFO exited: admin (terminated by SIGSEGV (core dumped); not expected)
2023-02-10 09:46:26,937 INFO spawned: 'admin' with pid 1090

 

[LORDNIKON1]

Und für den DB Container das nachstehende (liest sich nicht wirklich gut, ohne den genauen Inhalt zu verstehen)

2023-02-10 10:31:52 0 [Note] mariadbd: Shutdown complete
2023-02-10 10:32:05+01:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.10.3+maria~ubu2204 started.
2023-02-10 10:32:05+01:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2023-02-10 10:32:05+01:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.10.3+maria~ubu2204 started.
2023-02-10 10:32:05+01:00 [Note] [Entrypoint]: MariaDB upgrade not required
2023-02-10 10:32:05 0 [Note] Starting MariaDB 10.10.3-MariaDB-1:10.10.3+maria~ubu2204 source revision cc8b9bcee3ce88bc52147948f96765cd5009b88a as process 1
2023-02-10 10:32:05 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-02-10 10:32:05 0 [Note] InnoDB: Number of transaction pools: 1
2023-02-10 10:32:05 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-02-10 10:32:05 0 [Warning] mariadbd: io_uring_queue_init() failed with ENOSYS: check seccomp filters, and the kernel version (newer than 5.1 required)
2023-02-10 10:32:05 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
2023-02-10 10:32:05 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2023-02-10 10:32:05 0 [Note] InnoDB: Completed initialization of buffer pool
2023-02-10 10:32:06 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2023-02-10 10:32:07 0 [Note] InnoDB: 128 rollback segments are active.
2023-02-10 10:32:07 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2023-02-10 10:32:07 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2023-02-10 10:32:07 0 [Note] InnoDB: log sequence number 258539; transaction id 193
2023-02-10 10:32:07 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2023-02-10 10:32:07 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-02-10 10:32:07 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
2023-02-10 10:32:07 0 [Note] Server socket created on IP: '0.0.0.0'.
2023-02-10 10:32:07 0 [Note] Server socket created on IP: '::'.
2023-02-10 10:32:07 0 [Note] mariadbd: ready for connections.
Version: '10.10.3-MariaDB-1:10.10.3+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution
2023-02-10 10:32:07 0 [Note] InnoDB: Buffer pool(s) load completed at 230210 10:32:07
2023-02-10 10:32:16 3 [Warning] Aborted connection 3 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:32:16 5 [Warning] Aborted connection 5 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:32:56 8 [Warning] Aborted connection 8 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:32:56 10 [Warning] Aborted connection 10 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:33:22 15 [Warning] Aborted connection 15 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:33:22 17 [Warning] Aborted connection 17 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:33:50 22 [Warning] Aborted connection 22 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:33:50 20 [Warning] Aborted connection 20 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:34:16 27 [Warning] Aborted connection 27 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:34:16 25 [Warning] Aborted connection 25 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:34:42 32 [Warning] Aborted connection 32 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:34:42 30 [Warning] Aborted connection 30 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:35:06 35 [Warning] Aborted connection 35 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:35:06 34 [Warning] Aborted connection 34 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:35:32 39 [Warning] Aborted connection 39 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:35:32 41 [Warning] Aborted connection 41 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:35:56 46 [Warning] Aborted connection 46 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:35:56 44 [Warning] Aborted connection 44 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:36:21 51 [Warning] Aborted connection 51 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:36:21 49 [Warning] Aborted connection 49 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:36:47 54 [Warning] Aborted connection 54 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:36:47 56 [Warning] Aborted connection 56 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:37:12 58 [Warning] Aborted connection 58 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:37:12 61 [Warning] Aborted connection 61 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:37:37 65 [Warning] Aborted connection 65 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:37:37 63 [Warning] Aborted connection 63 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:38:02 68 [Warning] Aborted connection 68 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:38:02 70 [Warning] Aborted connection 70 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:38:28 73 [Warning] Aborted connection 73 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:38:28 75 [Warning] Aborted connection 75 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:38:54 78 [Warning] Aborted connection 78 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:38:54 80 [Warning] Aborted connection 80 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:39:20 83 [Warning] Aborted connection 83 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:39:20 85 [Warning] Aborted connection 85 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:39:45 90 [Warning] Aborted connection 90 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:39:45 87 [Warning] Aborted connection 87 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:40:08 92 [Warning] Aborted connection 92 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:40:08 93 [Warning] Aborted connection 93 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:40:33 97 [Warning] Aborted connection 97 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:40:33 99 [Warning] Aborted connection 99 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:40:58 102 [Warning] Aborted connection 102 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:40:58 104 [Warning] Aborted connection 104 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:41:24 109 [Warning] Aborted connection 109 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:41:24 107 [Warning] Aborted connection 107 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:41:49 114 [Warning] Aborted connection 114 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:41:49 111 [Warning] Aborted connection 111 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:42:15 116 [Warning] Aborted connection 116 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:42:15 118 [Warning] Aborted connection 118 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:42:41 121 [Warning] Aborted connection 121 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:42:41 123 [Warning] Aborted connection 123 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:43:06 126 [Warning] Aborted connection 126 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:43:06 128 [Warning] Aborted connection 128 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:43:31 131 [Warning] Aborted connection 131 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:43:31 133 [Warning] Aborted connection 133 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:43:56 138 [Warning] Aborted connection 138 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:43:56 136 [Warning] Aborted connection 136 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:44:22 140 [Warning] Aborted connection 140 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:44:22 143 [Warning] Aborted connection 143 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:44:47 145 [Warning] Aborted connection 145 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:44:47 147 [Warning] Aborted connection 147 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:45:09 152 [Warning] Aborted connection 152 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:45:09 150 [Warning] Aborted connection 150 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:45:09 151 [Warning] Aborted connection 151 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:45:34 158 [Warning] Aborted connection 158 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:45:34 156 [Warning] Aborted connection 156 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:45:59 161 [Warning] Aborted connection 161 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:45:59 163 [Warning] Aborted connection 163 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:46:24 167 [Warning] Aborted connection 167 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:46:24 165 [Warning] Aborted connection 165 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:46:50 170 [Warning] Aborted connection 170 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:46:50 172 [Warning] Aborted connection 172 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:47:15 175 [Warning] Aborted connection 175 to db: 'unconnected' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)
2023-02-10 10:47:15 177 [Warning] Aborted connection 177 to db: 'bitwarden_vault' user: 'bitwardenuser' host: '172.27.0.3' (Got an error reading communication packets)

 

[EDvonSchleck]

Bitwarden ist nicht Vaultwarden! Nute doch lieber Vautwarden. Der Server ist keiner und performanter und war schon immer die bessere Alternative zum Bitwarden Server!

 

[plang.pl]

Dem kann ich mich anschließen.
Vaultwarden ist die bessere Alternative!

 

[LORDNIKON1]

Mit Vaultwarden kann ich die Bitwarden Apps aber trotzdem nutzen, oder?

 

[LORDNIKON1]

... interessieren würde mich aber natürlich trotzdem wo der Hase im Pfeffer liegt bei meiner Bitwarden Installation.

 

[plang.pl]

Mit Vaultwarden kann ich die Bitwarden Apps aber trotzdem nutzen, oder?

Ja.
Nutze "vaultwarden/server:latest"

 

[EDvonSchleck]

... interessieren würde mich aber natürlich trotzdem wo der Hase im Pfeffer liegt bei meiner Bitwarden Installation.

Steht doch da: eine abgebrochene Verbindung zur Datenbank. Für Vaultwarden kannst du einfach SQLite (System) nehmen und musst keine weitere Datenbank laufen lassen. Dazu wirst du noch eine falsche Config haben: https://github.com/bitwarden/server/issues/2493

Für mich ist es sowie nicht verständlich: Nachdem Bitwarden 100 Millionen $ von Investoren eingesammelt haben, warum sie nicht Vaultwarden (ehemals Bitwarden RS) eingekauft(/aufgekauft haben und immer noch mit ihrer unfertigen Variante spielen. Dann hätten sie nur noch die Neuerungen einpflegen müssen. Andy Garcia macht eine super Arbeit!

 

[alexhell]

Dann hätten sie nur noch die Neuerungen einpflegen müssen.

"Nur noch"..... Das wäre alles neu machen. Die setzen doch auf komplett unterschiedliche Sprachen (Rust und C#). Und Vaultwarden fehlen wahrscheinlich auch alle Enterprise Features von Bitwarden. Da wäre die Freude bestimmt sehr groß bei den Kunden. Ich will Vaultwarden nicht schlecht machen, aber man sollte auch nicht Bitwarden schlechter machen als es ist. Ohne Bitwarden gäbe es kein Vaultwarden.

 

[EDvonSchleck]

Welche Features fehlen denn genau? Sie fangen jetzt wieder fast von vorne an. Es ist doch einfacher auf etwas bestehend aufzubauen, als neu zu machen. Das Bitwarden noch an #C festhalten. Wobei es etwas Besseres gibt, was auch noch Open Source ist, verstehe ich nicht. Fraglich wäre auch, ob das Seif-Hosten, mit bis zu 10 Container und deutlich höhere Last, Bitwarden auch so populär geworden wäre. Was zu kompliziert ist, egal wie gut es ist, wird aber oft vom Markt nicht angenommen. Passwortmanager gibt es genug.

 

[alexhell]

Welche Features fehlen denn genau?

Mir keine, aber ich bin auch kein Enterprise Kunden. Denen könnte einiges fehlen.

Gerade sowas wie eigene Rollen, SCIM, SSO und Richtlinien würde mir schon fehlen. Daher ist Vaultwarden für diese Kunden keine Alternative....

Es ist doch einfacher auf etwas bestehend aufzubauen, als neu zu machen. Das Bitwarden noch an #C festhalten. Wobei es etwas Besseres gibt, was auch noch Open Source ist, verstehe ich nicht.

Nein....Das kann es unter Umständen eher viel komplizierter machen als ein grüne Wiese Projekt. Und was spricht gegen C#? Ich bin kein C# Entwickler, aber was wäre den eine alternative und wieso wäre diese besser? Nur weil man selber eine Sprache besser findet ist für mich kein Argument. Jede Sprache hat ihre Vor- und Nachteile.

Bitwarden auch so populär geworden wäre

Und Vaultwarden wäre nie so beliebt geworden ohne die Apps/Extentsion von Bitwarden. Es werden schon beide ihre Daseinsberechtigung haben.

 

[LORDNIKON1]

... um ehrlich zu sein fällt mir gerade auf, dass ich auch vorher wohl vaultwarden installiert hatte und nicht bitwarden. Das läuft jetzt jedenfalls sauber. Danke für den Hinweis.