NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Customize SSL cert renewing interval to avoid reloading nginx every hour
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Is your feature request related to a problem? Please describe.
First of all: great tool! Setting up reverse poxies is really fun with this one :)
According to the docker logs, npm is checking for expired certificates every hour:
[10/26/2020] [1:26:22 AM] [SSL ] › ℹ info Renewing SSL certs close to expiry...
[10/26/2020] [1:26:24 AM] [Nginx ] › ℹ info Reloading Nginx
[10/26/2020] [1:26:24 AM] [SSL ] › ℹ info Renew Complete
[10/26/2020] [2:26:22 AM] [SSL ] › ℹ info Renewing SSL certs close to expiry...
[10/26/2020] [2:26:24 AM] [Nginx ] › ℹ info Reloading Nginx
[10/26/2020] [2:26:24 AM] [SSL ] › ℹ info Renew Complete
[10/26/2020] [3:26:22 AM] [SSL ] › ℹ info Renewing SSL certs close to expiry...
[10/26/2020] [3:26:23 AM] [Nginx ] › ℹ info Reloading Nginx
[10/26/2020] [3:26:23 AM] [SSL ] › ℹ info Renew Complete
[...]
I think reloading nginx every hour could lead to problems in the business times of our web services (e.g. downloads buffered by nginx ..)
Is there a way to customize the cron job which triggers the cert renewing every hour to start the renewing only once a day or so?
Describe the solution you'd like
some way (UI or production.config) to customize the renewal interval
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing the hourly certificate-renewal job and how it triggers Nginx reloads; done means exposing a configurable renewal interval through the UI or production.config and confirming that renewals and reloads follow it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100