<?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[Easier problem solving diagnostics]]></title><description><![CDATA[<p dir="auto">Sometimes, there are notifications, like this one:</p>
<blockquote>
<p dir="auto">Failed to new certs of xxx: Unexpected status: invalid. Renewal will be retried in 12 hours</p>
</blockquote>
<p dir="auto">These often require extra context to understand what went wrong, or how to rectify the problem (for many backup failures, for example).</p>
<p dir="auto">It would be great if the notification provided some sort of a pointer to jump into Cloudron's logs at the time of the event in this case, to dig into the problem further.</p>
]]></description><link>https://forum.cloudron.io/topic/4852/easier-problem-solving-diagnostics</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 04:15:05 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/4852.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 08 Apr 2021 11:22:22 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Easier problem solving diagnostics on Thu, 08 Apr 2021 18:05:04 GMT]]></title><description><![CDATA[<p dir="auto">Right, we are actually fixing notification for the next release (6.3). In the meantime, Domains -&gt; Renew all certs and then check the logs (button on the same page) if it fails. Usually, Let's Encrypt errors are temporary and currently Cloudron is a bit overzealous reporting those errors.</p>
]]></description><link>https://forum.cloudron.io/post/29420</link><guid isPermaLink="true">https://forum.cloudron.io/post/29420</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Thu, 08 Apr 2021 18:05:04 GMT</pubDate></item></channel></rss>