Error 1000 - Cloudflare for SaaS Custom hostnames with render.com origin

Background
I am not able to setup the Cloudflare for SaaS Custom hostnames service with a render.com origin.

I receive an Error 1000 “DNS points to prohibited IP” when attempting to go to a customer custom hostname.

Question
Is render.com compatible with the Cloudflare for SaaS Custom hostname product?

See setup steps below resulting in a Error 1000, HTTP 403 for customer domains.

Setup Steps

  1. In render.com - Add a custom domain to web service
  1. In Cloudflare - Create a CNAME record for render.com web service
  1. In render.com - Confirm domain has been verified, cert issued/deployed

  2. In Cloudflare - Turn on proxy (orange cloud) for origin.myapp.com CNAME record

  • This is required by the Cloudflare custom hostname service
  1. In Cloudflare - Configure Custom hostname service
  • Go to Custom hostname service page
  • Configure with origin → origin.myapp.com
  • Go to SSL page - Turn on Full SSL
  1. In Cloudflare - Add custom hostname for a customer
  • Add app.acmeinc.com to custom hostname
  • Verify ownership, wait for Cloudflare SSL to be deployed and issued
  1. In customer DNS registrar - Point to Cloudflare

Observe the following
https://myapp-123.onrender.com - Works as expected
https://origin.myapp.com - Works as expected
https://app.acmeinc.com - Errors with Error 1000 - 403

Hey Joel,

Thanks for the very thorough details - the hard thing is though being able to debug without actual domain names etc. Do you have a service setup like this so we can make queries and see?

It might be that replying here in a public forum isn’t ideal so contacting us via the dashboard via the ‘Contact Support’ link at the bottom is the best place to let us assist you with this,

Regards,

John B

Thanks John for the quick reply. I understand. I’ll reach out with the Contact Support feature with the actual service URLs. :muscle:

ok, We’ll keep our eyes out for it.

John B