Cloudron Forum

Hello @james Thanks for the suggestion! I checked the MySQL service — it has more than enough memory (20 GiB total, only about 40 % used). So it doesn’t look like a memory issue. There are no errors or warnings in the MySQL logs so far, so I think it should be fine. I’ll keep an eye on it for a few days just to be sure. Anyway, thank you very much for your help and your time!

@girish said in [GUIDE] Move PeerTube video storage to Hetzner S3: @archos should I use the email on this forum? Yes, please use the same email I use for this forum.

@james Thanks for the quick reply and especially for the fast update, you’re the best!

@robi Ok, I’ll give it a try. I’ll also search the PeerTube GitHub to see if someone has already reported this issue. Thanks a lot for your time and the information.

@robi I only added the recommended commands: 0 13,23 * * * rm -rf /app/data/public/wp-content/cache/* > /dev/null 2>&1 0 13,23 * * * rm -rf /tmp/magick-* /tmp/imagick* > /dev/null 2>&1

Looks like it's an issue with the Photos app itself. Hopefully it will be fixed soon. Github

Just for testing, you could place the app into recovery mode then create those files/folders and then run the start.sh which for Wallabag is at /app/code/start.sh

@nebulon Thanks a lot for the quick fix – just updated the app and everything works perfectly now. Really appreciate the fast response and great support!

Same problem in my peertube instance.

As far as I understand the domain will be verified with WOPI so probably add that, but then again I guess just give it a try.

Glad it worked out. Might be worth to report upstream in the Immich issue tracker actually.

@joseph said in Issue Starting NodeBB on Cloudron After Server Restart: /app/pkg/start.sh Thank you very much. I followed this guide, then adjusted the plugins to the corresponding versions and copied the appropriate package.json. The issue has been resolved

@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!