Cannot open website via www but can open via https

[TKtong]

Hi,
My website cannot open via www but can open via https

The site is https://nestsearcher.com

Faithfully yours,
Thanetphon L.

[schoen]

Hi Thanetphon,

It looks to me like when someone connects to http://nestsearcher.com/, your web server sends a 301 redirect

< HTTP/1.1 301 Moved Permanently
< Content-Type: text/html
< Content-Length: 617
< Date: Sun, 06 Jan 2019 03:17:41 GMT
< Server: LiteSpeed
< Location: https://nestsearcher.com/
< Vary: User-Agent
< Connection: Keep-Alive

which points the user’s browser at https://nestsearcher.com/, which loads successfully. Is this not what you wanted?

If you’re referring to http://www.nestsearcher.com/ and https://www.nestsearcher.com/ (with the www prefix), they have a different DNS setup from the base domain.

$ host nestsearcher.com
nestsearcher.com has address 209.97.167.168
nestsearcher.com mail is handled by 20 mx2.tmdhosting.com.
nestsearcher.com mail is handled by 10 mx1.tmdhosting.com.
$ host www.nestsearcher.com
www.nestsearcher.com is an alias for www.nestsearcher.com.cdn.cloudflare.net.

You have a DNS CNAME record that points www.nestsearcher.com to www.nestsearcher.com.cdn.cloudflare.net, which does not exist. If you want this to work via Cloudflare, you’ll have to do some more setup on Cloudflare’s site and follow their documentation about what the DNS records should say.

If you want it not to be proxied by Cloudflare, you should get rid of this CNAME record and create an A record that points to the same web server that the base domain is pointed to (209.97.167.168). Since your Let’s Encrypt certificate does cover both the base domain nestsearcher.com and the subdomain www.nestsearcher.com, this should most likely work properly once the DNS record has been fixed.

[stevenzhu]

Hi,

I’ve moved this topic to #help.

Thank you