<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Topics tagged with krakend]]></title><description><![CDATA[A list of topics that have been tagged with krakend]]></description><link>https://fusionauth.io/community/forum/tags/krakend</link><generator>RSS for Node</generator><lastBuildDate>Tue, 09 Jun 2026 09:30:20 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/tags/krakend.rss" rel="self" type="application/rss+xml"/><pubDate>Invalid Date</pubDate><ttl>60</ttl><item><title><![CDATA[FusionAuth Running In Azure Container App Environment]]></title><description><![CDATA[<p dir="auto">Hello there,<br />
I feels like you are encountering some complex issues with running FusionAuth in Azure Container Apps and using KrakenD as a proxy.</p>
<p dir="auto">For the Proxy Configuration Warning, be ensure that your FusionAuth instance is aware of the correct external URL and headers. You might need to set the FUSIONAUTH_URL environment variable appropriately.</p>
<p dir="auto">Releated KrakenD, you could configure it to correctly handle the necessary headers for FusionAuth. Be sure your KrakenD configuration includes the necessary routes and headers for FusionAuth's admin and OAuth endpoints.</p>
<p dir="auto">Consider checking the FusionAuth and KrakenD documentation for any specific configurations needed for Azure environments.</p>
<p dir="auto">If the issue still did not get solved, you might want to reach out to FusionAuth support directly for more tailored assistance.</p>
<p dir="auto">Hope it helps.</p>
]]></description><link>https://fusionauth.io/community/forum/topic/2709/fusionauth-running-in-azure-container-app-environment</link><guid isPermaLink="true">https://fusionauth.io/community/forum/topic/2709/fusionauth-running-in-azure-container-app-environment</guid><dc:creator><![CDATA[dom9]]></dc:creator><pubDate>Invalid Date</pubDate></item></channel></rss>