@MooCloud_Matt I think you can just use "no-op" in your situation and also use a custom wildcard certificate. The proxy can then accept just that wildcard cert. no-op ignores DNS checks. The cert can be Let's Encrypt or not depending on if your proxy can carefully forward well-known HTTP requests.

@Jeyakumarrathnaselvi services -> redis -> restart it. I think you should be able to restore after that.

@girish Thanks, will try this !

I think we have to 100% move to auto-generated passwords for the initial user in apps from the next release. We will make this a priority.

@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