Request for Assistance – App Fails to Start Due to Offline External Volume

[thibault]

Hello,

I need help with an issue on my Cloudron server. My Nextcloud app cannot start anymore because it is still trying to mount an external volume that is now offline. This external server is no longer accessible, and Cloudron keeps attempting to attach the bind mount during container creation, which results in an error.

The logs show:
“invalid mount config for type ‘bind’: stat /mnt/volumes/… : input/output error”

Since the volume cannot be reached, the app remains stuck in a pending restart/configure state and the container cannot be created.

I can no longer remove the volume from the UI because the app will not start, and I cannot find a way to delete this external volume reference manually.

Could you please advise how to remove this broken external volume from Cloudron so the app can start normally again?

Thank you for your assistance.

[nebulon]

That is likely a UI bug to not allow to remove the volume in such a case. We will see how to fix this for the next release, until that, you may be able to just create and empty folder at the /mtn/volumes/... path it tries to access. This should bring back the app, and then you should be able to remove the volume in the app config.

[thibault]

Thank for the reply!
I was able to resolve the issue.
The external SSHFS volume was still registered in Cloudron, but the remote server was offline, causing the container to fail during startup. Since the mount point was stuck and not removable at first, I proceeded as follows:

sudo rmdir /mnt/volumes/...
mkdir /mnt/volumes/...
cd /mnt/volumes/...

By recreating an empty local folder at the exact path Cloudron expected, the app was finally able to start again. Once the app was running, I could remove the external volume cleanly from the Storage configuration in the Cloudron dashboard.