Should port 443 be open on apache when requesting letsencrypt.sh?
Let's encrypt uses port 80 for domain verification. However, outgoing port 443 must be open in your firewall, otherwise let's encrypt script won't be able to connect to the API.
Should port 443 be open on apache when requesting letsencrypt.sh?
cat /var/named/[B]your.hostname.com.db[/B]
Why is it strange? DA always created these records for hostname. Please check:
Code:cat /var/named/[B]your.hostname.com.db[/B]
There you should see all the records, unless you removed the zone manually. The problem is that you're using an external DNS server, and you don't have an identical zone file there.
Let's encrypt uses port 80 for domain verification. However, outgoing port 443 must be open in your firewall, otherwise let's encrypt script won't be able to connect to the API.
root@server:~# netstat -tulpn | grep :443
tcp 0 0 127.0.0.1:443 0.0.0.0:* LISTEN 1854/nginx.conf
tcp 0 0 181.xx.278.xx:443 0.0.0.0:* LISTEN 1854/nginx.conf
tcp6 0 0 ::1:443 :::* LISTEN 1854/nginx.conf
Its fixed now and the certificate is installed, but this one will not get auto-renewed i assume
Is it possible to automate this by cron ? if yes could you give some example how to do that ?
Thank for your time and great product
cd /usr/local/directadmin
echo "action=rewrite&value=letsencrypt" >> data/task.queue; ./dataskq d2000
Apache listens to 8081 instead of 443 (using nginx_apache). Could this be the reason why I can't connect with the letsencrypt API?Code:root@server:~# netstat -tulpn | grep :443 tcp 0 0 127.0.0.1:443 0.0.0.0:* LISTEN 1854/nginx.conf tcp 0 0 181.xx.278.xx:443 0.0.0.0:* LISTEN 1854/nginx.conf tcp6 0 0 ::1:443 :::* LISTEN 1854/nginx.conf
e is 65537 (0x10001)
problems making Certificate Request
140277613172368:error:0D07A098:asn1 encoding routines:ASN1_mbstring_ncopy:string too short:a_mbstr.c:147:minsize=1
/usr/local/directadmin/data/users/USER/domains/example.com.csr: No such file or directory
140363474167440:error:02001002:system library:fopen:No such file or directory:bss_file.c:398:fopen('/usr/local/directadmin/data/users/USER/domains/example.com.csr','r')
140363474167440:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:400:
Size of certificate response is smaller than 500 characters, it means something went wrong. Printing response...
"detail":"Error unmarshaling certificate request"
I had to set letsencrypt=2, with 1 it would not work.
Is it possible to request a SSL certificate for my subdomains?
Make sure you don't have anything like the following in your custom templates, because it'd return 403 error then:
Code:location ~ /\. { deny all; }
You get 404, so I think it's still related to the alias thing (I can check it directly on your sever if you'd like me to)
Seems good, right?Getting challenge for klompenfabriek.nl from acme-server...
Waiting for domain verification...
Challenge is valid.
Getting challenge for www.klompenfabriek.nl from acme-server...
Waiting for domain verification...
Challenge is valid.
Generating 4096 bit RSA key for klompenfabriek.nl...
openssl genrsa 4096 > "/usr/local/directadmin/data/users/klompenfab/domains/klompenfabriek.nl.key.new"
Generating RSA private key, 4096 bit long modulus
......................................................++
............++
e is 65537 (0x10001)
Certificate for klompenfabriek.nl has been created successfully!
Doh! Something simple I've overlooked. Can't this be done automatically by DA when a user creates a certificate? Or at least give a notice?You have to enable SSL in domain setup.