Cloudron Forum

@joseph happy to, can you maybe enable chat so we can do that 1:1?

@joseph sure:

/mnt# node -e "console.log(fs.realpathSync('/mnt/media'))"
/mnt/media

Can only speak for my issue, not a symlink:

/mnt# ls -la
total 12
drwxr-xr-x  4 root root 4096 Jun  9 09:21 .
drwxr-xr-x 23 root root 4096 Dec 17 11:10 ..
drwxr-xr-x  1 root root    0 Jun  9 09:22 media
drwxr-xr-x  2 root root 4096 Dec 17 11:31 volumes

Your command doesn't fail, but doesn't give any output either.

Also getting that message, but on a different use-case. I'm trying to add a (sftp) rclone mount to Cloudron. Mounting and browsing works fine, but when trying to add it as a volume, it says hostPath must be a realpath without symlinks. Is that not supported?

You could just switch to "Manual" provider in the domain settings, that should do it.

Just chiming in here because I ran into a CORS error as well. Solution was not a missing env var, it was activating the workflow - because without that, the URL didn't exist yet and threw the various errors.

I packaged 3proxy a long time ago. It was working fine, but I eventually didn't need it anymore, so it has been unmaintained. It might need some love since many things changed in Cloudron (probably a better way to do healthchecks), but it will likely be easy to update to the latest version and make it work. It could do both, http and socks5: https://git.cloudron.io/msbt/3proxy-app

For me this happens because of the long names of external mounted volumes, they make the container grow so wide that it doesn't fit next to the graphs container. I mentioned it once in a chat with @nebulon but I guess it didn't make the todolist

If you plan to use them for Cloudron, the pitfall might be LXC/LXD. I'm guessing Cloudron doesn't run on that environment.

Yap, sounds like a job for the LAMP app

@nebulon can you also test it it multiple domains? I remember having issues with that a while back

@andreasdueren nice, happy to give it a try, which version did you pack?

A standalone, fully customizable PostgreSQL would be nice indeed, I have a use-case where the timescaledb extension is required, has anyone tried that before?

@potemkin_ai said in Authorization via temporary password (numbers) on e-mail:

@msbt , can I easily replace Cloudron's auth with Keycloak, keeping all other applications running, without my intervention?

I wasn't sure whether that was for Cloudron or some external app, since it was initially posted in "Discuss". Unsure if you could make it your primary thing for auth with Cloudron, my experience with it is rather minimal, just mentioned it because it crossed my desk the other day

Keycloak can do that via https://github.com/p2-inc/keycloak-magic-link?tab=readme-ov-file#email-otp

@girish https://www.keycloak.org/server/configuration-provider#_installing_and_uninstalling_a_provider

@girish the problem is that if you add a new provider, the executable needs a rebuild, else it won't recognize it (as far as I understand it)

Hah alright, reboot did the trick, sorry for the noise!

Yeah that made it worse, running:

cloudron-support --troubleshoot
Vendor: Hetzner Product: vServer
Linux: 5.15.0-134-generic
Ubuntu: jammy 22.04
Processor: Intel Xeon Processor (Skylake, IBRS, no TSX) x 16
RAM: 32086440KB
Disk: /dev/sda1       140G
[OK]	node version is correct
[OK]	IPv6 is enabled in kernel. No public IPv6 address
	Docker is down. Trying to restart docker ...

And it's stuck there. Rebooting the whole thing now

I just tried to restart Nextcloud because in the same minute I got the email that the storagebox is back. This is what Nextcloud says:

Mar 12 14:22:55 box:tasks update 21663: {"percent":10,"message":"Starting app services"}
Mar 12 14:22:55 box:tasks update 21663: {"percent":20,"message":"Restarting container"}
Mar 12 14:22:57 => Healtheck error: Error: Timeout of 7000ms exceeded
Mar 12 14:23:19 box:apptask run: app error for state pending_restart: BoxError: (HTTP code 500) server error - Cannot restart container 0e650789-7a15-44cb-ad69-5a914b3dea26: tried to kill container, but did not receive an exit event at Object.restartContainer (/home/yellowtent/box/src/docker.js:504:50) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async restart (/home/yellowtent/box/src/apptask.js:745:9) { reason: 'Docker Error', details: {}, nestedError: Error: (HTTP code 500) server error - Cannot restart container 0e650789-7a15-44cb-ad69-5a914b3dea26: tried to kill container, but did not receive an exit event at /home/yellowtent/box/node_modules/docker-modem/lib/modem.js:382:17 at getCause (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:417:7) at Modem.buildPayload (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:378:5) at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:346:16) at IncomingMessage.emit (node:events:531:35) at endReadableNT (node:internal/streams/readable:1696:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { reason: 'server error', statusCode: 500, json: { message: 'Cannot restart container 0e650789-7a15-44cb-ad69-5a914b3dea26: tried to kill container, but did not receive an exit event' } } }
Mar 12 14:23:19 box:taskworker Task took 24.202 seconds
Mar 12 14:23:19 box:tasks setCompleted - 21663: {"result":null,"error":{"stack":"BoxError: (HTTP code 500) server error - Cannot restart container 0e650789-7a15-44cb-ad69-5a914b3dea26: tried to kill container, but did not receive an exit event \n at Object.restartContainer (/home/yellowtent/box/src/docker.js:504:50)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async restart (/home/yellowtent/box/src/apptask.js:745:9)","name":"BoxError","reason":"Docker Error","details":{},"message":"(HTTP code 500) server error - Cannot restart container 0e650789-7a15-44cb-ad69-5a914b3dea26: tried to kill container, but did not receive an exit event ","nestedError":{"stack":"Error: (HTTP code 500) server error - Cannot restart container 0e650789-7a15-44cb-ad69-5a914b3dea26: tried to kill container, but did not receive an exit event \n at /home/yellowtent/box/node_modules/docker-modem/lib/modem.js:382:17\n at getCause (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:417:7)\n at Modem.buildPayload (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:378:5)\n at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:346:16)\n at IncomingMessage.emit (node:events:531:35)\n at endReadableNT (node:internal/streams/readable:1696:12)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)","name":"Error","reason":"server error","message":"(HTTP code 500) server error - Cannot restart container 0e650789-7a15-44cb-ad69-5a914b3dea26: tried to kill container, but did not receive an exit event "}}}
Mar 12 14:23:19 box:tasks update 21663: {"percent":100,"result":null,"error":{"stack":"BoxError: (HTTP code 500) server error - Cannot restart container 0e650789-7a15-44cb-ad69-5a914b3dea26: tried to kill container, but did not receive an exit event \n at Object.restartContainer (/home/yellowtent/box/src/docker.js:504:50)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async restart (/home/yellowtent/box/src/apptask.js:745:9)","name":"BoxError","reason":"Docker Error","details":{},"message":"(HTTP code 500) server error - Cannot restart container 0e650789-7a15-44cb-ad69-5a914b3dea26: tried to kill container, but did not receive an exit event ","nestedError":{"stack":"Error: (HTTP code 500) server error - Cannot restart container 0e650789-7a15-44cb-ad69-5a914b3dea26: tried to kill container, but did not receive an exit event \n at /home/yellowtent/box/node_modules/docker-modem/lib/modem.js:382:17\n at getCause (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:417:7)\n at Modem.buildPayload (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:378:5)\n at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/docker-modem/lib/modem.js:346:16)\n at IncomingMessage.emit (node:events:531:35)\n at endReadableNT (node:internal/streams/readable:1696:12)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)","name":"Error","reason":"server error","message":"(HTTP code 500) server error - Cannot restart container 0e650789-7a15-44cb-ad69-5a914b3dea26: tried to kill container, but did not receive an exit event "}}}
Mar 12 14:23:19 BoxError: (HTTP code 500) server error - Cannot restart container 0e650789-7a15-44cb-ad69-5a914b3dea26: tried to kill container, but did not receive an exit event
Mar 12 14:23:19 at Object.restartContainer (/home/yellowtent/box/src/docker.js:504:50)
Mar 12 14:23:19 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Mar 12 14:23:19 at async restart (/home/yellowtent/box/src/apptask.js:745:9)

Restarting docker now