Hi, I'm gaining my first experience with ISPconfig. I've configured a new domain with SSL and Let's Encrypt enabled. After running /usr/local/ispconfig/server/server.sh (I've disabled cron for debugging) I'm looking at the domain configuration panel again and the two checkboxes for SSL and LE are disabled by magic. Code: ~$ /usr/local/ispconfig/server/server.sh finished server.php. /var/log/ispconfig/ispconfig.log is empty, but why? Code: ~$ "/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" [Sat Oct 16 07:10:31 UTC 2021] ===Starting cron=== [Sat Oct 16 07:10:31 UTC 2021] Already uptodate! [Sat Oct 16 07:10:31 UTC 2021] Upgrade success! [Sat Oct 16 07:10:31 UTC 2021] Auto upgraded to: 3.0.1 [Sat Oct 16 07:10:31 UTC 2021] Renew: 'web2.mydomain.com' [Sat Oct 16 07:10:31 UTC 2021] Skip, Next renewal time is: Wed Dec 15 07:01:08 UTC 2021 [Sat Oct 16 07:10:31 UTC 2021] Add '--force' to force to renew. [Sat Oct 16 07:10:31 UTC 2021] Skipped web2.mydomain.com [Sat Oct 16 07:10:31 UTC 2021] ===End cron=== My new Domain is also not listed in /root/.acme.sh/ Can anybody tell me what's wrong or how to debug precisely? I've got the same behaviour on two seperate installations (ISPConfig version 3.2.6 on Ubuntu 20.04) Thanks!
This means that LE refused to issue a cert or the domain was unreachable from your server. Follow let's encrypt FAQ to find out why: https://www.howtoforge.com/community/threads/lets-encrypt-error-faq.74179/ Btw. the output from server.sh shows that you missed enabling debug mode (see link in Let's encrypt FAQ how to enable it), without debug mode, you won't get any debug info why the cert was not issued.
Hi Till, thank you very much for your helpful advices! Of course, I've missed enabling the debug loglevel :-( After generating meaningful logs I've found the problem: my website acts as a proxy redirector and therefor no acme location is configured for this site. I didn't know it, but I've found a workaround: ht tps: //git. ispc onfig.org/ispconfig/ispconfig3/-/issues/4618 (I have to misspell the link due to restrictions here) It's marked as "fixed"? For me it's solved by this workaround. Thanks!
The fix has been implemented for nginx. Could it be that you didn't reconfigure services when updating?