mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #1168] I cant renew SSL cert for my domain via http challenge... #958
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#958
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zantag on GitHub (Jun 10, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1168
Hi i cant renew SSL for my domain. Every time when i try to renew it manually message "Internal Error" appear...

What can i do?
This is the log of container via portainer GUI:
@zaqrt-zaq commented on GitHub (Jun 10, 2021):
same issue here . i been using this for about 6 mounth and today is stops working (i can`y request new certyfikate)
@frisodubach commented on GitHub (Jun 10, 2021):
Just a random guess here, but is the domain proxied by any change? Maybe try disabling the proxy when renewing the certificate.
@zaqrt-zaq commented on GitHub (Jun 10, 2021):
For me helped switching to the version 2.3.9 and deleting the let's encrypt folder
@asage-me commented on GitHub (Jun 10, 2021):
I'm curious if my issue is related? I'm using DNS challenge but I see the same "Internal Error" message
https://github.com/jc21/nginx-proxy-manager/issues/1146
@apollo40 commented on GitHub (Jun 10, 2021):
Same problem here. Cant renew Certs via Certbot using DNS Challenge on Cloudflair
@chaptergy commented on GitHub (Jun 10, 2021):
I'm pretty sure they aren't, as this issue is about using the HTTP challenge. So any issues with DNS challenges most likely have nothing to do with this issue.
@heyitsmdr commented on GitHub (Jun 10, 2021):
This is happening to me as well, using the http challenge. I'm going to see if I can debug this a bit further tonight.
@zantag commented on GitHub (Jun 11, 2021):
My version on nginx proxy manager is v2.7.3 but i see the latest is v2.9.3... How to update to to the latest version i hope this version to fix my problem...
@apollo40 commented on GitHub (Jun 11, 2021):
I updates mine too, and it didnt solve the Problem. Today i was able to renew 1 Cert then the Error displayed again.
For Updating it depands on your Setup. If you habe a docker-compose file, just enter the Directory and run
docker-compose pull
docker-compose up -d
@Verttigo28 commented on GitHub (Jun 11, 2021):
Yeah same issues for the past 6 months.
You need to remove the let's encrypt folder and redo it.
I don't know why, cause log say that the request could not be made but if i go on the HTTP Challenge URL i can access it shortly.
@zantag commented on GitHub (Jun 11, 2021):
I install nginx proxy manager via portainer like stack. I try to reinstall it but again is old v2.7.3... maybe integrated certbot is old or?
@Verttigo28 commented on GitHub (Jun 11, 2021):
You need to pull and check your docker.compose if the version is not hard coded.
@chartinger commented on GitHub (Jun 16, 2021):
Same problem here. (via docker-compose) Pulled the current image, error still there. @Verttigo28 which directory did you remove? If i remove the letsencrypt folder nginx fails to start.
@zantag commented on GitHub (Jul 1, 2021):
I give up guys, i bought new cert from ssl provaider and upload it manually to the proxy server.
@ChrisParsons commented on GitHub (Jan 19, 2022):
Has anyone figured out how to fix this? I'm having the same issue i.e. I cannot get new certificates or renew certificates using lets encrypt. This was working and now appears to be broken. I tried deleting the lets encrypt folder but had to restore it as NPM failed to start.
@chaptergy commented on GitHub (Jan 19, 2022):
What do the letsencrypt logs say? See https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/1749#user-content-certificate-error
@ChrisParsons commented on GitHub (Jan 20, 2022):
Thanks for the response @chaptergy. I have ports 443 and 80 directed from the router to the NPM container. I'm not using DNS challenge.
Here is log from /var/log/letsencrypt/letsencrypt.log
Looks like I can't access the internet from the container. The DNS server for the container is 127.0.0.11 which I understand is correct?
Any ideas?
@ChrisParsons commented on GitHub (Jan 21, 2022):
Resolved my issue. I don't think it was related to the NPM container but rather my docker config. I don't know exactly what was wrong. Restarting the docker service didn't seem to help but restarting the server on which docker runs seemed to fix it.
@github-actions[bot] commented on GitHub (Mar 9, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 22, 2025):
Issue was closed due to inactivity.