Cloudron.io Staff
Hello @stirchley.coop
I also had a look and redacted some content.
Also, the content that was not redacted are not critical since Cloudron ensures that non of the Cloudron services are accessible from the internet.
But if you still feel more comfortable to delete the whole topic, I can do that.
Hello @stirchley.coop
Since this topic could be of value to other people, I would like to keep the topic.
You can edit your posts to redact any details, mainly the domain name I see, but I personally would not consider that sensitive.
Hello @stirchley.coop
Great I could help and everything is resolving back to normal.
When everything is resolved, please leave a comment so I can mark this topic as solved.
Hello @stirchley.coop
Apr 24 19:17:50 BoxError: Storage volume "NetCup RS voln639290a1" is not active. Could not determine mount failure reason.
Can you validate if the mount is actually active and working?
You can use the mount -l command to show you all mounts on your system.
There is also this log entry:
Apr 24 19:17:06 shell: mounts: mountpoint -q -- /mnt/volumes/00fd99454f384c91a83326ad3097bb1e
Do these mounts exist and are accessible?
Hello @stirchley.coop
That is good to hear but also a little odd.
Just make sure that the app is in a functional state and does indeed have its data due to the still printed mount error.
Hello @stirchley.coop
Can you check in your Cloudron dashboard under Volumes?
If the volume has a red dot, please press the ... button to the right side and then press Remount.
When the remount works signalled by a green dot, you can go to your apps that are unresponsive into the Repair section and press Retry task.
This should repair the unresponsive apps back into a working state.
The log looks correct so far.
It is recreating the containers due to the update and this can take some time.
Can you observe this for maybe 5 minutes and report back?
Hello @stirchley.coop
I'm thinking I uninstall Cloudron from the server and reinstall version 9.1.5 with yesterday's backup
This would be the easy / safe route.
I think we can figure out this issue together and fix your server without restoring from a backup.
But the decision is up to you.
This output:
root@v2202403157799261297:~# docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f472efd072b2 registry.docker.com/cloudron/mail:3.18.2 "/app/code/start.sh" 17 minutes ago Created mail
is very suspicious.
No other docker container running from cloudron except this one.
Can you try to restart the box.service with:
systemcrtl restart box.service
Then you can also observe the box.log with:
tail -f /home/yellowtent/platformdata/logs/box.log
To see all log messages from Cloudron.
Hello @stirchley.coop
Can you please share the output of the command:
docker ps -a
and
docker network list
