[GH-ISSUE #959] Renewal of Certs with non-default ACME User Fail #4940

New issue

Closed

opened 2026-03-01 15:37:22 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @Neshura87 on GitHub (Apr 12, 2025).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/959

Describe the bug
When creating a Cert with a non-default ACME User renewal fails because it tries to use the Default User

To Reproduce
Steps to reproduce the behavior:

Create ACME User for use with Step-CA
Create Certificate with Step-CA ACME User
Renew Certificate
Certificate Renewal uses Default (System Initial User) User

Expected behavior
Certificate Renewal should use the ACME User saved for the Certificate

Screenshots

Info (please complete the following information):

Server OS: Debian 12
Server Arch: x86_64
Nginx UI Version: 2.0.0-rc.5
Your Browser: Firefox

Additional context
Through some testing (changing emails of the ACME users mostly) I've discovered that the application does not pass the acme user in the websocket request for certificate renewal. Which consequently leads to the Default User always being selected. If I understand the code correctly this should be solvable by simply passing the acme_user_id in the websocket request.

Originally created by @Neshura87 on GitHub (Apr 12, 2025). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/959 **Describe the bug** When creating a Cert with a non-default ACME User renewal fails because it tries to use the Default User **To Reproduce** Steps to reproduce the behavior: 1. Create ACME User for use with Step-CA 2. Create Certificate with Step-CA ACME User 3. Renew Certificate 4. Certificate Renewal uses Default (System Initial User) User **Expected behavior** Certificate Renewal should use the ACME User saved for the Certificate **Screenshots** ![Image](https://github.com/user-attachments/assets/cc05e7c3-73c9-4ef8-9931-9347d7d4fa18) ![Image](https://github.com/user-attachments/assets/b1813bf5-9a09-44a9-9d03-bf5097f960f3) **Info (please complete the following information):** - Server OS: Debian 12 - Server Arch: x86_64 - Nginx UI Version: 2.0.0-rc.5 - Your Browser: Firefox **Additional context** Through some testing (changing emails of the ACME users mostly) I've discovered that the application does not pass the acme user in the websocket request for certificate renewal. Which consequently leads to the Default User *always* being selected. If I understand the code correctly this should be solvable by simply passing the `acme_user_id` in the websocket request.

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@0xJacky commented on GitHub (Apr 12, 2025):

Hi @Neshura87, this issue has been fixed in the recent comment, please wait for the v2.0.0-rc.6.

@0xJacky commented on GitHub (Apr 12, 2025): Hi @Neshura87, this issue has been fixed in the recent comment, please wait for the v2.0.0-rc.6.