How to set up naked domain https://mydomain.com to work

[boostm...@gmail.com]

Hi,

I've gone thru the set up on let's EncryptSSL on this doc https://www.nodechef.com/docs/node/global/letsencryptssl  for my domain ("boostmode.net" "www.boostmode.net")

and I've set up the DNS records as shown below in NameCheap. The text record is set up as instructed in the doc https://www.nodechef.com/docs/node/global/domains 

In the Routing, I have set up

• Redirect "boostmode.net" to "www.boostmode.net"
• ForceSSL : "Yes"

however, https://boostmode.net isn't going anywhere.  Is this the correct way to set up?

I'd like to do the following

1. Always servers "www.boostmode.net" or "boostmode.net" with "https://"

2. Redirect  http://boostmode.net to "https://www.boostmode.net"

2. Redirect  https://boostmode.net to "https://www.boostmode.net"

2. Redirect  http://boostmode.net/* to "https://www.boostmode.net/*"

Anyone knows how to set up, please help 

Thanks

[dev.no...@gmail.com]

On the NodeChef side of things you have setup everything correctly. Your issue is boostmode.net is not resolving to NodeChef but www.boostmode.net is.

ping boostmode.net

Pinging boostmode.net [162.255.119.107] with 32 bytes of data:

Reply from 162.255.119.107: bytes=32 time=147ms TTL=41

Reply from 162.255.119.107: bytes=32 time=158ms TTL=41

Reply from 162.255.119.107: bytes=32 time=149ms TTL=41

Reply from 162.255.119.107: bytes=32 time=147ms TTL=41

ping www.boostmode.net

Pinging boostmode-****.nodechef.com [149.56.17.34] with 32 bytes of data:

Reply from 149.56.17.34: bytes=32 time=37ms TTL=50

Reply from 149.56.17.34: bytes=32 time=36ms TTL=50

Reply from 149.56.17.34: bytes=32 time=76ms TTL=50

Reply from 149.56.17.34: bytes=32 time=64ms TTL=50

Note in the above, for www.bostmode.net, ping picks up the nodechef subdomain correctly. 

[dev.no...@gmail.com]

Also after the validation is over, you can delete the TXT record so you can set a CNAME for the root domain as well since you cannot have both the TXT record and CNAME for the same record name at the same time.

[boostm...@gmail.com]

Thanks for your reply.  

Is this means I need to set up A record to point to '149.56.17.34' for @ (naked domain) on DNS side?

[boostm...@gmail.com]

I see you are suggesting CNAME record to point to nodeChef subdomain of my container also delete the TXT record.

However, according to my DNS provider (NameCheap), if I set CNAME record for Root (@), they mentioned that e-mail will stop working.

  

[dev.no...@gmail.com]

We have updated the dashboard to provide the IPv4 and IPv6 addresses of the load balancers assigned to your App. Note on the dashboard you will find 3 IP addresses, make sure to create an A record for each  address clients can failover if a load balancer is unreachable.

[BoostMode Contact]

That’s great!

BTW, where in Dashboard I can find those IP info?
I looked under App Action but I can’t find it?

[BoostMode Contact]

Found it under Custom Domain thanks. Now I’m setting A Records for @ with those 3 IPv4s

> On Jul 18, 2017, at 4:28 PM, dev.no...@gmail.com wrote:
>