Issue with Proxying Cloudflare Custom Hostname for app-dev.shorterloop.com

I am encountering an issue related to the proxying of a Cloudflare custom hostname for the domain app-dev.shorterloop.com. I have configured a Cloudflare Page URL, app-7t4.pages.dev, which is correctly mapped to app-dev.prodeasy.com. However, when attempting to proxy this using the Cloudflare custom hostname app-dev.shorterloop.com, I am facing difficulties and receiving a Connection Timed Out error (Error code 522) upon trying to access the site.

Below are the settings I have currently applied:

  1. Site prodeasy.com Settings:
  1. Site shorterloop.com Settings:

I have ensured that the SSL settings are correctly configured and that the DNS settings are appropriately set up. Despite this, I am unable to access the desired site through the custom hostname app-dev.shorterloop.com, and the Connection Timed Out error persists.

Additionally, I tried using S3 buckets instead of Cloudflare pages. In that case, it is looking for the proxy bucket name on AWS S3

Please provide guidance on any additional steps that need to be taken to ensure the proper proxying of the Cloudflare custom hostname.

Thank you for your prompt attention to this matter.

Best regards
Dinesh

Add the hostname app-dev.shorterloop.com to the Pages project as a custom domain. Don’t add DNS entries yourself; Pages will create it for you.

1 Like

The thing is, these are vanity URLs for the customer(s), which means it could be anything like ideas.acme.com or ideas.abc.com. Additionally, their DNS managers could be different. My app allows customers to add their custom domains in the product. So it need not necessarily be on Cloudflare. Do you think it would necessarily help.

Yes, it will work for non-Cloudflare domains as long as it’s a subdomain, not the apex. So foo.example.com but not just example.com.

If the domain is in your Cloudflare account, then you don’t create any DNS entries, but just add the custom domain to your pages project.

If the domain is NOT on Cloudflare (or not in your account) then you still must add it to the project (so the server knows to answer to that name). Then, in the domain’s DNS, wherever it is managed, make that name a CNAME to the whatever.pages.dev name. See the docs here:

1 Like

I tried for my Cloudflare account website it worked, I just added the custom name for it.

But to customer’s account which was also on cloudflare it failed

DNS settings-
Type= cname
Name=app-dev
Content = app-7t4.pages.dev
Proxy status= tried both proxied and dnd dns only

Error:

Error 1014

CNAME Cross-User Banned

Oops, I forgot about that limitation. (I had tried it across two accounts and it worked, but it turns out Cloudflare is smart enough to see that I am an admin on both accounts and let it work.) You can’t CNAME to another Cloudflare account like that.

You would use Cloudflare for SaaS for that. See the docs here:

1 Like

I tried that implementing it such a pain!
The approach you shared earlier is working for me that cname for cloudflare pages.
Thank you for that!

Now I just need to check how to programmatically add the custom hostname to cloudflare page.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.