Domain is inaccessible, please verify!

[tombarber92]

Hi there,

I have previously set up Litespeed WordPress config with AWS and had these issues, however, I don't seem to be able to get the domain to be encrypted this time.

It is a new domain (sportswear-designer.com) and I have linked it with Route 53 like previous, but I keep coming up against the same issue.

When trying to link the domain to the EC2 instance, it says that "Domain has been added into OpenLiteSpeed listener." but then when trying to add the Let's encrypt cert it fails.

Has anyone got any advice?

 

[Pong]

Do you use OLS or LSWS? For OLS, please use https://forum.openlitespeed.org/

 

[Unique_Eric]

@tombarber92

curl -I http://sportswear-designer.com/
curl: (6) Could not resolve host: sportswear-designer.com

You did not point the domain correctly, so it failed to connect and apply cert.

 

[tombarber92]

@tombarber92

curl -I http://sportswear-designer.com/
curl: (6) Could not resolve host: sportswear-designer.com

You did not point the domain correctly, so it failed to connect and apply cert.

Hi Unique_Eric, that is a strange one, as the domain is linked to the IP and when you go to the domain, it shows you the WordPress installation.

 

[Unique_Eric]

I see, just checked again, only www domain works but the root domain. You can edit /opt/domainsetup.sh and comment out Line 321 https://github.com/litespeedtech/ls-cloud-image/blob/master/Setup/domainsetup.sh#L321 to skip the domain verify.

 

[tombarber92]

I see, just checked again, only www domain works but the root domain. You can edit /opt/domainsetup.sh and comment out Line 321 https://github.com/litespeedtech/ls-cloud-image/blob/master/Setup/domainsetup.sh#L321 to skip the domain verify.

Thank you for looking into this for me Unique_Eric! With your help and the team at 123-Reg, we managed to connect the domain to the IP address after all this time and patience. Once that was all sorted, the Let's Encrypt script went through without issues. Don't know why the domain wasn't 100% connected, but all's sorted now. Thanks again.