Cloudron Forum

Looks like it's an issue with the Photos app itself. Hopefully it will be fixed soon.
Github

@james As I mentioned, Nextcloud suddenly came back online, but the Photos app still doesn’t work.
It’s possible that the issue is on Nextcloud’s side, but I’m not sure.

Anyway, thank you very much for the quick response!

Well, mystery solved (maybe) – I’ve been struggling with this for two hours, and suddenly I got an email that the app is back online.
No idea what was wrong.

All of this started because the native Photos app in Nextcloud refuses to load or add any folders that contain photos.

@james Hello,
thank you for the quick reply. This is all I have in the logs for now:
log

Hello,

after restoring the Nextcloud app (from a previous backup), the application enters the Not responding state.
The logs only show repeated health check failures:

Jun 12 08:39:55 Config value were not updated
Jun 12 08:39:55 ==> Run cron job on startup
Jun 12 08:40:00 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:40:10 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:40:20 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:40:30 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:40:40 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:40:50 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:41:00 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:41:10 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:41:20 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:41:30 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:41:40 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:41:50 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:42:00 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:42:10 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:42:20 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:42:30 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:42:40 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:42:50 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.58:80
Jun 12 08:42:55 13:M 12 Jun 2025 06:42:55.468 * 10000 changes in 60 seconds. Saving...
Jun 12 08:42:55 13:M 12 Jun 2025 06:42:55.469 * Background saving started by pid 26
Jun 12 08:42:55 26:C 12 Jun 2025 06:42:55.480 * DB saved on disk
Jun 12 08:42:55 26:C 12 Jun 2025 06:42:55.481 * Fork CoW for RDB: current 1 MB, peak 1 MB, average 0 MB
Jun 12 08:42:55 13:M 12 Jun 2025 06:42:55.569 * Background saving terminated with success

Just to add:
We mainly want to test if the custom config for respekt.cz works correctly (including login support).
If it does, we plan to submit a pull request to Wallabag’s graby-site-config so it could be included in future releases.

Thanks again!

Hi,
we're using Wallabag and I'd like to add a custom site configuration file for the website respekt.cz, which requires login due to a paywall.
Wallabag usually loads these configs from:

vendor/j0k3r/graby-site-config/sites/

On Cloudron, however, this directory is read-only, so I can't manually add a new file like respekt.cz.txt.

Is there a supported way to include custom site configuration files in Wallabag on Cloudron?

Thanks a lot for any guidance!

@nebulon Thanks a lot for the quick fix – just updated the app and everything works perfectly now.
Really appreciate the fast response and great support!

@nebulon said in Walabag – Error 500 when trying to reset password:

I was able to reproduce this. Apparently wallabag moved to some new config variables mailer_dsn: 'smtp://127.0.0.1'

We have to fixup the package

Thanks a lot for looking into this and confirming the issue!

Good to know it's not a misconfiguration on my side. I’ll wait for the updated package with the fix.

Thanks again for the quick response and great support.

Hi,

I'm getting a 500 error when trying to reset the password in my Walabag instance on Cloudron. Has anyone experienced something similar?

Do I need to configure anything manually in Walabag to make password reset work?

Thanks a lot for any help!!

[23/May/2025:09:54:17 +0000] "POST /resetting/send-email HTTP/1.1" 500 4524 "https://read.oscloud.cz/resetting/request" "Mozilla/5.0 (X11; Linux x86_64; rv:138.0) Gecko/20100101 Firefox/138.0"

This is not a Cloudron issue — it appears to be a bug in PeerTube itself.
The issue has already been reported and confirmed by the developer:

Hi,
I’m not sure if this is related to the Cloudron update to version 8.3.1, but I’ve encountered an issue in the PeerTube app.

When I try to edit an existing user to increase their video quota (e.g. max upload size), after clicking Save, I get the following error:

User with this email already exists

However, I’m not changing the email address – only the quota field.
I’ve tested this in different browsers (Firefox, Vivaldi, incognito mode), but the result is always the same.

Backend returned code 409, errorMessage is: User with this email already exists.

@nebulon Wow, everything is working now! Thank you so much for your time and for fixing the app.

Just a quick question – for connecting a Nextcloud instance running on a different server, is it enough to just add the IP address of the server where Collabora is running to the WOPI allow list?

@LoudLemur You don't need to modify any files. Just go to:

Admin settings → Sharing → Sharing Privacy settings → Disable user email address auto-completion

Once this is disabled, other users will no longer see email addresses when sharing.

I also tried a fresh Nextcloud installation. My first Nextcloud instance is on the main domain, so I thought that might be the issue, but even with the new instance I have the same problem.

After restarting the Collabora app, the same error appears again.

It seems like someone had a similar issue here

@nebulon Hi,
I tried the demo instance of Collabora, but after a restart, I get the same error. I must be doing something wrong, but I really don't know what.

I logged into Collabora and added my two Nextcloud domains: app1.demo.cloudron.io|app2.demo.cloudron.io. After a restart, I can no longer connect.

At least now we know that the issue is somewhere on my side.

@nebulon No, I haven’t manually modified any configuration files. Everything was set up through the Cloudron interface.

I have tried reinstalling Collabora multiple times, even on a different domain, but the issue persists. After installation, it works fine, but after a restart, it stops responding.

The only changes I made were increasing the memory allocation and connecting multiple Nextcloud instances.

@nebulon After restarting Collabora Online, I checked the logs and found the following errors:

connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: , request: "GET /hosting/discovery HTTP/1.1", upstream: "http://127.0.0.1:9980/hosting/discovery"
Failed to initialize COOLWSD: SSL context exception: Error loading private key from file /etc/coolwsd/key.pem: error:8000000D:system library::Permission denied
sh: 1: /usr/bin/coolmount: Operation not permitted

It seems like Collabora Online fails to properly start after a reboot. Could the SSL certificate issue or permission errors be causing this? Any suggestions on what to check next?

@nebulonThe "Memory Limit" setting in this case refers to the RAM allocation for Collabora Online in the Cloudron Dashboard.
Initially, the application was running with 1GB of RAM, but I increased it to 3GB to see if it helps with stability.

The only relevant issue I found is this one
but I’m not sure if it’s the same problem.

Unfortunately, I don’t have much experience with this.

@nebulon The application seems to work normally right after installation.
I tried connecting two Nextcloud instances – one on the same server as Collabora, and another on a different server.

When I add the "Memory Limit" application, after a restart, Collabora stops working, and I can no longer connect.

I also tried keeping only the instance that is on the same server as Collabora, but it only works until the next restart.

I’m not sure if it’s related, but the only errors I found in the logs are:

2025-03-17T20:08:05.532Z box:dns/cloudflare upsert: Adding new record fqdn: _acme-challenge.collab.example.com, zoneName: example.com proxied: false
2025-03-17T20:08:07.644Z box:dns/waitfordns isChangeSynced: NS damon.ns.cloudflare.com errored when resolving _acme-challenge.collab.example.com (TXT): Error: queryTxt ENOTFOUND _acme-challenge.collab.example.com
2025-03-17T21:11:21+01:00 Failed to initialize COOLWSD: SSL context exception: Error loading private key from file /etc/coolwsd/key.pem: error:8000000D:system library::Permission denied