Cloudron Forum

@robi for the first logviewer mismatch, this is because the first time shown is from the logservice itself and is translated into the local time of your browser, whereas the second comes from the app itself and is just treated as a plain string. Apps normally run in UTC. For the winscp part, I am not sure how winSCP translates timestamps. The folder names are set from server time. I don't think any of this will have anything to do with DB reconnection, if you have any issue there, please make a new entry in the TS forum section with some more info.

@girish I am referring to any that don't need to be written to disk. You can use the lines for what you need in memory.

@girish Yes, in fact I did not understand... To many logs to check with vi

@nebulon clearing the cache did indeed help - thanks @girish

I will put a cache busting hash for the other toplevel pages in the dashboard, just like we have for the main dashboard. This should mitigate that issue for the next release.

This is fixed with https://git.cloudron.io/cloudron/box/-/commit/fe1c483b7819404d4531fd34323bc2fc18534b85 now

I guess some webhook api could be supported. It is a bit of work though and lets first see if this feature is also relevant to more people.

Yes those log lines indicate a login attempt by an app. Each app makes the requests on the Cloudron local network. So different IPs indicate different apps. In your case it looks like someone/bot tries to login to some or your apps.

@girish Thanks for the tip on updating SSH-keys. I wasn't talking about fail2ban reporting, only. I was also referring to the built-in "rate-limiting" of Cloudron (and other security features, e.g. the cloud firewall) where there's currently little or no transparency what's happening. Since Cloudron "takes over the server" I think it would be a good opportunity to add transparent monitoring of the system's security features similar to the "System info" tab...

Nice, thanks @girish

Can you describe the use-case a bit further? Cloudron already collects logs for each application and addon, as well as the Cloudron related platform components. Generally it is not supported to install other daemons on the side of Cloudron on the same server, since we cannot test such configurations during updates. FYI all the logs are collected currently as described here https://cloudron.io/documentation/troubleshooting/#logs

@foliovision you can also try docker system prune -a --volumes but generally I have never succeeded in making that reclaimable space be less than 2GB in any server using docker (even without Cloudron).

For a start, we have added a UI to set the timezone for the next release.

@girish Went ahead and tried it and it works beautifully! Took a matter of seconds for it to load all my feeds. Really appreciate y'all's work on this. I'm becoming a bigger Cloudron fan by the minute