Hi,
I have created various users while SMTP didn't work (I suppose that might be the issue).
There was an error when creating the user (timeout etc.) relatec to the mails that couldn't be delivered.
But the users are created anyways it seems as I get the error "user already exists - this user is already a member of the organization" when I try to create them again. The thing is that I cannot find them anywhere, they are not shown in the users list for my one organization.
After fixingt the mailserver config the users that are being created receive their mail and are also visible within the users section, but there are just a few I cannot see and cannot recreate and cannot reset the password for (because there it says "A user with that email does not exist")
Seems like a bug!
Originally created by @cyrrelsneer on GitHub (Jun 13, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/905
Originally assigned to: @miloschwartz on GitHub.
Hi,
I have created various users while SMTP didn't work (I suppose that might be the issue).
There was an error when creating the user (timeout etc.) relatec to the mails that couldn't be delivered.
But the users are created anyways it seems as I get the error "user already exists - this user is already a member of the organization" when I try to create them again. The thing is that I cannot find them anywhere, they are not shown in the users list for my one organization.
After fixingt the mailserver config the users that are being created receive their mail and are also visible within the users section, but there are just a few I cannot see and cannot recreate and cannot reset the password for (because there it says "A user with that email does not exist")
Seems like a bug!
@oschwartz10612 commented on GitHub (Jun 13, 2025):
Hi! This might be expected behavior but maybe not ideal. Could you check if you see the users in the server admin > all users page and if so delete them from there? It would be at /admin/users
<!-- gh-comment-id:2970382729 -->
@oschwartz10612 commented on GitHub (Jun 13, 2025):
Hi! This might be expected behavior but maybe not ideal. Could you check if you see the users in the `server admin > all users` page and if so delete them from there? It would be at `/admin/users`
Hi,
I currently have 1 admin and 1 working user and 3 or 4 invisible users (just to make sure that you understand what could one expect to see).
On that specific page I can only see one user (not my admin) account, but not the 3 or 4 that I have created without the working mail account
<!-- gh-comment-id:2970443124 -->
@cyrrelsneer commented on GitHub (Jun 13, 2025):
Hi,
I currently have 1 admin and 1 working user and 3 or 4 invisible users (just to make sure that you understand what could one expect to see).
On that specific page I can only see one user (not my admin) account, but not the 3 or 4 that I have created without the working mail account
@oschwartz10612 commented on GitHub (Jun 13, 2025):
Okay sounds like a bug then. Thanks for letting us know. We will look into it - my guess is we just need to handle the reset of the user setup process correctly if the email part fails.
In regards to how to resolve this right now unfortunately there are two not great options:
reset your config by deleting the config/db/db.sqlite file and set stuff back up if needed.
Download and use a sqlite editor tool (like dbever) to edit the db and remove the users from all of the reference tables and then put the db back.
Let me know if you need any further pointers on that!
<!-- gh-comment-id:2970458502 -->
@oschwartz10612 commented on GitHub (Jun 13, 2025):
Okay sounds like a bug then. Thanks for letting us know. We will look into it - my guess is we just need to handle the reset of the user setup process correctly if the email part fails.
In regards to how to resolve this right now unfortunately there are two not great options:
- reset your config by deleting the config/db/db.sqlite file and set stuff back up if needed.
- Download and use a sqlite editor tool (like dbever) to edit the db and remove the users from all of the reference tables and then put the db back.
Let me know if you need any further pointers on that!
hey, thanks for the response.
There is no real impact for me as they were mail adresses from my own domain and I was tinkering around before setting the real user up.
Just for the sake of a clean database I will not do that, but I cross my fingers you'll maybe find the bug and I can see the users in a later version ;-)
If you need anything else I can surely give logs or whatever is needed.
Thanks for your great work!
<!-- gh-comment-id:2970472892 -->
@cyrrelsneer commented on GitHub (Jun 13, 2025):
hey, thanks for the response.
There is no real impact for me as they were mail adresses from my own domain and I was tinkering around before setting the real user up.
Just for the sake of a clean database I will not do that, but I cross my fingers you'll maybe find the bug and I can see the users in a later version ;-)
If you need anything else I can surely give logs or whatever is needed.
Thanks for your great work!
Okay sounds like a bug then. Thanks for letting us know. We will look into it - my guess is we just need to handle the reset of the user setup process correctly if the email part fails.
In regards to how to resolve this right now unfortunately there are two not great options:
reset your config by deleting the config/db/db.sqlite file and set stuff back up if needed.
Download and use a sqlite editor tool (like dbever) to edit the db and remove the users from all of the reference tables and then put the db back.
Let me know if you need any further pointers on that!
Hi, and thanks for your work too. I ran also into that issue just forgetting to put the smtp secure option in config. And thinking that default example with host, port, user and pass is enough. Of course when I tried to add users I got timeout 10000 failure to add, but the user email was added in database and disallowed me to add again the same username/email. I really need this, and I think that such an error must be treated somehow in the app. For example by not writing in db in case of any error, or if it is necessary deleting the row in case of error/failure to send. To manually edit the db for such is not a good option at all. Also, in my case there are a lot of resources defined :) and it will be a pain to reset-up all. Please give me another solution. Maybe a clean option to delete all users that are not confirmed. Or show all users in user section even if they are confirmed or not... This option will be best, as in case of many invites we can see if we invited someone and not confirmed, or failed to invite or such other things.
<!-- gh-comment-id:2989091863 -->
@SirAry commented on GitHub (Jun 19, 2025):
> Okay sounds like a bug then. Thanks for letting us know. We will look into it - my guess is we just need to handle the reset of the user setup process correctly if the email part fails.
>
> In regards to how to resolve this right now unfortunately there are two not great options:
>
> * reset your config by deleting the config/db/db.sqlite file and set stuff back up if needed.
> * Download and use a sqlite editor tool (like dbever) to edit the db and remove the users from all of the reference tables and then put the db back.
>
> Let me know if you need any further pointers on that!
Hi, and thanks for your work too. I ran also into that issue just forgetting to put the smtp secure option in config. And thinking that default example with host, port, user and pass is enough. Of course when I tried to add users I got timeout 10000 failure to add, but the user email was added in database and disallowed me to add again the same username/email. I really need this, and I think that such an error must be treated somehow in the app. For example by not writing in db in case of any error, or if it is necessary deleting the row in case of error/failure to send. To manually edit the db for such is not a good option at all. Also, in my case there are a lot of resources defined :) and it will be a pain to reset-up all. Please give me another solution. Maybe a clean option to delete all users that are not confirmed. Or show all users in user section even if they are confirmed or not... This option will be best, as in case of many invites we can see if we invited someone and not confirmed, or failed to invite or such other things.
@oschwartz10612 commented on GitHub (Jun 22, 2025):
@SirAry we will work on a better way to prevent this and to clean bad users out of the system with a cli tool or something but I think your best bet right now if you want to keep your config is to use a basic sqlite editor like Dbever and remove the users. I am sorry its not super easy or simple to do. You could delete the users from the users table and then reupload the db.
<!-- gh-comment-id:2994271898 -->
@oschwartz10612 commented on GitHub (Jun 22, 2025):
@SirAry we will work on a better way to prevent this and to clean bad users out of the system with a cli tool or something but I think your best bet right now if you want to keep your config is to use a basic sqlite editor like Dbever and remove the users. I am sorry its not super easy or simple to do. You could delete the users from the users table and then reupload the db.
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 @cyrrelsneer on GitHub (Jun 13, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/905
Originally assigned to: @miloschwartz on GitHub.
Hi,
I have created various users while SMTP didn't work (I suppose that might be the issue).
There was an error when creating the user (timeout etc.) relatec to the mails that couldn't be delivered.
But the users are created anyways it seems as I get the error "user already exists - this user is already a member of the organization" when I try to create them again. The thing is that I cannot find them anywhere, they are not shown in the users list for my one organization.
After fixingt the mailserver config the users that are being created receive their mail and are also visible within the users section, but there are just a few I cannot see and cannot recreate and cannot reset the password for (because there it says "A user with that email does not exist")
Seems like a bug!
@oschwartz10612 commented on GitHub (Jun 13, 2025):
Hi! This might be expected behavior but maybe not ideal. Could you check if you see the users in the
server admin > all userspage and if so delete them from there? It would be at/admin/users@cyrrelsneer commented on GitHub (Jun 13, 2025):
Hi,
I currently have 1 admin and 1 working user and 3 or 4 invisible users (just to make sure that you understand what could one expect to see).
On that specific page I can only see one user (not my admin) account, but not the 3 or 4 that I have created without the working mail account
@oschwartz10612 commented on GitHub (Jun 13, 2025):
Okay sounds like a bug then. Thanks for letting us know. We will look into it - my guess is we just need to handle the reset of the user setup process correctly if the email part fails.
In regards to how to resolve this right now unfortunately there are two not great options:
Let me know if you need any further pointers on that!
@cyrrelsneer commented on GitHub (Jun 13, 2025):
hey, thanks for the response.
There is no real impact for me as they were mail adresses from my own domain and I was tinkering around before setting the real user up.
Just for the sake of a clean database I will not do that, but I cross my fingers you'll maybe find the bug and I can see the users in a later version ;-)
If you need anything else I can surely give logs or whatever is needed.
Thanks for your great work!
@SirAry commented on GitHub (Jun 19, 2025):
Hi, and thanks for your work too. I ran also into that issue just forgetting to put the smtp secure option in config. And thinking that default example with host, port, user and pass is enough. Of course when I tried to add users I got timeout 10000 failure to add, but the user email was added in database and disallowed me to add again the same username/email. I really need this, and I think that such an error must be treated somehow in the app. For example by not writing in db in case of any error, or if it is necessary deleting the row in case of error/failure to send. To manually edit the db for such is not a good option at all. Also, in my case there are a lot of resources defined :) and it will be a pain to reset-up all. Please give me another solution. Maybe a clean option to delete all users that are not confirmed. Or show all users in user section even if they are confirmed or not... This option will be best, as in case of many invites we can see if we invited someone and not confirmed, or failed to invite or such other things.
@oschwartz10612 commented on GitHub (Jun 22, 2025):
@SirAry we will work on a better way to prevent this and to clean bad users out of the system with a cli tool or something but I think your best bet right now if you want to keep your config is to use a basic sqlite editor like Dbever and remove the users. I am sorry its not super easy or simple to do. You could delete the users from the users table and then reupload the db.