Originally created by @jonathanmmm on GitHub (Oct 5, 2021).
Hi,
I am using vaultwarden/server:latest (updated today from bitwardenrs/server:latest, didn't work there either, sadly in my service file there was still the wrong image pulled and so).
Originally created by @jonathanmmm on GitHub (Oct 5, 2021).
Hi,
I am using vaultwarden/server:latest (updated today from bitwardenrs/server:latest, didn't work there either, sadly in my service file there was still the wrong image pulled and so).
If I go on the admin page first the token field is half behind the top nav bar.
Second if I am logged in and I press "Remove all 2FA" from a user, the following happens:
https://bitwarden.my-domain.com/admin/users/overview
changes to
https://bitwarden.my-domain.com/admin/users/overview#
and it autoscrolls to the top.
Still 2FA is displayed, even if I switch menus or log in from a different browser.
It works for me locally at least.
What browser are you using, and do you have any extensions which block javascript or part of it?
Also are you accessing it via HTTP or HTTPS.
Are you using a reverse proxy? If so, does it do caching? If so, try to clear the cache, or restart the reverse proxy.
If you Press F12 to open the developer console of the browser, and then reload the page, and click the delete again, do you see any error's appear?
@BlackDex commented on GitHub (Oct 6, 2021):
It works for me locally at least.
What browser are you using, and do you have any extensions which block javascript or part of it?
Also are you accessing it via HTTP or HTTPS.
Are you using a reverse proxy? If so, does it do caching? If so, try to clear the cache, or restart the reverse proxy.
If you Press F12 to open the developer console of the browser, and then reload the page, and click the delete again, do you see any error's appear?
If I access port 90 directly it works flawlessly (forgot about that, that is what I normally used before), couldn't find any "caching" enabled, gzip is off.
@jonathanmmm commented on GitHub (Oct 8, 2021):
I am having it behind a proxy (nginx):
```
location /admin {
allow 127.0.0.1;
allow 10.6.0.0/24;
deny all;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://127.0.0.1:90;
}
```
If I access port 90 directly it works flawlessly (forgot about that, that is what I normally used before), couldn't find any "caching" enabled, gzip is off.
It is there behind https (if it matters), just in the normal proxy settings for vaultwarden (which works normal)
@jonathanmmm commented on GitHub (Oct 8, 2021):
It is there behind https (if it matters), just in the normal proxy settings for vaultwarden (which works normal)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @jonathanmmm on GitHub (Oct 5, 2021).
Hi,
I am using vaultwarden/server:latest (updated today from bitwardenrs/server:latest, didn't work there either, sadly in my service file there was still the wrong image pulled and so).
If I go on the admin page first the token field is half behind the top nav bar.
Second if I am logged in and I press "Remove all 2FA" from a user, the following happens:
https://bitwarden.my-domain.com/admin/users/overview
changes to
https://bitwarden.my-domain.com/admin/users/overview#
and it autoscrolls to the top.
Still 2FA is displayed, even if I switch menus or log in from a different browser.
@BlackDex commented on GitHub (Oct 6, 2021):
It works for me locally at least.
What browser are you using, and do you have any extensions which block javascript or part of it?
Also are you accessing it via HTTP or HTTPS.
Are you using a reverse proxy? If so, does it do caching? If so, try to clear the cache, or restart the reverse proxy.
If you Press F12 to open the developer console of the browser, and then reload the page, and click the delete again, do you see any error's appear?
@jonathanmmm commented on GitHub (Oct 8, 2021):
I am having it behind a proxy (nginx):
If I access port 90 directly it works flawlessly (forgot about that, that is what I normally used before), couldn't find any "caching" enabled, gzip is off.
@jonathanmmm commented on GitHub (Oct 8, 2021):
It is there behind https (if it matters), just in the normal proxy settings for vaultwarden (which works normal)
@BlackDex commented on GitHub (Oct 8, 2021):
Well, try F12 when you access it through the proxy, because it seems to be blocking something.