Cloudron Forum

I stumbled upon OpenTrashMail since it is able to convert newsletter mails into subscribable RSS feeds. I would really like to separate newsletters from my mail inbox. OpenTrashMail seems to do the job. Any new considerations?

I am also interestedin using WriteFreely via Cloudron.

Thank you very much for resolving the issue. I would love to understand what i did wrong.

I tried deleting the nginx.conf and certs and let them be regenerated as you have described in other threads. Yet I did not manage to get nginx back up and running. Are there additional steps besides deleting cofings, restarting box, nginx and unbound?

Muchas Gracias for saving the day!

Now that Castopod has reached v 1.0 can we have it on Cloudron? That would be excellent. I wish I could help but I am not a programmer.

Alternatively, people who installed Castopod on LAMP-stack, is anyone willing to write a short tutorial?

Is it possible to grant access to a non-administrator to monitor the status of a backup volume and system info?

The only option seems to be to escalate the user's status to an administrator. This would bring dangerous privileges to the user who only wants to check if backups are running properly once a week.

I used an API call to get a list of backups in Grafana. The API does not include a status variable as it seems? I am referring to the green (or red) dot next to the backup volume.

Exposing backup status and volume statuses via API would do the trick as well.

Any tips?

Just updated the last working version to the newest package. Everything is fine. I guess the cause was the strange group provisioning confusion I caused.

Smooth ride so far.

@girish

I hope this is the right place. This is a minor one but it would be comfy: An option to delete accidental local backups from the UI. The scenario occurs when no backup volume is configured and backups are on, which if remembered correctly is the default.

The way to get rid of local backups right now involves ssh-ing into the server and manually deleting the files.‬

Has anyone successfully installed it DIY on Cloudron?

Thanks, it works.

@nebulon So throwing off the unused linux images and restarting unbound helped. Consider it solved. Thank you.

I have searched the forum for a similar case and found this one. Link to the solution:

https://forum.cloudron.io/post/70404

I have the exact same log errors. The problem is that I have no backup to restore a working config.php file from.

What to do in this case? Will it help to make a backup of the current non-responding Nextcloud, install a fresh one and recover from the former backup?

I am out of ideas. Help appreciated.

Running the app in recovery mode gives me the following:

Jan 07 20:51:02 Command "upgrade" is not defined.
Jan 07 20:51:02Nextcloud is not installed - only a limited number of commands are available
Jan 07 20:51:05[GET] /healthcheck
Jan 07 20:51:05box:tasks update 4766: {"percent":30,"message":"Setting up addons"}
Jan 07 20:51:05box:services setupAddons: Setting up ["postgresql","sendmail","ldap","redis","localstorage","scheduler","turn"]
Jan 07 20:51:05box:services setupAddons: setting up addon postgresql with options {}
Jan 07 20:51:05box:services Setting up postgresql
Jan 07 20:51:05box:services Setting postgresql addon config to [{"name":"CLOUDRON_POSTGRESQL_URL","value":"postgres://user1af67d47f12d4d8b9890304a9c7e915b:30234061fc3bfa5e3c9c8f6d760fee506c9d6cb66069523f6c00ea7bb4addd9c4fb5f942c853d832967cee25d5b42d08eb3e2c766bc13954f0bd54459685c9d9@postgresql/db1af67d47f12d4d8b9890304a9c7e915b"},{"name":"CLOUDRON_POSTGRESQL_USERNAME","value":"user1af67d47f12d4d8b9890304a9c7e915b"},{"name":"CLOUDRON_POSTGRESQL_PASSWORD","value":"30234061fc3bfa5e3c9c8f6d760fee506c9d6cb66069523f6c00ea7bb4addd9c4fb5f942c853d832967cee25d5b42d08eb3e2c766bc13954f0bd54459685c9d9"},{"name":"CLOUDRON_POSTGRESQL_HOST","value":"postgresql"},{"name":"CLOUDRON_POSTGRESQL_PORT","value":"5432"},{"name":"CLOUDRON_POSTGRESQL_DATABASE","value":"db1af67d47f12d4d8b9890304a9c7e915b"}]
Jan 07 20:51:05box:services setupAddons: setting up addon sendmail with options {"supportsDisplayName":false}
Jan 07 20:51:05box:services Setting up SendMail
Jan 07 20:51:05box:services Setting sendmail addon config to [{"name":"CLOUDRON_MAIL_SMTP_SERVER","value":"mail"},{"name":"CLOUDRON_MAIL_SMTP_PORT","value":"2525"},{"name":"CLOUDRON_MAIL_SMTPS_PORT","value":"2465"},{"name":"CLOUDRON_MAIL_STARTTLS_PORT","value":"2587"},{"name":"CLOUDRON_MAIL_SMTP_USERNAME","value":"wolke@tee-server.de"},{"name":"CLOUDRON_MAIL_SMTP_PASSWORD","value":"6257492a4e30247b589fefb907b9e8b4d5bdf3396d2c5914"},{"name":"CLOUDRON_MAIL_FROM","value":"wolke@tee-server.de"},{"name":"CLOUDRON_MAIL_DOMAIN","value":"tee-server.de"}]
Jan 07 20:51:05box:services setupAddons: setting up addon ldap with options {}
Jan 07 20:51:05box:services setupAddons: setting up addon redis with options {}
Jan 07 20:51:05box:services Re-using existing redis container with state: {"Status":"running","Running":true,"Paused":false,"Restarting":false,"OOMKilled":false,"Dead":false,"Pid":42957,"ExitCode":0,"Error":"","StartedAt":"2024-01-07T11:40:56.222621687Z","FinishedAt":"2024-01-07T11:40:55.251426628Z"}
Jan 07 20:51:05box:services Waiting for redis-1af67d47-f12d-4d8b-9890-304a9c7e915b
Jan 07 20:51:05box:services setupAddons: setting up addon localstorage with options {}
Jan 07 20:51:05box:services setupLocalStorage
Jan 07 20:51:05box:shell createVolume spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/mkdirvolume.sh /home/yellowtent/appsdata/1af67d47-f12d-4d8b-9890-304a9c7e915b/data
Jan 07 20:51:05box:shell createVolume (stderr): sudo: unable to resolve host 1001415-406: Name or service not known
Jan 07 20:51:05box:services setupAddons: setting up addon scheduler with options {"housekeeping":{"schedule":"*/5 * * * *","command":"/app/pkg/cron.sh"}}
Jan 07 20:51:05box:services setupAddons: setting up addon turn with options {"optional":true}
Jan 07 20:51:05box:services Setting up TURN
Jan 07 20:51:05box:tasks update 4766: {"percent":60,"message":"Creating container"}
Jan 07 20:51:05box:apptask createContainer: creating container
Jan 07 20:51:06Repair mode. Use the webterminal or cloudron exec to repair. Sleeping
Jan 07 20:51:06box:shell addLogrotateConfig spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/configurelogrotate.sh add 1af67d47-f12d-4d8b-9890-304a9c7e915b /tmp/1af67d47-f12d-4d8b-9890-304a9c7e915b.logrotate
Jan 07 20:51:06box:shell addLogrotateConfig (stderr): sudo: unable to resolve host 1001415-406: Name or service not known
Jan 07 20:51:06box:apptask startApp: starting container
Jan 07 20:51:06box:tasks update 4766: {"percent":100,"message":"Done"}
Jan 07 20:51:06box:tasks setCompleted - 4766: {"result":null,"error":null}
Jan 07 20:51:06box:taskworker Task took 9.183 seconds
Jan 07 20:51:06box:tasks update 4766: {"percent":100,"result":null,"error":null}
Jan 07 20:51:10=> Healtheck error: Error: connect ECONNREFUSED 172.18.19.126:80```

Solution:

./bin/tootctl media remove

has an option

--days

which defaults to 7 days of not set.

Our instance is only 3 days old. Since i did not set the flag it defaulted to 7 days.
The system did everything right. There were no files as old or older than 7 days. Accordingly it did not delete anything. Computer smart.

I was able to delete the cached media files.

I am running the latest version of Nextcloud on a Cloudron instance. Periodically the app gets unresponsive. It is shown as "Running" in the dashboard but is not functional on front end and sync. The only thing I found in the logs is the following. This coincides with the unresponsiveness. As these messages are not very descriptive, I am not sure what to do here. I already switched off all unused nextcloud plug ins. The Instance is small and only used by a handful of people. No heavy load, mostly syncing text files between 6 machines. CPU and RAM are rarely fully utilized.

It does not fix itself. The app needs to be restarted manually.

=> Run cron job
ldap undefined
ldap undefined
localstorage undefined
localstorage undefined
postgresql undefined
postgresql undefined
redis undefined
redis undefined
scheduler undefined
scheduler undefined
sendmail undefined
sendmail undefined
turn undefined
turn undefined

@jdaviescoates I had this thought. I consulted other Mastodon admins. They say, they can delete everything. This should not occur.

@joseph We are already up-to-date on a live Nextcloud. Thankfully problem 1. only affaects 5 accounts so far. We will manually transfer those to Cloudron.

A nice option would be to customize the text of the "Login with Cloudron" button and the info text shown above. Or, even better, a redirect to Cloudron's login form without a need of the button to begin with.

In a non-Docker installation it is apparently found under

config/settings.yml

and should look like this:

reserved_usernames:
  - admin
  - support
  - help
  - root
  - webmaster
  - administrator
  - mod
  - moderator

It would be good if admins were able to control this list.

Never mind but if you happen to get yourself into a similar situation, do the following in the Nextcloud app's terminal:

sudo -u www-data php -f /app/code/occ group:adduser admin <username-of-existing-account-to-be-admin> -n

This way the native Nextcloud group "Administrators" reappears and the account is granted admin rights.

@nebulon Thanks! If that´s the case, we will be patient and wait for it to find its way upstream.

@jdaviescoates Yep, I read about it and it made sense. Problem was that I could not even get to the NC OIDC app config due to missing admin rights. thankfully the occ command made the native admin group reappear.

From a logical point of view provisioning admin rights to a certain OICD group should be an option.

This could be a field in the OIDC plugin where we could define a group name that is treated as admin and grants native NC admin rights to users within.