[GH-ISSUE #1686] Can I re-upload a nginx-proxy-manager ssl and have it auto renew? #1259

New issue

Closed

opened 2026-02-26 06:36:27 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 06:36:27 +03:00

Owner

Originally created by @teamwolfyta on GitHub (Dec 26, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1686

Hello, I was curious if there is a way to upload a SSL cert from a previous installation of npm and have it auto renew ? When I use the custom SSL upload it doesn't provide that option and I don't wanna have to re-create another SSL cert and add another cert to my transparency logs lol

Originally created by @teamwolfyta on GitHub (Dec 26, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1686 Hello, I was curious if there is a way to upload a SSL cert from a previous installation of npm and have it auto renew ? When I use the custom SSL upload it doesn't provide that option and I don't wanna have to re-create another SSL cert and add another cert to my transparency logs lol

kerem closed this issue

2026-02-26 06:36:27 +03:00

kerem commented

2026-02-26 06:36:27 +03:00

Author

Owner

@chaptergy commented on GitHub (Dec 27, 2021):

Unfortunately not. Copying old cerbot config files over would make make it available for certbot, however it would still not be possible to view and select it inside the admin panel, it would not exist there. Furthermore you would have to upload both the certificate, as well as the renew information to make it work, and then just creating a new certificate would be basically the same. Letsencrypt also automatically publishes transparency logs for all issued certificates. So just I don't really see a use case for this.

@chaptergy commented on GitHub (Dec 27, 2021): Unfortunately not. Copying old cerbot config files over would make make it available for certbot, however it would still not be possible to view and select it inside the admin panel, it would not exist there. Furthermore you would have to upload both the certificate, as well as the renew information to make it work, and then just creating a new certificate would be basically the same. Letsencrypt also [automatically publishes transparency logs](https://letsencrypt.org/docs/ct-logs/) for all issued certificates. So just I don't really see a use case for this.

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#1259

No description provided.

Rows
Columns