NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Automatically generate PFX certificate
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.
I recently moved from the linuxserver/letsencrypt docker container to nginx-proxy-manager. linuxserver/letsencrypt would also generate a PFX cert during cert renewal, and store this in the same folder as the other cert files. It would be lovely if this feature could also be added to this container.
Describe the solution you'd like
Perhaps an automated script that would generate a PFX cert during cert renewal?
Something along the lines of:
"openssl pkcs12 -export -out privkey.pfx -inkey privkey.pem -in cert.pem -certfile chain.pem -passout pass:"
Describe alternatives you've considered
I'm currently generating the PFX cert manually, but this means having to do this every three months.
Additional context
I'm running a dockerized Plex server which only accepts PFX cert formats. I'm using a path mapping which points at the folder where the certs are stored. This means Plex always uses an up to date certificate. This currently doesn't work because there is no PFX being generated.
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
Start by tracing the container's certificate-renewal process and use the proposed openssl pkcs12 command as the behavioral reference. Done means a PFX file is generated automatically beside the renewed certificate files, with the empty password behavior described in the issue, so Plex can consume the updated certificate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100