@zylstra This is built into Cloudron - https://docs.cloudron.io/networking/#dynamic-dns . If you use a programmatic DNS provider, Cloudron will keep the DNS updated.

It's also throwing PHP notice errors, might be related to .well-known parts not being in place ?
https://paste.armada.digital/cuqodoxago.pl
This errors output when one try to visit one's Solid profile :

https://cloud.domain.com/apps/solid/@rick/

I should probably report this upstream since this does not seem related to the cloudron distribution branch 🙂

got the same issue with one of my nextcloud's, even after removing the app, I could not restore the app to normal state, in the end, I noticed Circles app was throwing errors, disabled with

sudo -u www-data php occ app:list

sudo -u www-data php occ app:disable circles

Update: all previously disabled apps now running flawlessly after the latest 22.1.1 update. The new "Voice Messages" feature in Talk/ Spreed is delightful!

@luckow Thanks for this - very handy.

It didn't fix the issue I had with folder sharing with the "Everyone" Group/Plugin, but difficult to tell as I tried what you suggested first.

Then it was only fixed when user's logged out and back in again, so maybe that was all that was needed, I can't be sure, but had disabled and re-enabled the Everyone Group plugin anyway.

@nebulon Thanks for helping me work through this!

@avatar1024 said in Nextcloud 22 is out:

So wouldn't it make sense to push that one instead?

Yes, 22.1.0 will come as well. Hopefully, next week. Currently, we are still pushing out 22.0.0.

@nebulon said:

did you maybe share the calendar as read-only?

No they're normal calendars.

@d19dotca said:

Do you happen to see this issue if using a more supported macOS version (11.x "Big Sur" and lower?) with the built-in Calendar app?

Yes, I was having this same problem with Big Sur. Seeing the problem was still there in Monterey actually prompted me to look into it more.

@girish perfect, thank you

@vladimir-d OK thanks, I will take this into account when trying to add cron support (or equivalent) for 6.4

@amg-web I mean the recovery mode, which you can enable for the app in the "Repair" section on the app configure view in the Cloudron dashboard.

@girish I ended up migrating back to my home server a lot faster than I thought and so this is no longer an issue but when I forgot I went from a machine with 32GB of RAM to a VPS with 2 so this was likely it. When I first installed Cloudron is was randomly shutting down and failing to restore becuase it was running out of RAM.

I found a couple of similar issues - https://github.com/ONLYOFFICE/DocumentServer/issues/33 and https://github.com/ONLYOFFICE/Docker-DocumentServer/issues/96

Can you check the below:

Are the certs for the onlyoffice installation valid? Give the onlyoffice app more memory.

@necrevistonnezr
I use both for on prem storage and for wasabi storage

@necrevistonnezr It is, I skimed the start of that thread, and as it was unrelated, I just assumed it was not about my issue.

@timconsidine

@privsec : are these problems stem-ing from the encruption plugin ? Rather than Nextcloud itself.
I have used NextCloud for 5+ years and I struggle to remember any problems at all.

It is certainly possible. I really don't want data stored unencrypted but it is looking like that is the only option.
All my data is stored on Wasabi, and they do have data stored at rest, but they store the encryption keys in meta data (from what I recall)

@necrevistonnezr

Rarely problems, and if any, I was able to solve them via the occ tool - thought I stayed away from encryption as my server is at home with nextcloud on an encrypted home folder so I don't need e2e encryption on top of that.
Also, activate only the really necessary addons.

Ill have to look into the OCC tool, hopefully all my data isn't lost.

@jagan I think in your case, the issue was with the google external storage primarily. I think there is a general issue with plugins where whenever nextcloud updates they are slow to catch up and something fails.

@robi Looks like non-cloudron users hit the same issue - https://github.com/nextcloud/server/issues/13556#issuecomment-848314122

The root cause is that the nextcloud package is configured to log to the console (stdout / stderr) instead of a file. Nextcloud tries to open the stdout/stderr and this fails. Ideally, nextcloud can show a graceful error message that logs cannot be viewed from inside the app because it is logging to the console. Workaround is to use the cloudron logs viewer to view the logs - which IMO is the correct place to view logs (for all apps and not just nextcloud). After all, if the app is not working, one cannot view the logs within itself.