starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #1411] letsencrypt SSL Certificate has 306 bytes key size #1102

New issue

Closed

opened 2026-02-26 06:35:46 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 06:35:46 +03:00

Owner

Originally created by @fahidsh on GitHub (Sep 18, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1411

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- Yes
Are you sure you're not using someone else's docker image?
- Yes
Have you searched for similar issues (both open and closed)?
- Yes

Describe the bug

My previously generated letsencrypt SSL-Certs had a Key file privkeyXX.pem of 1.7k size. After generating the letsencrypt certs, I copy them from NPM archive folder and use them with some other docker-apps.

lately, when I renew letsencrypt certs from NPM, certs are being generated, but the key file privkeyXX.pem has a size of 306 bytes. When I copy these NPM generated certs, some of my other docker-apps are failing to start with error invalid certificate. I have checked everything including permissions etc. Everything is fine, only difference is the key file size of letencrypt-certs generated by NPM.

At the time when problem started a few days back, I had NPM 2.9.7, today I updated my NPM to 2.9.9 and regenerated the certs and generated some new certs, all have a key file of 306 bytes.

When I goto NPM->SSL Certs, it show the certificates correct with correct expiry date. So I am wondering, why is it? has something changed on Letsencrypt side which is causing smaller key files (from 1.7 KB to 306 B) or is something wrong with NPM?

As for my NPM usage, I am not using some complex settings, just have some proxy hosts for my docker-apps being served with HTTPS.

Nginx Proxy Manager Version

2.9.7 and 2.9.9

To Reproduce
Steps to reproduce the behavior:

Go to 'SSL Certificates'
Click on 'Renew Certificate' or 'Generate Certificate' from Let's encrypt
goto npm data -> letsencrypt/archive/npm-XX directory via terminal
ls -lah and see the size of privkeyXX.pem file.

Expected behavior

Screenshots

Operating System

Ubuntu Server 20.04

Additional context

Originally created by @fahidsh on GitHub (Sep 18, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1411  **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug**  My previously generated letsencrypt SSL-Certs had a Key file _privkeyXX.pem_ of 1.7k size. After generating the letsencrypt certs, I copy them from NPM archive folder and use them with some other docker-apps. lately, when I renew letsencrypt certs from NPM, certs are being generated, but the key file _privkeyXX.pem_ has a size of 306 bytes. When I copy these NPM generated certs, some of my other docker-apps are failing to start with error _invalid certificate_. I have checked everything including permissions etc. Everything is fine, only difference is the key file size of letencrypt-certs generated by NPM. At the time when problem started a few days back, I had NPM 2.9.7, today I updated my NPM to 2.9.9 and regenerated the certs and generated some new certs, all have a key file of 306 bytes. When I goto NPM->SSL Certs, it show the certificates correct with correct expiry date. So I am wondering, why is it? has something changed on Letsencrypt side which is causing smaller key files (from 1.7 KB to 306 B) or is something wrong with NPM? As for my NPM usage, I am not using some complex settings, just have some proxy hosts for my docker-apps being served with HTTPS. **Nginx Proxy Manager Version**  2.9.7 and 2.9.9 **To Reproduce** Steps to reproduce the behavior: 1. Go to 'SSL Certificates' 2. Click on 'Renew Certificate' or 'Generate Certificate' from Let's encrypt 3. goto npm data -> letsencrypt/archive/npm-XX directory via terminal 4. ls -lah and see the size of privkeyXX.pem file. **Expected behavior**  **Screenshots**  [![npm-20210918.png](https://i.postimg.cc/Qdk3j3Z2/npm-20210918.png)](https://postimg.cc/5X0GmD0g) **Operating System**  Ubuntu Server 20.04 **Additional context**

kerem

2026-02-26 06:35:46 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:35:47 +03:00

Author

Owner

@fahidsh commented on GitHub (Sep 18, 2021):

this is how the new smaller key file looks with cat command

@fahidsh commented on GitHub (Sep 18, 2021): this is how the new smaller key file looks with cat command [![npm-20210918-2.png](https://i.postimg.cc/GpySbPDH/npm-20210918-2.png)](https://postimg.cc/8FTbH6tS)

kerem commented

2026-02-26 06:35:47 +03:00

Author

Owner

@chaptergy commented on GitHub (Oct 5, 2021):

Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/1411

@chaptergy commented on GitHub (Oct 5, 2021): Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/1411

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

No description provided.

Rows
Columns