[GH-ISSUE #1137] letsencrypt staging environment #935

Closed
opened 2026-02-26 06:35:03 +03:00 by kerem · 3 comments
Owner

Originally created by @gitmors on GitHub (May 30, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1137

Hello,

I think it would be very useful if there was the possibility to use the letsencrypt staging environment. You could simply set a switch in the mask for creating the certificates.

Is your feature request related to a problem? Please describe.

There is no way to try if you already have a rate limit from letsencrypt.

Describe the solution you'd like

You could simply set a switch in the mask for creating the certificates.

Originally created by @gitmors on GitHub (May 30, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1137 Hello, I think it would be very useful if there was the possibility to use the letsencrypt staging environment. You could simply set a switch in the mask for creating the certificates. **Is your feature request related to a problem? Please describe.** There is no way to try if you already have a rate limit from letsencrypt. **Describe the solution you'd like** You could simply set a switch in the mask for creating the certificates.
kerem 2026-02-26 06:35:03 +03:00
Author
Owner

@jc21 commented on GitHub (Jun 29, 2021):

This should be possible with version 3, as it will add configurable CA's and LE-staging will be pre-populated.

<!-- gh-comment-id:870217146 --> @jc21 commented on GitHub (Jun 29, 2021): This should be possible with version 3, as it will add configurable CA's and LE-staging will be pre-populated.
Author
Owner

@github-actions[bot] commented on GitHub (Mar 10, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:1987039111 --> @github-actions[bot] commented on GitHub (Mar 10, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Apr 22, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2819878282 --> @github-actions[bot] commented on GitHub (Apr 22, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#935
No description provided.