Closed ParkerChih closed 3 months ago
github-actions[bot]
commented
3 months ago Please upgrade to the latest code and try again first. Maybe it's already fixed. acme.sh --upgrade If it's still not working, please provide the log with --debug 2, otherwise, nobody can help you.
ParkerChih
commented
3 months ago Before I success, I always use the synology`s scheduled task to run the command. At that time in my domainname dir, only 4 files in there. They are
But when I mannul to execute the conmand one by one
docker exec acme acme.sh --force --log --issue --server letsencrypt --dns dns_cf --dnssleep 120 -d example.com -d *.example.com
After that there have extra 3 files flowlling：
and the time for resquest cert from the internet is not as quickly as before, almost about 3 minutes.
The else command without any hitch, and successful soon.
docker exec acme acme.sh --deploy -d example.com -d *.example.com --deploy-hook synology_dsm
Although the ture reason still unknown, but I remmond you to try this mannal way when you can`t find any other problem. And notice if the files downloaded fully. I have search the full list before, but not successful, haha!
Steps to reproduce
I use the amcesh docker on my Synology DS220+ with 7.2.1-69057 update5 which amcesh is 3.0.8 version . Cause the network services reason I have no 80 and 443 port，so chose the dns way. It looks like the processer of down cer does not have error info. And it has already start to raplace cer , but finally fail. If the device_id is incorrect , it will has a different ending soon without “-----BEGIN EC PRIVATE KEY----”. I find many issue report , but still have any idea.
Debug log