- Update InvoiceNinja to 5.1.43
@robi I've updated the package now to check the actual teamspeak daemon is running for the healthcheck, as well as restarting for longer. This should hopefully solve your case as well.
@jdaviescoates that service (graphite+collectd) collects the data used in the graphs, like memory usage over time. Given that it causes issues from time to time and also we don't really utilize it well, we are thinking of maybe collecting the data on our own and ditch graphite.
Hi! Oh right, for the branding we have to update the pricing page there. All branding, regarding the Cloudron dashboard is available in the premium plan. Essentially you can change the main icon/favicon, the footer, the name shown in all places and some templates. More info at https://docs.cloudron.io/branding/
Regarding the apps, this very much depends on the app itself how much branding it supports.
@imc67 at least on our main instance with 4 mailboxes, we don't see this error but every once in a while some other imap related connection issues. Those do look like temporary problems with the mailserver communication. Things are retried also. If you can consistently reproduce this, maybe it is worth contacting the upstream authors and see if they have more insight here if this is an app/server/connection issue.
I can also see the warning on fresh installs, however after adding a client and sending an invoice, eventually it goes away.
Thing is the actual tasks it refers to are running and get handled by the laravel queue which is active as described in https://laravel.com/docs/8.x/queues#supervisor-configuration
Also hitting the "Refresh Data" shows the tasks being run in the logs, however that notification is not immediately dismissed.
Thanks for the logs. This is interesting, since the first failing log indicate that the TeamSpeak process is being restarted at least twice.
So I think there are two fixes required:
The defaults are not always a good fallback. Not many people actually know that they could adjust their system (not even many about those who rely on assistive technologies). When we avoid touching the way the defaults do the styling (e. g. outline) we can still do a lot for accessibility
so we are on track here, I've added the darker outline, but the native one is still inset of that. I have not restyled this (not visible in the screenshot, as real focus went to the screenshot tool )