<?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 repair]]></title><description><![CDATA[A list of topics that have been tagged with repair]]></description><link>https://forum.cloudron.io/tags/repair</link><generator>RSS for Node</generator><lastBuildDate>Tue, 19 May 2026 09:28:46 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/tags/repair.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 09 Jan 2025 13:56:05 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Bug: When adding of a volume fails, docker container creation fails, removal of old volume impossible]]></title><description><![CDATA[@girish said in Bug: When adding of a volume fails, docker container creation fails, removal of old volume impossible:

nvm, I reproduced it. If you change the path behind Cloudron's back, it doesn't work. I think it's correct to error since that path doesn't exist anymore. But anyway quick fix is: simple create empty /media/SG2TB/M/Calibre on the server and then Retry configure will work.
After it comes up, remove the mount from the app, delete the volume, add new volume with correct path, add mount into app...

That's what I did, I went behind Cloudron's back 
... and didn't think of the obvious solution presented by you! Thank you.
]]></description><link>https://forum.cloudron.io/topic/13084/bug-when-adding-of-a-volume-fails-docker-container-creation-fails-removal-of-old-volume-impossible</link><guid isPermaLink="true">https://forum.cloudron.io/topic/13084/bug-when-adding-of-a-volume-fails-docker-container-creation-fails-removal-of-old-volume-impossible</guid><dc:creator><![CDATA[necrevistonnezr]]></dc:creator><pubDate>Thu, 09 Jan 2025 13:56:05 GMT</pubDate></item><item><title><![CDATA[Issue after 8.0.3 upgrade with one app because of manually configured domain name - a post mortem (kind of)]]></title><description><![CDATA[Thanks for sharing . Right... our current domain/location configuration follows an all or nothing approach. If one or more fail, it will refuse to bring the app up and will get "stuck" forever . We have a task somewhere to make this more smart and also make the app repair feature smarter but it always gets pushed out as low priority.
]]></description><link>https://forum.cloudron.io/topic/12295/issue-after-8-0-3-upgrade-with-one-app-because-of-manually-configured-domain-name-a-post-mortem-kind-of</link><guid isPermaLink="true">https://forum.cloudron.io/topic/12295/issue-after-8-0-3-upgrade-with-one-app-because-of-manually-configured-domain-name-a-post-mortem-kind-of</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Thu, 15 Aug 2024 15:17:22 GMT</pubDate></item></channel></rss>