Cloudron Forum

Rocketchat group calls are also using Jitsi, so including that would be a big plus for us.

This appears to be a case of https://forum.cloudron.io/post/6533 . Applying the linked setting change fixed the issue.

Is there, or is there planned to be, a way to restrict an OpenID Connect provider to members of a certain group?

Specifically, we have a web site hosted outside of Cloudron, that it would be great to use our Cloudron accounts to control user access to. OpenID Connect (and other OAuth variants) are supported, so Cloudron just coming out with a Provider, is promising. But we want to restrict it to a particular group of users.

For some of our users, their SMTP connections are being denied, with:

902 Host names have more than one DNS label

This error appears to come from https://codeclimate.com/github/msimerson/Haraka/plugins/helo.checks.js/source

I don't know how to walk them through finding out what HELO their device is sending to validate it, but it seems related to the plugin.cfg.reject.valid_hostname setting. Did this change in 5.0.3 ?

@girish Thank you, the workaround worked.

I grabbed out the certs that were there before. I don't know if it would help to attach them, but they look like standard Lets Encrypt Authority X3 issued certs.

@girish said in Backups failing with ERR_STREAM_WRITE_AFTER_END:

npm install git+https://github.com/cloudron-io/aws-sdk-js.git#continue_once

This has worked for me.

Just as a note, I had to su yellowtent rather than sudo, as NPM kept complaining about root owned cache files (since HOME was still pointing at /root/). Just in case anyone else needs to follow these instructions.

One of our Nextcloud installs broke in package update 4.21.* , with all users files not being visible in the UI. Also the external mount (A Linode object store using the S3 interface) gave errors when trying to access it. These are the updates that moved from Nextcloud 27 to Nextcloud 28. The disk usage shows the same amount of usage as before, so I expect the files are still present in the container.

Going back to the last backup of version 4.20.6 update restored all the files, so everything is currently "fine", but it'd be nice to know why it broke.

Interestingly, a newer Nextcloud install on Cloudron has updated without issue.

So I'm guessing some deprecated functionality is still being used by our install, from possibly years ago, and it was removed in this update. However, I don't have any idea what it was, or if it was part of the Cloudron packaging or part of the Nextcloud update. Nextcloud's changelogs are not great to read, and I haven't found any kind of migration guide for Nextcloud 28.

Does anyone who is familiar with Nextcloud have any ideas where I should start looking?