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:

archos
Posts
-
Problem editing user quota – "User with this email already exists" error -
Problem editing user quota – "User with this email already exists" errorHi,
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.
-
Collabora Online stops working after restart (502 Bad Gateway)@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?
-
Nextcloud email addresses are visible by default - how to change setting?@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.
-
Collabora Online stops working after restart (502 Bad Gateway)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
-
Collabora Online stops working after restart (502 Bad Gateway)@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.
-
Collabora Online stops working after restart (502 Bad Gateway)@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.
-
Collabora Online stops working after restart (502 Bad Gateway)@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?
-
Collabora Online stops working after restart (502 Bad Gateway)@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.
-
Collabora Online stops working after restart (502 Bad Gateway)@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
-
Collabora Online stops working after restart (502 Bad Gateway)@joseph Thank you for your response.
I have tried reinstalling the application multiple times. I even installed it on a different domain once.But after every restart, the issue remains the same.
-
Collabora Online stops working after restart (502 Bad Gateway)@joseph I tried opening https://collab.example.com/hosting/discovery in a browser, and I got the same page as before ("This app is currently not responding").
When I try it from the Nextcloud terminal using curl, I receive the HTML code of the Cloudron App Error page, which includes styling and the message:
"This app is currently not responding. Please try refreshing the page in a few minutes."
What should I check next?
Thank you for your response.
[link text](link url)
-
Collabora Online stops working after restart (502 Bad Gateway)Hi, everybody.
I have an issue with Collabora Online on Cloudron. After installation, it works fine—I add the Collabora address in Nextcloud, and the connection status is green.However, as soon as I restart Collabora, it stops working, and Nextcloud reports the following error:
Server error: `GET https://collab.example.com/hosting/discovery` resulted in a `502 Bad Gateway` response: <!DOCTYPE html> <html> <head> <meta charset="utf-8" /> <meta name="viewport" content="user-scalable=no, initial- (truncated...)
Has anyone experienced a similar issue or knows how to fix this? Thank you very much and information
-
Map not displaying in Immich@nebulon I found another error in the browser console that might explain the issue.
When trying to load the map in Firefox, I saw this error:
Uncaught (in promise) Error: {"requestedAttributes":{"alpha":true,"stencil":true,"depth":true,"failIfMajorPerformanceCaveat":false,"preserveDrawingBuffer":false,"antialias":false},"statusMessage":"WebGL is currently disabled.","type":"webglcontextcreationerror","message":"Failed to initialize WebGL"}
The problem was that WebGL was disabled in Firefox. After enabling webgl.disabled = false in about:config, the map in Immich started displaying correctly.
Such a small thing, yet so much work!
If anyone else has the same issue, make sure to check WebGL settings in about:config!
So the issue is resolved! Thanks everyone for the help!
-
Map not displaying in ImmichSorry, but this is a Firefox issue.
There is no problem in other web browsers. I don't know why it doesn't work in Firefox—it has never been an issue before.
I also tried disabling ad blockers, but it didn’t help. Hopefully, the log I sent is okay.
-
Map not displaying in Immich@nebulon Thank you for your response!
I have also tried a fresh installation, but I still cannot see the map. When I click on the map section, I only see a black screen.
In addition, I have the same issue with albums. In the web application, I can only see three albums, while on the mobile app, everything appears correctly.
In the logs, I see the following warnings:eb 21 13:59:04 [Nest] 55 - 02/21/2025, 12:59:04 PM WARN [Api:ServerInfoRepository~nny03ylq] Failed to read /usr/src/app/build-lock.json Feb 21 13:59:05 [Nest] 55 - 02/21/2025, 12:59:05 PM LOG [Api:EventRepository] Websocket Connect: CPs-qtzCVeSNE6wfAAAn Feb 21 13:59:05 [Nest] 55 - 02/21/2025, 12:59:05 PM WARN [Api:ServerInfoRepository~3xkn0m6k] Failed to read /usr/src/app/build-lock.json Feb 21 13:59:05 [Nest] 55 - 02/21/2025, 12:59:05 PM WARN [Api:ServerInfoRepository~e2iale1k] Failed to read /usr/src/app/build-lock.json Feb 21 14:00:52 [Nest] 55 - 02/21/2025, 1:00:52 PM LOG [Api:EventRepository] Websocket Disconnect: CPs-qtzCVeSNE6wfAAAn Feb 21 14:00:53 [Nest] 55 - 02/21/2025, 1:00:53 PM LOG [Api:EventRepository] Websocket Disconnect: TPbCeqJQDnM1ZijwAAAl
-
Map not displaying in ImmichHi,
After one of the recent updates of Immich, I noticed that the map is no longer displaying in the application. Everything seems to be properly enabled in the settings, but the map does not show up anywhere.
Has anyone experienced a similar issue or found a solution? Is there any additional configuration required (such as an API key for maps), or did I miss something during the update?
Thanks for any help!
-
Let's Encrypt Ending Expiration Email Notifications@humptydumpty Hi,
Thanks for the clarification! I tried a manual renewal, and everything is working fine.
I just found it strange because, in the past, I only received these expiration emails for domains I had removed, so I had some doubts. But if Cloudron renews certificates just before expiration, that makes sense now.
Thanks again!
-
Let's Encrypt Ending Expiration Email NotificationsHi,
I have the same issue. I was just about to post on the forum as well. For some domains, I also receive emails from Let's Encrypt saying that the certificate will expire in 5 days, but in Cloudron, everything is green, and it looks like the certificates are active as expected.
I haven’t tried a manual renewal yet, but it seems that Cloudron renews certificates at the last moment.
Has anyone else experienced this, or does anyone know if this is normal behavior?Thanks!
-
Issue Starting NodeBB on Cloudron After Server RestartI tried running the command in recovery mode, and I got the following output in the terminal:
root@630e742c-440d-409a-97ef-45a5161aa337:/app/code# cd /app/code root@630e742c-440d-409a-97ef-45a5161aa337:/app/code# ./nodebb reset -p nodebb-plugin-markdown Warning: Failed to detect linux-musl, fallback to linux-gnu: The "offset" argument must be of type number. Received an instance of Object 2025-01-30T18:38:12.386Z [undefined/19] - error: uncaughtException: ENOENT: no such file or directory, mkdir 'logs' Error: ENOENT: no such file or directory, mkdir 'logs' at Object.mkdirSync (node:fs:1398:3) at File._createLogDirIfNotExist (/app/code/node_modules/winston/lib/winston/transports/file.js:759:10) at new File (/app/code/node_modules/winston/lib/winston/transports/file.js:94:28) at Object.<anonymous> (/app/code/install/web.js:45:3) at Module._compile (node:internal/modules/cjs/loader:1256:14) at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) at Module.load (node:internal/modules/cjs/loader:1119:32) at Module._load (node:internal/modules/cjs/loader:960:12) at Module.require (node:internal/modules/cjs/loader:1143:19) at require (node:internal/modules/cjs/helpers:119:18) {"date":"Thu Jan 30 2025 18:38:12 GMT+0000 (Coordinated Universal Time)","error":{"code":"ENOENT","errno":-2,"path":"logs","syscall":"mkdir"},"exception":true,"os":{"loadavg":[0.46,0.81,0.94],"uptime":44782.76},"process":{"argv":["/usr/local/node-18.18.0/bin/node","/app/code/nodebb","reset","-p","nodebb-plugin-markdown"],"cwd":"/app/code","execPath":"/usr/local/node-18.18.0/bin/node","gid":0,"memoryUsage":{"arrayBuffers":327376,"external":2265472,"heapTotal":30515200,"heapUsed":23418856,"rss":79994880},"pid":19,"uid":0,"version":"v18.18.0"},"stack":"Error: ENOENT: no such file or directory, mkdir 'logs'\n at Object.mkdirSync (node:fs:1398:3)\n at File._createLogDirIfNotExist (/app/code/node_modules/winston/lib/winston/transports/file.js:759:10)\n at new File (/app/code/node_modules/winston/lib/winston/transports/file.js:94:28)\n at Object.<anonymous> (/app/code/install/web.js:45:3)\n at Module._compile (node:internal/modules/cjs/loader:1256:14)\n at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)\n at Module.load (node:internal/modules/cjs/loader:1119:32)\n at Module._load (node:internal/modules/cjs/loader:960:12)\n at Module.require (node:internal/modules/cjs/loader:1143:19)\n at require (node:internal/modules/cjs/helpers:119:18)","trace":[{"column":3,"file":"node:fs","function":"Object.mkdirSync","line":1398,"method":"mkdirSync","native":false},{"column":10,"file":"/app/code/node_modules/winston/lib/winston/transports/file.js","function":"File._createLogDirIfNotExist","line":759,"method":"_createLogDirIfNotExist","native":false},{"column":28,"file":"/app/code/node_modules/winston/lib/winston/transports/file.js","function":"new File","line":94,"method":null,"native":false},{"column":3,"file":"/app/code/install/web.js","function":null,"line":45,"method":null,"native":false},{"column":14,"file":"node:internal/modules/cjs/loader","function":"Module._compile","line":1256,"method":"_compile","native":false},{"column":10,"file":"node:internal/modules/cjs/loader","function":"Module._extensions..js","line":1310,"method":".js","native":false},{"column":32,"file":"node:internal/modules/cjs/loader","function":"Module.load","line":1119,"method":"load","native":false},{"column":12,"file":"node:internal/modules/cjs/loader","function":"Module._load","line":960,"method":"_load","native":false},{"column":19,"file":"node:internal/modules/cjs/loader","function":"Module.require","line":1143,"method":"require","native":false},{"column":18,"file":"node:internal/modules/cjs/helpers","function":"require","line":119,"method":null,"native":false}]}