My domain is peggy.rvchost.com and I have configured my internal records as such however I am not reaching the proper address via the web.
This is what my clients are showing as DNS resolution:
peggy.rvchost.com is an alias for peggy.rvchost.com.cdn.cloudflare.net.
peggy.rvchost.com.cdn.cloudflare.net has address 104.21.88.203
peggy.rvchost.com.cdn.cloudflare.net has address 172.67.186.210
If you followed the guidance in the Community topic that you linked, the DNS output that you shared matches what you should expect to see with such a configuration.
I am able to see a web based launcher panel at that address.
What are you doing?
What are you expecting to see as a result?
What happens instead?
You are seeing the correct thing and I am seeing the correct thing outside of my network however see the screenshot for what I’m seeing when I enter peggy.rvchost.com.cdn.cloudflare.net in a browser on my local network. The secure connection is Firefox and the error 1001 is Safari.
Typing in peggy.rvchost.com was not working for the longest time so I figured the best way to trace/troubleshoot would be to put in what I did to bypass any DNS config that was happening locally. Now when I type it in: Peggy.rvchost.com, it appears to work properly on Firefox but Safari doesn’t auto upgrade to HTTPS and hangs. Any thoughts there?
It doesn’t look like you have configured a redirect from HTTP-> HTTPS. When I connect to the peggy.rvchost.com hostname using curl, I am sent an HTTP 307 temporary redirect to a relative URL of /board
The best way to ensure that your HTTP connection is upgraded to HTTPS is to have a redirect in place that covers that. You can do that at the edge using Cloudflare or at the origin. It is often helpful to choose one location or the other to handle such redirection in order to avoid competing and conflicting redirects creating an infinite loop.
