https://www.ory.sh/ logo
Join Slack
Powered by
Hi all. We have been testing integrations with Ory...
# ory-network
e
Hi all. We have been testing integrations with Ory for our platform (we have a Ory Network Production subscription). All has been going well for the most part but we've just run into an issue and I'm trying to see if anything has changed recently in how Ory's Cloudflare configuration is treating requests proxied through AWS Cloudfront as we are now getting 
502
errors. Nothing has changed on our end from a configuration perspective (our platform uses IaaS). I instrumented the CloudFront distribution for realtime logging to troubleshoot and see that we are receiving 
OriginCommError
when connecting to our Ory project as an origin 
{project-slug}.<http://projects.oryapis.com|projects.oryapis.com>
. Direct browser access works fine and I've verified that nothing looks hinky with respect to the DNS and SSL config on Ory's side. Perhaps Cloudflare is (now) blocking CloudFront IP ranges? Has anyone else run into this issue?
b
Hi! Nothing changed recently, and if cloudflare was blocking on interfering, it would return 40X errors. Do you have any webhooks configured? On what requests are you receiving the 502 errors?
e
Hi @bland-eye-99092 - This is not related to webhooks, but rather on requests to the Ory hosted UI that we have been proxying to via AWS Cloudfront.
This was all working as expected for months up until sometime in the last 10 days.
Cloudfront returning a 
502
with an underlying cause of 
OriginCommError
does not necessarily mean that Ory (behind Cloudflare) is returning a 
502
.
We have determined the cause of this issue (thank you @bland-eye-99092) and it relates to how Ory's Cloudflare Enterprise integration handles proxied requests. We're switching to directly pointing the custom domain DNS to the Ory project endpoint for the time being.
2 Views
Open in Slack
PreviousNext
Powered by