Cloudron Forum

@joseph good idea. Thanks for the support.

Thank you for the feedback.
Kuma has only been running for 3 months. The database is about 800 MB in size and cannot be reduced in size via the settings. I have now reduced the data retention to 100 days. Since I have seen the problem several times in the last few weeks, I don't expect this to solve the problem.

I have about 50 monitors running. Monitoring is reliable, notifications are coming in.
However, the web UI regularly crashes after a little longer uptime (haha!). Then the entries/monitors are not updated, or are missing, or the whole app is not loaded.
Browser Reload does not help, Server Restart does.
The log is unremarkable. I couldn't find any comparable reports in the forum yet. Am I the only one with this problem?

@jdaviescoates

Thank you very much.
Absolutely right, that helped me.
ONLYOFFICE Docs 8.1.3 Package Version com.onlyoffice.coudronapp@1.17.2 restore from backup works. But updates then fail.
So I installed the latest version directly from the app store, changed the secret and made the corresponding changes in Nextcloud (/settings/admin/onlyoffice). So just a whole restart. You really don't lose anything.
Now it's running again. Thanks.

I have had an unclear problem for two days: OnlyOffice App throws error 502, not responding.
Restarting, recovery mode etc. has not helped. Logs are not revealing (to me).
Currently there is an update to package 1.18.2, but this may not be installed due to the error and cannot be triggered manually.
Does anyone have any ideas?

Nov 13 08:53:36 - [2024-11-13T07:53:36.378] [ERROR] [localhost] [docId] [userId] nodeJS - DB table "task_result" does not contain columns: created_at,password,additional, columns info: change_id,status,status_info,last_open_date,user_index,tenant,callback,baseurl,id
Nov 13 08:53:40 - 2024/11/13 07:53:40 [error] 124#124: *1 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /healthcheck HTTP/1.1", upstream: "http://[::1]:8000/healthcheck", host: "onlyoffice.example.com"
Nov 13 08:53:40 - 2024/11/13 07:53:40 [error] 124#124: *1 connect() failed (111: Unknown error) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /healthcheck HTTP/1.1", upstream: "http://127.0.0.1:8000/healthcheck", host: "onlyoffice.example.com"
Nov 13 08:53:40 - 172.18.0.1 - - [13/Nov/2024:07:53:40 +0000] "GET /healthcheck HTTP/1.1" 502 150 "-" "Mozilla (CloudronHealth)"
Nov 13 08:53:40 => Healtheck error got response status 502

Thanks for the tip, I have entered it there: https://forum.mattermost.com/t/online-offline-status-indicator-in-the-mac-app-broken/19481/3

My problem is probably a bit off-topic as it only relates to the desktop app (Mac). However, nobody else seems to have the problem and it has only occurred very recently and without updating the app. So I'll try my luck here!

In the desktop app, the user's online status (green tick next to the profile picture) has only been displayed as ‘offline’ for a few days now.
If the user is logged into the browser, the status is displayed correctly both in the browser and in the app. However, if the user is only logged into the app, the status is marked as offline. Manual changes to the status are only retained until the next reload/restart of the app.

Reinstalling, updating the app, clearing the cache and restarting the server have been tried. Without success.
I can't find anything in the server logs, in the app logs or in the app's Dev Console. No comparable case can be found on Google, on Github (desktop app), there is only an older issue for the Windows app.

Is it the same for others? Does anyone have an idea?

Desktop App version 5.9.0 (but also 5.2.2), server version 9.10.1., Cloudron Package Version 2.2.0

I am a big fan of Statamic CMS.
A bit similar to Grav, but better in my opinion. Based on Laravel (i.e. PHP), can be used with or without a database (flatfile first), headless/JAMstack or classic, suitable for small or very large sites, great maintenance backend for editors, well documented, easy to update ...

and to mention it again: a Netdata installation could run in the OS of the Cloudron host system like on any other server, which sends metrics to a Netdata Cloudron app via a configured stream.conf. In this case, everything would remain isolated. But of course you would have to test it!

@girish said in netdata - real-time monitoring:

The add node button was disabled and it asks me to go to the cloud.

This is also part of the dark pattern. If you are logged into the cloud, you will find instructions on how to add nodes behind this button.

As far as I understand it correctly (I wouldn't call myself a professional either!), Netdata basically works as follows:
There is ONE application that can:

1. monitor its own host system and output the result on a web interface. This is the case that you obviously have on your computer now.
2. alternatively, every Netdata application can also send data (additionally or exclusively) to other nodes. This is where Netdata's advertising comes in. If you want more than an unsecured output via port 19999 on the system to be monitored, you should preferably go to the cloud and pay! But it also works without a paid cloud, just not as convincingly.
3. or the Netdata installation acts as the master (or parent node) processes the data from other nodes (child nodes). In other words, it can display, act, send alarms, etc. That would be the variant that I could very well imagine as a Cloudron app. In this case, however, the child nodes are not added via the UI of the master, but via an entry in stream.conf on the sending Netdata. As soon as the master receives data, the UI changes slightly and you can switch between different nodes.

This is explained quite clearly at https://www.netdata.cloud/blog/netdata-parents-streaming-replication/.

It is also important to know that Netdata should always run behind a proxy: https://learn.netdata.cloud/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/

@girish

I understand what you mean, basically these are exactly the points I suspected at the beginning.

However, I probably expressed myself incorrectly in option 2. You can also operate a master with the current UI that displays all nodes together or individually. That's quite a lot! You get very detailed and precise information about what is currently running (or not) on a server. The alarms are also very helpful. You can manage them centrally with a central node. Hard disks or SWAP that are full, RAM problems and even DDos can be recognised.
However, you have to live with the fact that the login button goes to the cloud and functions such as the war rooms only work there. This is somewhat confusing and could be unsatisfactory for Cloudron users.

So my conclusion: this can make sense on Cloudron. It is a popular tool and, in my opinion, one of the best in the area of server monitoring. I would use the app.

Option 1:
you could of course also treat the Cloudron server as a child node. Then the app has no direct access to the host system. Simply install the agent normally on the shell and have the metrics delivered to a possible app (option 2). This would just be option 2 + two lines in the documentation.

Yes exactly, that's what I described above. Everything goes to the Netdata cloud! This is very confusing at first. However, as I said, you can still run Netdata as a master node and then carry out the analysis for many agents in one place. However, I still use the old UI for this, which can be called up with monitoringmaster-example.com/v1/. Here you then have a sidebar and can call up the individual nodes. As I want to monitor individual servers and not a connected server farm, this exactly covers my use case.

But back to the Cloudron use case.
As mentioned above, I see two possibilities:

1. the app is used to monitor the Cloudron server/hardware. That would already do a lot: Hard drive, ram etc. there is also a Docker plugin which provides various insights into the containers running on the machine.
2. the use case described above: the app is a masternode and receives the metrics from child nodes (any web server). The advantage would be that you have the monitoring in one place and do not have to use the Netdata Cloud. Compared to a self-installation, another advantage would be that I could clarify the security (htpasswd?).

I would be delighted to see Netdata in Cloudron.
I have been using Netdata for many years now for about 50 servers.
My experience:
Netdata is a great tool for analysing the load on a machine, in real time or in the aftermath of a problem. Netdata itself is relatively resource-efficient.
Initially, I was irritated by the fact that the UI is very much geared towards using netdata.cloud. For example, there is a conspicuous "log in" button that takes you directly to the cloud (which has been payable for a few months now). Once you have registered the agent there, it is not so easy to get it out.
What is perhaps not so clear from the documentation is that the agent to be installed on the client can also act as a master and collect data from many clients. And completely without netdata.cloud.
As the Netdata UI is publicly accessible in the opensource version, protection via proxy is recommended, similar to https://learn.netdata.cloud/docs/netdata-agent/configuration/running-the-netdata-agent-behind-a-reverse-proxy/nginx

However, the question for me is in what context Netdata should be integrated into Cloudron. As an agent in the apps? As an agent on the host system? As a "monitoring master" app to monitor other servers/containers?

Many thanks for the quick help and the detailed explanation.
As I said, the problem occurred when emptying the trash. I assume that many workers are being requested here.
I have increased MaxRequestWorkers from 15 to 100 and slightly increased the RAM allocated to the app.
As far as I could test now, the problem seems to be solved.

Hi there,

for some time now, I have noticed that the Nextcloud GUI freezes for a few minutes. Recently I wanted to empty the trash.

The log shows the following error.

[mpm_prefork:error] [pid 1] AH00161: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting
=> Healtheck error: Error: Timeout of 7000ms exceeded

The problem has already been discussed in the forum with other apps, but always without a conclusive result.

I'm using "User management" with "Only allow the following users and groups". But "Allow all users from this Cloudron" makes no difference anyway. "Dashboard visibility" is not available as an option

No. Just the remember me an the sign in.

Hello to all,

I just realised today that I can no longer log in to my Matomo installation.
Not with any of the Cloudron users.

As I only log in from time to time, this may well have been the case for some time.

I currently have the app 1.44.1 (Matomo 5.0.1) installed. Two week ago, version 1.42.0 was switched to OICD. That could be the problem.
Unfortunately there is nothing in the log. Only a 403. The error message in the login frontend is "Error: Username and/or password is not correct."
Does anyone know a solution?

@nebulon maybe because you use Linux? Unfortunately, the support there is still very poor, but it looks much better on other devices. https://www.passkeys.io/compatible-devices

Hello,
I just wanted to emphasise that this topic is super important.
Now that all browsers and the big tech giants support the topic, more and more websites are offering passkey as a secure and very convenient authentication method. At the latest after Amazon offers passkey as a password replacement (https://www.theverge.com/2023/10/23/23928589/amazon-passkey-support-web-ios-shopping-mobile-app), the topic has finally arrived on the broad market.

I see two areas of interest for Cloudron here:

1. cloudron apps with keypass (as 2fa or also as 1fa)
2. app for developers such as Hanko.io=> https://forum.cloudron.io/topic/8375/hanko-io-fido2-webauthn-passwordless-login