Renew now on SSL Certificates page gives internal error #1816
Comments
|
Here ist my Log about the Error:
|
|
Hi, I have been solving this too. I don't know why, but some of my certificates cannot be renewed as it outputs "Connection refused" for acme-challenge as shown on the picture.
If this happens, than after each restart of NPM there is stuck processes as shown on the next image, that results in "Another instance of Certbot is already running."
If you kill these processes, than you can create new certificate for these domains and it will work as it should (renew will not work). Then go to your host and assign the new certificate to it. Than you can delete the old one. After these changes is done, you can try to restart your NPM and see if there is still that processes. If not, than you are OK and you can ensure yourself by issuing renew. Hope this helps and I am looking forward for this to be fixed. I don't know what cause this, but it happends on all of my 4 NPM installs for only some domains. |
|
where can i find those logs? in npm/data/logs i find but they don't show me any errors like in your posts |
I have found this log here: /var/log/letsencrypt/letsencrypt.log |
|
Hi, Just go to your
Make it exectuable:
And run it:
At the end of the script you will be asked if you want to delete the old files which are no longer needed. After running the script restart your nginxproxymanager instance. #!/usr/bin/env bash
DELETE_ME=()
for i in $(find . -name "npm-*" -type d); do
pushd "${i}" &>/dev/null
RELATIVE_PATH=$(echo "${i}" | sed 's/\.\///g')
# find all regular (non symbolic link) files
for t in $(find . -name "*.pem" -type f); do
# remove ./ path prefix
FILE_TO_LINK=$(echo "${t}" | sed 's/\.\///g')
NEW_FILE_NAME=$(echo "${FILE_TO_LINK}" | sed 's/\./1\./g')
echo "${RELATIVE_PATH}/${FILE_TO_LINK} needs to be linked"
echo "Moving ${RELATIVE_PATH}/${FILE_TO_LINK} to ${RELATIVE_PATH}/${FILE_TO_LINK}.bak"
mv "${FILE_TO_LINK}" "${FILE_TO_LINK}".bak
DELETE_ME+=("${RELATIVE_PATH}/${FILE_TO_LINK}.bak")
echo "linking ../../archive/${RELATIVE_PATH}/${NEW_FILE_NAME} to ${RELATIVE_PATH}/${FILE_TO_LINK}"
ln -s ../../archive/"${RELATIVE_PATH}"/"${NEW_FILE_NAME}" "${FILE_TO_LINK}"
if [[ "$?" == 0 ]]; then
echo "success"
else
echo "failure"
fi
done
popd &>/dev/null
done
if [[ -n ${DELETE_ME} ]]; then
echo -e "\nOld *.pem files:\n"
echo "${DELETE_ME[*]}"
echo "Do you want to delete the old *.pem files? (y/n) "
read delete
if [[ "${delete}" == "y" || "${delete}" == "yes" ]]; then
for y in "${DELETE_ME[@]}"; do
rm "${y}"
done
fi
else
echo "Nothing to be done."
fi |
|
For anyone experiencing this issue, I was able to fix my setup using the following steps:
After doing the above steps for each of my Proxy Hosts, they can be renewed from the GUI. I'm not sure if Auto-renew will work but I guess I'll find out in a couple months. I don't know what caused the problem or if it will come back but at least for now it appears to be working. |
This just create an "Internal error", no new cert. |
|
The same on my side. |
|
I had the same issue and solved it by adding a DNS CAA record for the HOST.MYDOMAIN.TLD and setting letsencrypt.org as an authorized certificate provider (I use EasyDNS). |
|
npm 2.10.1. Out of nowhere expired certs + symlink error on npm startup. Internal error in GUI. Godaddy DNS challenge cert |
|
Issue is now considered stale. If you want to keep it open, please comment 👍 |
|
For me the issue is still there: |
|
I just get internal error in NPM gui when trying to renew wildcard cert (*.domain.ltd) |
|
I encountered the same issue when trying to renew certificates using the NPM GUI. Removing the certificate that failed to renew and requesting new ones resolved the problem for me. |
Same issue for me but following these steps seemed to work. Be nice to see this fixed though so we don't have to do things manually. |
I'm on v2.9.15 and have a problem with "renew now" on SSL Certificates tab. I get internal error. Tried with different certs for different proxy hosts. Need more info, then please tell me where to find the needed logs.
The text was updated successfully, but these errors were encountered: