Issue with domain proxy setup with cloudflare

Website, Application, Performance DNS & Network
1

I have setup DNS records (CNAME) for a custom domain proxy. when testing the domain without the cloudflare proxy by bypassing cloudflare ( directly accessing the origin server) it works, but with domain proxy get the bellow error.
Note: the content of CNAMEs are: cdn.segment.com and another one api.segemmt.io
we do not use cloudfront, and not sure why this error generated by cloudfront. I am not sure if this issue is related to segment settings or cloudflrae setting.

403 ERROR

The request could not be satisfied.

Bad request. We can’t connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

Generated by cloudfront (CloudFront) Request ID: DM7fX3Ypypr9C9CVDMSNur43KdoSlexx0Ng-u4WD2JS5jWZbUKiMsQ==

4

Without having used Segment or delved into the service’s documentation, my guess is they don’t like the domain sitting behind the proxy as they cannot directly validate it.

5

you mean Segment cannot validate it? I just need to make sure this issue has nothing to do with Cloudflare?

6

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