<?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[App Proxy: add a way to specify healthcheck path]]></title><description><![CDATA[<p dir="auto">Hi guys,</p>
<p dir="auto">I would like to setup <a href="https://grafana.com/oss/loki/" target="_blank" rel="noopener noreferrer nofollow ugc">Grafana Loki</a> as an app on my Cloudron server by using <code>docker run</code> and proxying it this way: <code>http://private_ip:loki_exposed_port</code>. My app is working and accessible through Cloudron reverse proxy but Cloudron healtcheck is returning 404 because Loki service don't expose the route <code>/</code> (they expose <code>/ready</code> for healtcheck).</p>
<p dir="auto">Because of this, the application is showing <code>not responding</code> in my apps page and Cloudron is constantly polling it to verify the readiness.</p>
<p dir="auto">Is there an option I missed to specify a route to target healthcheck endpoint in Cloudron app config?</p>
]]></description><link>https://forum.cloudron.io/topic/10843/app-proxy-add-a-way-to-specify-healthcheck-path</link><generator>RSS for Node</generator><lastBuildDate>Tue, 12 May 2026 00:11:00 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/10843.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 11 Jan 2024 14:28:48 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to App Proxy: add a way to specify healthcheck path on Fri, 12 Jan 2024 15:37:05 GMT]]></title><description><![CDATA[<p dir="auto">We don't have this feature yet to specify the healthcheck path in the app proxy. I will move this feature request.</p>
<p dir="auto">Thanks for the suggestion!</p>
]]></description><link>https://forum.cloudron.io/post/80985</link><guid isPermaLink="true">https://forum.cloudron.io/post/80985</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Fri, 12 Jan 2024 15:37:05 GMT</pubDate></item></channel></rss>