Masterpassword not accepted

Hi,
I am Selfhosting a Bitwarden installation and since yesterday I am facing the issue that I can not login to my Vault with Username and Password. I tried app, webinterface and Browserextension.
I saw a couple of post already asking always if Username+PW are correctly used and I can confirm that I am using the correct Username and PW, because if I am using a Browserextension which was once succesfully logged in, I can use Username and PW, but if I am using Desktop App, Android App, WebVault etc. which never were logged in or were I closed the session I can not relog again.
I rebootet my server, restored a backup taken 4 days ago, nothing seems to work.
Yes I am using correct Username+PW, typed and copied it into the password field, yes password copied and pasted into Browserextension where I did not close the session still work with that PW.
Restarting of Docker containers is working fine.

Havent updated the environment the last 3 weeks, so there should be no changes to my knowledge.

Restore a backup?

To be more specific about the ‘restored a backup taken 4 days ago’ it was a VM backup, so the entire VM has been restored yesterday.

Hi there,
could solve the issue.
Seemed to be a DNS issue, because of a 2MFA Setup with Duo.
Bitwarden host has a DNS issue as described here:

Could not fix the issue with systemd-resolved so I stopped the service as described here:
https://wiki.ubuntuusers.de/systemd/systemd-resolved/
and followed through:
Stopp systemd-resolved, modify the /etc/resolv.conf and add GoogleDNS and afterwards:

  1. Open config file sudo nano /etc/resolv.conf and add the following under existing nameservers

nameserver 8.8.8.8

nameserver 8.8.4.4

  1. run following commands to restart daemon and docker service

sudo systemctl daemon-reload

sudo systemctl restart docker

Now I updated OS and Bitwarden to the latest available version.
And I am able to login. I am assuming issue will be back as soon as I do a reboot.

Working with the service provider for the Linux container on a more permanent solution.
Because of the DNS not properly working the DUO MFA did not work.