<![CDATA[Topics tagged with cloudflare]]>https://fusionauth.io/community/forum/tags/cloudflareRSS for NodeThu, 13 Aug 2026 14:56:31 GMTInvalid Date60<![CDATA[Receiving 502 errors when using Cloudflare in front of FusionAuth]]>This is due to non-ASCII characters in headers causing an issue in the FusionAuth parsing code. Cloudflare sends headers with non-ASCII characters (such as cf-region: São Paulo) which triggers this issue.

This is a java-http bug that was fixed in 2024, and released in FusionAuth version 1.51.2.

So, two options:

upgrade to a version of FusionAuth 1.51.2 or newer. This is the recommended approach, but may require some work. as an interim workaround, you can disable the "Add visitor location headers" option from your CloudFlare console. This should not have any negative impact, since we do not inspect those headers. ]]>https://fusionauth.io/community/forum/topic/2932/receiving-502-errors-when-using-cloudflare-in-front-of-fusionauthhttps://fusionauth.io/community/forum/topic/2932/receiving-502-errors-when-using-cloudflare-in-front-of-fusionauthInvalid Date<![CDATA[Does FusionAuth integrate with Cloudflare?]]>This iss possible and we have many other customers doing this.

Technically speaking FusionAuth doesn't care what kind of proxy sits in front of it, if any. So this is outside of FusionAuth but Cloudflare makes it really simple.

]]>https://fusionauth.io/community/forum/topic/328/does-fusionauth-integrate-with-cloudflarehttps://fusionauth.io/community/forum/topic/328/does-fusionauth-integrate-with-cloudflareInvalid Date