[solved] Godaddy https redirects to www

Ok I give up, been playing with this for a few days and can not get it to work.

I have successfully installed a cert using Manual file creation and DNS challenge.
My domain is l2lseo.com

SSL checker shows all green successful for https://l2lseo.com but not for www.l2lseo.com

So this is the problem. Godaddy redirects https://l2lseo.com to www.l2lseo.com which I do not have a cert for.

So if I anyone types https://l2lseo.com it redirects to www.l2lseo.com which throws “Your connection is not private”

Obviously I do not have access to WWW root domain and I have tried creating a file in my root director for www.l2lseo.com in ./well-known/acme-challenge, just like I did for l2lseo.com. However certbot fails to verify this cert.

So what am I doing wrong and two is there any way to set this up?

Hi @Radmod,

What Certbot command did you run, and what error message did you get?

This cert is only for l2lseo.com (and doesn't include www.l2lseo.com)
See: crt.sh | 256479042

You could simply redo the certificate request to include both domains (l2lseo.com & www.l2lseo.com)

Thanks for your response. So how do I redo the request for both domains is the question?

Here is what I have done.

./certbot-auto certonly --manual
I then enter in the two domains

l2lseo.com, www.l2lseo.com

I then created the two files in /public_html/.well-known/acme-challange/long string name

I hit enter and certbot found the file for l2lseo.com but did not find it for www.l2lseo.com

The following errors were reported by the server:

Domain: www.l2lseo.com
Type: connection
Detail: Fetching
http://www.l2lseo.com/.well-known/acme-challenge/nbanq5Ze1FAdcbII13gkpS6LBZQuph0kIbKhd5rRbzs/:
Timeout

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. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

I have also tried the DNS challenge for both domains
I can add the txt file to DNS for l2lseo.com but can not enter it in for www.l2lseo.com as godaddy has a cname record for www to point to l2lseo.com

Here is what I have done.

./certbot-auto certonly --manual
I then enter in the two domains

l2lseo.com, www.l2lseo.com

I then created the two files in /public_html/.well-known/acme-challange/long string name

I hit enter and certbot found the file for l2lseo.com but did not find it for www.l2lseo.com

The following errors were reported by the server:

Domain: www.l2lseo.com
Type: connection
Detail: Fetching
http://www.l2lseo.com/.well-known/acme-challenge/nbanq5Ze1FAdcbII13gkpS6LBZQuph0kIbKhd5rRbzs/:
Timeout

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. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

I have also tried the DNS challenge for both domains
I can add the txt file to DNS for l2lseo.com but can not enter it in for www.l2lseo.com as godaddy has a cname record for www to point to l2lseo.com

To “fix” the DNS AUTH problem, replace the CNAME with an A record that points to the same IP.

There must be some difference in their vhost files.
They should both point to /public_html

HTTP, deleting the cname for www and just putting in an A record for www did the trick. Thanks for your help.

Since it was a WP site I had to make additional changes to the site to get it Green.

I’m including a link to the instructions I found in case anyone else is looking for help.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.