Ok, I solved it. I had to delete all my DNS settings that previously existed and then reset them. Once I did this within milliseconds Cloudron started working. Whew, I was sweating bullets there for a minute.

@d19dotca Yes, I think you're right, thank you. I need to look into that. Or move some long term storage files ("archive") into Minio. That might just be moving the problem, but dividing the problem might be a partial solution.

added a Feature Request for #2 -- please upvote https://forum.cloudron.io/topic/5027/pop3-gmail-polling-support

@girish that fixed the issue. Thanks!

@girish thanks for the guidance, that's exactly what I was looking for

@d19dotca Okay, that is a bit confusing, but I will only be able to figure it out once I try it. I appreciate everyone's help and responses.

@nebulon Yes before rebooting I tried to umount-remount but it seems it has been impossible due to an error... So I decided to restart. About auto-remounting it will be an amazing feature

@derin If email works, you can just click Reset password in the login page and you will get an email with the reset link. If email is wrong or does not work, you can SSH into the server and run cloudron-support --admin-login. This will give you a one time use password (will also print the username to use). You can then go to Profile and change the password. Note that you have to run the command again to get a new password when changing the password.

@girish yep, it loads, awesome, thank you

@humptydumpty Yes, correct. Server restart won't fix the issue, have to restart the service explicitly (since it copies over certs).

@garyhost did you get this sorted out ? I guess the box code is/was down. You can figure using systemctl status box. And if it is indeed down, please check /home/yellowtent/platformdata/logs/box.log. You can also check if you have enough disk space because this is a common source of the box code being down.

@rmdes yes, I am not sure why. It doesn't happen in any of our demo servers or managed services. Quite strange. It could also be that maybe others have hit it but have not noticed it (since it only causes a CPU spike..) but clearly it's a bug since it's been fixed upstream.

@rlp10 there is no clear cut between which backup target is preferred. We try to cover a few options to cover a range or use-cases, but all should work. If you own the backup machine, I would anyways not advise to encrypt backups. Unencrypted files on trusted storage is a lot easier to restore if worst case trouble hits

I figured it out. Git's inline help, upon not knowing who you are, makes the suggestions: git config --global user.email <email> git config --global user.name <name> Cloudron's problem is "--global". It has no problem with setting the user.name and user.email for a particular /app. So this solved my problem: git config user.email <email> git config user.name <name> of course substituting my email address for "<email>" and my name for "<name>".

@nebulon You try to make things easy for us but we'll screw it up somehow. ; )

@girish Thanks for looking at this. Just triggered another backup with all apps active and it succeeded. I guess then it's finally time to move to the new hardware (plus making sure that the new system is using the c locale by default)

@girish right, I figured that out! Thank you! I am downloading that 10gb data now.. wuih! You are saviour!

@onlybro Thanks that worked

@girish said in Email into apps - DNS/MX/CNAME/TXT: You have to setup the CNAME/TXT for the root domain and not for my.example.com. You don't have to set it up for each app individually Thank you. That was my main issue.

@bluxomat To answer your questions (and my understanding of your needs): If you have different customers on one Cloudron instance, there is no option to have a "kind of" multi-tenant user management. If you give the role "user admin" to one user of client A, she is able to see and create all users on that Cloudron instance. In that case it's better for all (including Cloudron the company because of more subscriptions) to install a Cloudron instance per client. If you are a "frugal fox" (never heard of this before, I had a quick translate of the german word "Sparfuchs" that means something like: If I don't have to put more money in other people's pockets, why should I?), then the only chance is to have some kind of "multi-tenant" within the user management of the apps themselves. But if your customer has more than one app on your instance, you have to repeat the creation of users in every app again and again.