@rbin saw your ticket on support. I sent you a response there.

Glad it all worked out

@girish alright, thanks a lot. Always useful to learn more about the things we use I did what you wrote above and now everything works just like usual If disk issues keep on happening, I will have to get in contact with the provider..

@nebulon thanks a millio! it works now, i am going to proceed with the update to the ubuntu 20.04.

This is fixed already with https://git.cloudron.io/cloudron/box/-/commit/5fc0a5f9a28be601bcec2e3bcf68fc93f3b3e8c5 but only part of next release.

@girish THANK YOU! I followed your instructions and all good now.

Also for others to come here, to get back up on Ubuntu 18.04 run the following commands via SSH: mkdir -p /usr/local/node-16.18.1 curl -sL https://nodejs.org/dist/v16.18.1/node-v16.18.1-linux-x64.tar.gz -o /tmp/node.tar.gz tar zxvf /tmp/node.tar.gz --strip-components=1 -C /usr/local/node-16.18.1 rm /tmp/node.tar.gz ln -sf /usr/local/node-16.18.1/bin/node /usr/bin/node ln -sf /usr/local/node-16.18.1/bin/npm /usr/bin/npm systemctl restart box Then the system should be working again, however for the 7.5 update ubuntu has to be upgraded first.

@girish Thank you!

Yes, that was the problem. I was logged in under a second test user account that I had assigned admin role. Logged out and back in as my original cloudron owner account and all good on that front. Thanks.

For clarification, the root cause is a ' in the french translation, which breaks some javascript code. The code is fixed to prevent this, but since it involves other changes, the easiest fix the moment is to remove the quote from the translation file. This can be done by running the following on the server via SSH: sed -e "s/\"errorIncorrectCredentials\": \"Nom d'utilisateur ou mot de passe incorrect\",/\"errorIncorrectCredentials\": \"Nom dutilisateur ou mot de passe incorrect\",/" -i /home/yellowtent/box/dashboard/dist/translation/fr.json

@girish I've never used a profiler, but maybe I should look into that. I'll open another thread for my issue.

Check the contents of/home/yellowtent/box/VERSION . Is it 7.4.3 ? If so, you can run the commands below and make it work again . After you get it back, snapshot the server and upgrade ubuntu when possible. mkdir -p /usr/local/node-16.18.1 curl -sL https://nodejs.org/dist/v16.18.1/node-v16.18.1-linux-x64.tar.gz -o /tmp/node.tar.gz tar zxvf /tmp/node.tar.gz --strip-components=1 -C /usr/local/node-16.18.1 rm /tmp/node.tar.gz ln -sf /usr/local/node-16.18.1/bin/node /usr/bin/node ln -sf /usr/local/node-16.18.1/bin/npm /usr/bin/npm systemctl restart box

@girish Thank you Girish for the fast response! We solved it now with your help.

@girish said in Mail rejected by Protonmail: Also, have you tried https://www.mail-tester.com/ already for any other errors? Thanks for linking this very nice tool!

This is fixed in 7.5.0

@BrutalBirdie said in Volumes error on access but work? kinda?: Getting the picture? Yes! Excellent

This is fixed for the next version.

A server snapshot is useful to recover quickly. But a backup is quite separate : Backups are generally separate from your server provider. If you lose access to AWS (maybe they think you are a bad actor or a billing failure makes them kill everything, this happened to me), then backups are a way for you to recover. Snapshots are almost always in the same server provider. Backups are portable . You can't take a EBS snapshot and put it in Digitalocean On Cloudron, backups are per app. So, you can restore each app individually unlike a server snapshot which will roll back everything. Backups help in upgrading things. For example, you can upgrade/migrate database using backup of old version into new version. So, they have different use cases. Both are useful. Use both when possible.

I got everything working now by skipping some updates, finding a problematic one and debugging it a bit. I'm leaving a message I was going to send mid debugging before I managed to get it working just in case anyone else comes across the same issue. I got it working by skipping versions until I got to one that wouldn't apply. It was v4.41.0. It would run but the database migration would never connect to MySQL. This happened even after I got to the version just before and tried to apply it a few times. While I was debugging I found that the MySQL connection wouldn't work from the Terminal. Then I put the app into recovery to debug further. It MySQL worked in the Terminal there, so I turned off recovery mode and it booted just fine! Not sure what the root issue was though. Unusual that I was able to reproduce it but then it kind of resolved itself. Maybe switching to or from recovery resets some value causing an issue. I'm not sure. Original message: So, this is now pretty specific to Ghost. I've made it up to v4.40.2 just fine, but when I apply the next version v4.41.0, Ghost fails to start. The log shows Jul 11 14:39:18 ==> Start ghost Jul 11 14:39:18 ==> Clear potential migration lock Jul 11 14:39:18 mysql: [Warning] Using a password on the command line interface can be insecure. Jul 11 14:39:20 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:39:30 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:39:40 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:39:50 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:40:00 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:40:10 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:40:20 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:40:30 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:40:40 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:40:50 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:41:00 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:41:10 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:41:20 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:41:30 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:41:32 json: updated "/app/data/config.production.json" in-place Jul 11 14:41:32 json: updated "/app/data/config.production.json" in-place Jul 11 14:41:32 json: updated "/app/data/config.production.json" in-place Jul 11 14:41:32 ===> Copy frotend/public folder for asset generation Jul 11 14:41:32 ==> Loading /app/data/env for potential overrides Jul 11 14:41:32 ==> Ensure permissions Jul 11 14:41:32 ==> Migrating database Jul 11 14:41:40 => Healtheck error: Error: connect ECONNREFUSED 172.18.17.238:2368 Jul 11 14:41:44 [2023-07-11 21:41:44] ERROR Invalid database host. Jul 11 14:41:44 Jul 11 14:41:44 Invalid database host. Jul 11 14:41:44 Jul 11 14:41:44 "Please double check your database config." Jul 11 14:41:44 Jul 11 14:41:44 Error ID: Jul 11 14:41:44 500 Jul 11 14:41:44 Jul 11 14:41:44 Error Code: Jul 11 14:41:44 DATABASE_CREATION_FAILED Jul 11 14:41:44 Jul 11 14:41:44 ---------------------------------------- Jul 11 14:41:44 Jul 11 14:41:44 Error: connect ETIMEDOUT Jul 11 14:41:44 at /home/cloudron/ghost/versions/5.41.0/node_modules/knex-migrator/lib/database.js:134:19 Jul 11 14:41:44 at /home/cloudron/ghost/versions/5.41.0/node_modules/knex-migrator/lib/database.js:50:23 Jul 11 14:41:44 at Connection._handleTimeoutError (/home/cloudron/ghost/versions/5.41.0/node_modules/knex-migrator/node_modules/mysql2/lib/connection.js:202:17) Jul 11 14:41:44 at listOnTimeout (node:internal/timers:564:17) Jul 11 14:41:44 at process.processTimers (node:internal/timers:507:7) The diff for this version bump is here: https://git.cloudron.io/cloudron/ghost-app/-/commit/93e180df6ad9216f8f04480b9b60212816f86c28 I've tried restoring my backup to v4.40.2 and re-applying multiple times but it continues to fail. It also fails if I use the CLI to skip this version and jump to the latest.

No, nothing there. It might have gotten deleted when I cleared the message from the email queue days ago. I don't care about the file as much as knowing from which app did that message originate from. It's probably from the WP app, but I'd like a sure way to tell. I'm guessing there are no tools to trace it back to the app. Oh well.