I configured my fallback origin in cloudflare, and added the custom hostname using automatic HTTP validation. Everything validated and shows as active:
First of all, are you using Flexible SSL setting in Cloudflare? The 404 error for your https page includes this part: Server at asmtcf.wittsparks.com Port 80. An https connection shouldn’t be made on port 80.
You can (should) fix this by changing Cloudflare’s SSL setting to Full (strict).
Other then that, the error is clearly returned by your server, so you probably have some error in your vhost for asmtcf.wittsparks.com.
I actually didn’t have a virtual host entry for the subdomain - I thought that Cloudflare for SaaS was forwarding the content/responses. Adding that solved the problem.
If Cloudflare did that, then every custom hostname for the same origin would display the same site. That would not be very helpful for businesses that serve multiple customers from the same origin (though this is supported on Enterprise plans).
But it’s still weird that the connection was made to your server on port 80, I would recommend looking into that.
The 404 error message that I copied into my first post included the port.
The dev tools show you what port is used to connect to Cloudflare, not how Cloudflare connects to your server.
The fact that we were able to even see the error is a clear giveaway - without a vhost for the name, we should have seen a certificate error, not a 404.
Are you certain your main CF account is not using the flexible ssl option?
