[GH-ISSUE #853] Can't change password and recreate account with same name #4884

New issue

Closed

opened 2026-03-01 15:36:58 +03:00 by kerem · 3 comments

kerem commented

2026-03-01 15:36:58 +03:00

Owner

Originally created by @skrylexx on GitHub (Feb 6, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/853

Hi,

Here are the steps i followed before the bug :
I enabled TOTP on my ui.
Then i updated nginx's version.
I had some issues with configuration file that i replaced to recover everything, i restarted service then it worked again.
Next, i saw that passwords was 20 char max, so i tried to modify mine.
I had a bug that said "Username already used" :

I tried to disconnect then go back to my account, but i was not able to connect, it said "Wrong password", and "Wrong parameters" in the top of the login page.

I switched to the admin account of the proxy to modify my password, but same problem.
I deleted the account, but i wasn't able to create a new one with the same name.
So i created a new one with "adm-" in front of, but same problem, i can't login with.

I need to get back my account name and setup again the TOTP on my account.
This time, i will not change my password for nothing.

I had another question too.
I'm renewing my certificates with letsencrypt from and for my nginx reverse proxy, and I'd like to do it with the UI, as it's easier to access.
How can i do it ?
I tried following the documentation, but i wasn't able to make it work.

Is it working as with letsencrypt from cli ?
Is it only generating certificate for DNS name that are already registred in the DNS provider ?

Thanks

Originally created by @skrylexx on GitHub (Feb 6, 2025). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/853 Hi, Here are the steps i followed before the bug : I enabled TOTP on my ui. Then i updated nginx's version. I had some issues with configuration file that i replaced to recover everything, i restarted service then it worked again. Next, i saw that passwords was 20 char max, so i tried to modify mine. I had a bug that said "Username already used" : ![Image](https://github.com/user-attachments/assets/d3db95cf-be6e-45cb-9195-0ad9ac726d4c) I tried to disconnect then go back to my account, but i was not able to connect, it said "Wrong password", and "Wrong parameters" in the top of the login page. I switched to the admin account of the proxy to modify my password, but same problem. I deleted the account, but i wasn't able to create a new one with the same name. So i created a new one with "adm-" in front of, but same problem, i can't login with. I need to get back my account name and setup again the TOTP on my account. This time, i will not change my password for nothing. --------------------- I had another question too. I'm renewing my certificates with letsencrypt from and for my nginx reverse proxy, and I'd like to do it with the UI, as it's easier to access. How can i do it ? I tried following the documentation, but i wasn't able to make it work. Is it working as with letsencrypt from cli ? Is it only generating certificate for DNS name that are already registred in the DNS provider ? Thanks

kerem

2026-03-01 15:36:58 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-01 15:36:59 +03:00

Author

Owner

@0xJacky commented on GitHub (Feb 6, 2025):

This is a known issue, please wait for the patch. #852

@0xJacky commented on GitHub (Feb 6, 2025): This is a known issue, please wait for the patch. #852

kerem commented

2026-03-01 15:37:00 +03:00

Author

Owner

@0xJacky commented on GitHub (Feb 6, 2025):

For username conflicts after deletion, make sure you delete the records in the trash as well.

@0xJacky commented on GitHub (Feb 6, 2025): For username conflicts after deletion, make sure you delete the records in the trash as well.

kerem commented

2026-03-01 15:37:00 +03:00

Author

Owner

@0xJacky commented on GitHub (Feb 6, 2025):

Please reinstall the latest rc.1, this issue has been resolved.

@0xJacky commented on GitHub (Feb 6, 2025): Please reinstall the latest rc.1, this issue has been resolved.