[GH-ISSUE #273] Unable to create a certificate from a second environment #4574

New issue

Closed

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

kerem commented

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

Owner

Originally created by @mateo08c on GitHub (Feb 2, 2024).
Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/273

Describe the bug
It is impossible to generate a self-signed certificate from another environment linked to nginx-ui.

To Reproduce
Steps to reproduce the behavior:

Go to 'Environment'
Click on 'Add.'
Add new node
Go to 'Dashboard'
Click on second 'Environment'
Go to 'Certificates'
Generate certificate
Certificate not generated

Console log

2024-02-02 15:47:42	ERROR	certificate/issue.go:60	websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header

Expected behavior
Unable to generate an automatic certificate.

Screenshots

Originally created by @mateo08c on GitHub (Feb 2, 2024). Original GitHub issue: https://github.com/0xJacky/nginx-ui/issues/273 **Describe the bug** It is impossible to generate a self-signed certificate from another environment linked to nginx-ui. **To Reproduce** Steps to reproduce the behavior: 1. Go to 'Environment' 2. Click on 'Add.' 3. Add new node 4. Go to 'Dashboard' 5. Click on second 'Environment' 6. Go to 'Certificates' 7. Generate certificate 8. Certificate not generated **Console log** ```log 2024-02-02 15:47:42 ERROR certificate/issue.go:60 websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header ``` **Expected behavior** Unable to generate an automatic certificate. **Screenshots** ![image](https://github.com/0xJacky/nginx-ui/assets/36140949/2940a2bf-c754-493f-9714-3120bf22ede7) ![image](https://github.com/0xJacky/nginx-ui/assets/36140949/026b34f7-d36b-42b0-9936-d2d1b1815379)

kerem

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

closed this issue
added the
bug
label

kerem commented

2026-03-01 15:34:23 +03:00

Author

Owner

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

Thanks for your report, this issue has been resolved in 2526d71c0e, and it will be released with the next beta verison.

@0xJacky commented on GitHub (Feb 6, 2024): Thanks for your report, this issue has been resolved in 2526d71c0e4156b01f441aa01b68082ce98721d3, and it will be released with the next beta verison.