Here is a previous issue that was solved in the Community:
I configured my 2nd server with an additional domain in the same manner, but DNS fails to flow. So what am I doing wrong here?
Please review my detailed configurations and MOSS.sh’s support response.
== My CloudFlare DNS Configurations and Validation ==
I made sure the DNS Name Servers were changed at Registrar to point to the CloudFlare Name Servers and have confirmed DNS has propagated and the CloudFlare IP is appearing: 22.214.171.124
I only have 3 DNS Records entered at CloudFlare pointing to my Server IP Address: 126.96.36.199
A swiftdigitalmarketinggroup.com 188.8.131.52
cname www swiftdigtialmarketinggroup.com
cname dev swiftdigtialmarketinggroup.com
I installed WP (using MOSS’s install) and enabled Let’s Encrypt for HTTPS traffic.
At CloudFlare I ensured SSL was enabled and set for Full (strict) as instructed by CloudFlare Community member in the link at the top of this post. Again by setting my first domain (swiftpointcloud.com) to Full (strict) cleared the problem…but not this time. Why?
From my Windows PC I flushed my DNS Cache and can successfully NSLookup swiftdigtalmarketinggroup.com confirming it resolves to the CloudFlare public IP: 184.108.40.206
I have confirmed DNS propagated, but I can’t browse http://swiftdigitalmarketinggroup.comwithout getting the error below or attached.
When I browse or http://swiftdigtialmarketinggroup.com I get the following error:
This site can’t be reached
swiftdigtialmarketinggroup.com ’s server IP address could not be found.
- Search Google for swift digital marketing group
== MOSS.sh Support Response ==
Not all possible combinations of Moss/Cloudflare configs make sense. You can choose any of these combinations:
Cloudflare Crypto: Off (not recommended) => choose None as the certificate in Moss
Cloudflare Crypto: Flexible => choose None as the certificate in Moss
Cloudflare Crypto: Full => provide Moss with a certificate for the site (it doesn’t need to be valid cert though, a self-signed one will work)
Cloudflare Crypto: Full (strict) => provide Moss with a certificate for the site (it must be a valid cert, e.g. one you purchased for your domain or a Cloudflare’s Origin Certificate)
You could tell Moss to use Let’s Encrypt in cases 3-4, but then you must also take care to disable HTTP to HTTPS redirections in Cloudflare. Otherwise, Let’s Encrypt renewals won’t work. In general this setup is harder to troubleshoot, so I don’t encourage you to follow this path unless you know well how Cloudflare and Let’s Encrypt work and play together.