Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
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.
My web server is (include version): apache
The operating system my web server runs on is (include version): Linux
My hosting provider, if applicable, is: amazon aws
I can login to a root shell on my machine (yes or no, or I don't know): yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
You say that you are using Apache as your webserver, but for some reason I'm getting a 200 OK response from Nginx for ANYTHING I request (even things that don't exist).
>>> http://apostolosandreaswindsor.com/.well-known/acme-challenge/test
> --------------------------------------------
> 200 OK
> --------------------------------------------
Status: 200 OK
Code: 200
Server: nginx/1.16.1
Date: Tue, 01 Dec 2020 17:59:32 GMT
Content-Type: text/html; charset=utf-8
Connection: close
>>> http://www.apostolosandreaswindsor.com/.well-known/acme-challenge/test
> --------------------------------------------
> 200 OK
> --------------------------------------------
Status: 200 OK
Code: 200
Server: nginx/1.16.1
Date: Tue, 01 Dec 2020 17:59:19 GMT
Content-Type: text/html; charset=utf-8
Connection: close
It looks like you have GoDaddy site redirection active, which will definitely interfere with acquiring a certificate via http-01 validation. I'm guessing there's an opaque (masking) redirection?
@griffin thanks for your help. I followed your instructions and I managed to get the certificate. However when I try to go to my website I got this:
Destination
Unknown
Everything's working on our side, so the link you clicked is either wrong or has been retired.
except from the A should I change something else? My A now is the IP of my webserver. When I call it directly I can see my website. When I use the www.apostolosandreaswindsor.com I get an error.
Just don't make the mistake of covering a mail subdomain with a certificate and then try using it for outbound (SMTP) connections. You'll have to accept "all certificates". Best to use the GoDaddy hosting instance name in your email software.
