Originally created by @toobie83 on GitHub (Apr 26, 2021).
Hi there,
I was able to create a new account on my bitwarden server, even as the signups_allowed flag is set to false.
a) Is this known? or just me?
b) is there a way to look into the database if there exists any new/unknown accounts which are not mine?
Originally created by @toobie83 on GitHub (Apr 26, 2021).
Hi there,
I was able to create a new account on my bitwarden server, even as the signups_allowed flag is set to false.
a) Is this known? or just me?
b) is there a way to look into the database if there exists any new/unknown accounts which are not mine?

Could you post a support string which you can generate via /admin/diagnostics please?
Also, via /admin you are able to see the users which are on your server.
@BlackDex commented on GitHub (Apr 26, 2021):
Could you post a support string which you can generate via /admin/diagnostics please?
Also, via /admin you are able to see the users which are on your server.
Could you post a support string which you can generate via /admin/diagnostics please?
Also, via /admin you are able to see the users which are on your server.
Ok, looks like it shouldn't be possible.
We're you just able to create a new account right from the main page?
And what happens if you try it again? With a different email?
@BlackDex commented on GitHub (Apr 26, 2021):
Ok, looks like it shouldn't be possible.
We're you just able to create a new account right from the main page?
And what happens if you try it again? With a different email?
Ok, looks like it shouldn't be possible.
We're you just able to create a new account right from the main page?
And what happens if you try it again? With a different email?
The point I noticed this, I was able to create a new account on the main page and I was also able to login into this account after that. Of course different email than my normale one.
@toobie83 commented on GitHub (Apr 26, 2021):
> Ok, looks like it shouldn't be possible.
> We're you just able to create a new account right from the main page?
> And what happens if you try it again? With a different email?
The point I noticed this, I was able to create a new account on the main page and I was also able to login into this account after that. Of course different email than my normale one.
The only change I made was to enable the admin panel. Dont know why it is now restricted as it should be.
@toobie83 commented on GitHub (Apr 26, 2021):
Tried it now with a different email address:

The only change I made was to enable the admin panel. Dont know why it is now restricted as it should be.
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 @toobie83 on GitHub (Apr 26, 2021).
Hi there,
I was able to create a new account on my bitwarden server, even as the signups_allowed flag is set to false.
a) Is this known? or just me?
b) is there a way to look into the database if there exists any new/unknown accounts which are not mine?
@BlackDex commented on GitHub (Apr 26, 2021):
Could you post a support string which you can generate via /admin/diagnostics please?
Also, via /admin you are able to see the users which are on your server.
@toobie83 commented on GitHub (Apr 26, 2021):
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Didnt know that a admin panel exists, thx for suggesting :)
@BlackDex commented on GitHub (Apr 26, 2021):
Ok, looks like it shouldn't be possible.
We're you just able to create a new account right from the main page?
And what happens if you try it again? With a different email?
@toobie83 commented on GitHub (Apr 26, 2021):
The point I noticed this, I was able to create a new account on the main page and I was also able to login into this account after that. Of course different email than my normale one.
@toobie83 commented on GitHub (Apr 26, 2021):
Tried it now with a different email address:

The only change I made was to enable the admin panel. Dont know why it is now restricted as it should be.
@BlackDex commented on GitHub (Apr 26, 2021):
I think because the previous time the container didn't restart. Which then didn't disabled it.