I’m trying to register a private NextCloud server at home, and I have created a new record whch can be resolved by all the nameservers and still lets encryp says it can’t.
Is it because it’s a 192.168.0 address and it’s not allowed in lets encrypt?
Imroot@ncserver:/etc/apache2# host -t ns militant.dk
militant.dk name server ns1.unoeuro.com.
militant.dk name server ns2.unoeuro.com.
militant.dk name server ns3.unoeuro.com.
root@ncserver:/etc/apache2# nslookup skyen.militant.dk ns1.unoeuro.com.
root@ncserver:/etc/apache2# sudo certbot --apache
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Which names would you like to activate HTTPS for?
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter ‘c’ to cancel): 1
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for skyen.militant.dk
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. skyen.militant.dk (http-01): urn:acme:error:unknownHost :: The server could not resolve a domain name :: No valid IP addresses found for skyen.militant.dk
The following errors were reported by the server:
Detail: No valid IP addresses found for skyen.militant.dk
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.