@girish Thank's! Good the idea to end DST...

@d19dotca it's not a problem. Just the natue of any service being exposed to the internet. There a bots, misconfigured services, compromised iot devices doing all sorts of things. Nothing to worry.

Generally, I am wary of putting this information for general use (and even in docs) because many things can go wrong . So, please, if you care about the data, don't hesitate to contact us on support@ . We help regardless of the subscription plan.

@girish thanks a lot for your answer.i appreciate.

@humptydumpty haha! whoops - on it - great find!!!

@nebulon I enabled remote debugging and emailed, look forward to hearing back

@msbt the old LAMP app will be left as-is. So, no change to that in the foreseeable future.

@austinsonger this may happen if the server is a bit overloaded or if the disk I/O is slow. The latter can be quickly checked with hdparm -Tt /dev/<your-root-disk-partition>. Otherwise the blog seems to be up and running fine by now?

@nebulon @girish @d19dotca Thank's a lot @d19dotca ! For me is a little bit complex append that command in cronjob and I don't know if Cloudron make some integrity test at boot time to try to check if turn is on or off. Another solution is to use VPS provided firewall to lock that doors... But as @nebulon wrote, one improvement could be add rate-limiting and/or start that services on demand. Thank's all for your answer

@martinkbs it will be good to have documented the tested rclone setup as part of the documentation!

Ubuntu notice - https://ubuntu.com/security/notices/USN-4891-1

I've synced the expiration now to 7 days to keep changes low until we have a reason to change it Instead of making it configurable I would prefer a sensible default, since so far no-one else has complained.

Ok, thanks

@girish easy enough!

@brutalbirdie Thank you, I'll give that a shot!

@stoccafisso I think I am able to reproduce this in one of our managed Cloudrons. Looking into the fix.

how embarrassing. You're absolutely right. I was searching after ghosts.

I will mark this as solved for now but also ack that there is possibly some bug either on minio side or Cloudron side.

@vladimir Usually for LAMP app, we tend to create separate apps. i.e LAMP 7.3, 7.4 and in the future 8, are totally separate apps. So, your app won't update automatically. For addons which are shared across apps, we don't have a way to do this. I guess one idea is to have the app "pin" itself to a specific mysql version and that way we will have multiple mysql databases with different versions running in parallel. Doable but quite complicated! I think @luckow also reported that MySQL 8 broke his drupal app. Good news is that I don't expect such a big upgrade any time soon.

@girish I guess I'm wondering though why it'd say "Not available yet"... is that because I had restarted the server a few hours earlier? I don't normally notice that though when I restart, it usually still shows data. Is it possible there's a bug here? If the restarts are losing that data, then I'd think that's a bug, right, if it shows for some services but not all? To me that makes it seems like it's either not completing properly when it runs and that could maybe explain why it shows values for some but not all, or perhaps it's losing data when it should be remembering it. My gut tells me there's a bug here. Or am I way off? I guess it's okay since we have a workaround to run that command when it happens, my brain is just wondering why it happened in the first place and how it could be prevented.