Cloudron Forum

@humptydumpty You’re absolutely right. I’ll try to restore the post.

@girish Thank you, I'll try writing there and let you know.

Many thanks to everyone for the help and information; everything is fine now. I ended up purchasing a few additional modules. It was the classic case of an error between the chair and the keyboard. 🙂

Thank you for the explanation, I didn't know that.

I was about to write a long time ago that the parameter for resetting SSH has changed:

sudo systemctl restart ssh.socket

@nebulon Thank you for your response. I correctly configured the repositories, and the installation is now working without any issues.

@girish Ok, great! Thank you very much for the information. I really appreciate your time. Thanks again!

Sure, I understand. I’ll wait. No problem. Still, thank you for the information.

Always good to hear, if things are fine 🙂

Thanks for sharing and good to know they are aware of at least and might come up with solutions.

@girish Thank you, Cloudron team, once again for the great work. After updating Cloudron, the problem is resolved. Thank you very much.

I tried the command

bin/tootctl accounts refresh --all --verbose

and after running this command, the avatars started reappearing on our instance. It seems to have resolved the issue. Thank you.

@nebulon Thank you for your response. Yes, it seems the issue is indeed with hardlinks. I have them enabled. I will try to wait for the Cloudron update, or I might consider using Borg for backups to the Storage Box. That should probably resolve the issue. Another option is using rsync with the -H switch, but I haven't tested it yet. Thank you very much for your help.

@girish How simple things seem complicated 🙂 Thank you very much for adding to the guide. It really is simple. Cloudron is just great.

@girish It really was caused by uBlock Origin. After disabling it, Umami appears to load all pages correctly. In Uptime Kuma, I removed and re-added the HTTPS address for Umami, and now everything works fine. Thank you very much for the information; I would have never thought of that.

@girish Alright, thank you for the information. I think I can close the thread now.

For the "suspicious login" plugin atleast, maybe try reporting it upstream . Just make sure it's up to date before reporting upstream . There are some issues upstream already - https://github.com/search?q=repo%3Anextcloud%2Fsuspicious_login+caught+unknown+error+ipv4+background+training&type=issues

The other one comes from some fediverse thing in nextcloud ...

@nebulon Yes, I just ran in the admin jobs section, extract metadata. Thank you very much for your help.