starred/nginx-ui

Fork 0

mirror of https://github.com/0xJacky/nginx-ui.git synced 2026-04-25 08:45:58 +03:00

[GH-ISSUE #1263] Wrong ACME user selected when getting certificate using Let's Encrypt #6472

New issue

Closed

opened 2026-03-01 17:12:27 +03:00 by kerem · 5 comments

kerem commented

2026-03-01 17:12:27 +03:00

Owner

Originally created by @LinUwUxCat on GitHub (Jul 26, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1263

Describe the bug
In the form to get a certificate from Let's Encrypt, there is an ACME User dropdown, however that choice is either ignored or wrong, as the User chosen to get the CA is the wrong one in the end.

To Reproduce
Steps to reproduce the behavior:

Go to any website's edit page
Click on "Encrypt Website with Let's Encrypt"
Choose an ACME user (here i chose "LinuxCat")
Click on Next
See how the user selected is the wrong one

Here I would expect "LinuxCat", along with my email, to appear, but it ends up being "P", with his email, which is wrong.

Info (please complete the following information):

Server OS: Ubuntu 24.04.2 LTS
Server Arch: x86_64
Nginx UI Version: 2.1.14 (455)
Your Browser: Firefox

Originally created by @LinUwUxCat on GitHub (Jul 26, 2025). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/1263 **Describe the bug** In the form to get a certificate from Let's Encrypt, there is an ACME User dropdown, however that choice is either ignored or wrong, as the User chosen to get the CA is the wrong one in the end. **To Reproduce** Steps to reproduce the behavior: 1. Go to any website's edit page 2. Click on "Encrypt Website with Let's Encrypt" 3. Choose an ACME user (here i chose "LinuxCat") <img width="125" height="135" alt="Image" src="https://github.com/user-attachments/assets/b8ceed09-52bb-4849-a9d2-69d0c2f171ed" /> 4. Click on Next 5. See how the user selected is the wrong one <img width="496" height="189" alt="Image" src="https://github.com/user-attachments/assets/044ff953-6b2c-4178-8d33-5b3104eeffef" /> Here I would expect "LinuxCat", along with my email, to appear, but it ends up being "P", with his email, which is wrong. **Info (please complete the following information):** - Server OS: Ubuntu 24.04.2 LTS - Server Arch: x86_64 - Nginx UI Version: 2.1.14 (455) - Your Browser: Firefox

kerem

2026-03-01 17:12:27 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-01 17:12:28 +03:00

Author

Owner

@0xJacky commented on GitHub (Jul 26, 2025):

Hi, did you click save button before renew the cert?

@0xJacky commented on GitHub (Jul 26, 2025): Hi, did you click save button before renew the cert?

kerem commented

2026-03-01 17:12:28 +03:00

Author

Owner

@LinUwUxCat commented on GitHub (Jul 26, 2025):

This is not on the renew certificate page, this is on the website's page directly. However i also tried it on the certificate page now and there's the same problem yes, it's still the wrong user, even after saving

@LinUwUxCat commented on GitHub (Jul 26, 2025): This is not on the renew certificate page, this is on the website's page directly. However i also tried it on the certificate page now and there's the same problem yes, it's still the wrong user, even after saving

kerem commented

2026-03-01 17:12:28 +03:00

Author

Owner

@0xJacky commented on GitHub (Jul 28, 2025):

This problem is quite strange, and I cannot reproduce it.

@0xJacky commented on GitHub (Jul 28, 2025): This problem is quite strange, and I cannot reproduce it.

kerem commented

2026-03-01 17:12:28 +03:00

Author

Owner

@0xJacky commented on GitHub (Jul 28, 2025):

I have refactored the user selector. You can update to the latest dev version for testing.

@0xJacky commented on GitHub (Jul 28, 2025): I have refactored the user selector. You can update to the latest dev version for testing.

kerem commented

2026-03-01 17:12:29 +03:00

Author

Owner

@BigBang1112 commented on GitHub (Aug 3, 2025):

Can confirm the user selection now applies the changes properly and the certificate is requested on correct email. Previous certificates have acme user called "0" to what was previously empty, but it is still backwards compatible, so looks fine. The 0 user is curious though.

@BigBang1112 commented on GitHub (Aug 3, 2025): Can confirm the user selection now applies the changes properly and the certificate is requested on correct email. Previous certificates have acme user called "0" to what was previously empty, but it is still backwards compatible, so looks fine. The 0 user is curious though.