Cloudron Forum

@benborges Are you running out of memory? Try bumping the app mem.

All good !

Solved! Just for the sake of someone else stumbling into the same issue : Backup SSHFS mount with hetzner storage box should always be mounted pointing to the exact sub folder where backup will be stored, so the path would be /home/yourfolder and the URL to the server should not contain any path. Now, if you use the same storage volume mounted a second time, as a volume to be added to specific apps then the URL is always ID.your-storagebox.de and the path field is simply / no need to specify any folder. The issue here is that I had it to mount the URL of the storage box ID.your-storagebox.de/home + / in the path and that was the origin of the mess, the odd part is that it did mount and the volume was usable via the filemanager just fine, it's just that the hdparam.sh script would freak out due to this confusion in the path. Anyway, solved !

@d19dotca Interesting, on the new fresh install, I restarted and voila, it works ! on my old install, the one I don't want to loose the site ID's (even if I lost the historical data, that's fine) I see this error after restart : ==> Starting Umami May 26 10:33:14 May 26 10:33:14 May 26 10:33:14 Inconsistent column data: Error creating UUID, invalid character: expected an optional prefix of `urn:uuid:` followed by [0-9a-zA-Z], found `u` at 1 May 26 10:33:14 Invalid `prisma.website.findUnique()` invocation: May 26 10:33:14 PrismaClientKnownRequestError: May 26 10:33:14 at async NextNodeServer.runApi (/app/code/node_modules/next/dist/server/next-server.js:514:9) May 26 10:33:14 at async NextNodeServer.runImpl (/app/code/node_modules/next/dist/server/base-server.js:432:29) { May 26 10:33:14 at async Object.apiResolver (/app/code/node_modules/next/dist/server/api-utils/node.js:372:9) May 26 10:33:14 at async Object.fn (/app/code/node_modules/next/dist/server/next-server.js:828:35) May 26 10:33:14 at async Router.execute (/app/code/node_modules/next/dist/server/router.js:243:32) May 26 10:33:14 at async __WEBPACK_DEFAULT_EXPORT__ (/app/code/.next/server/pages/api/websites/[id].js:154:25) May 26 10:33:14 at async t._request (/app/code/node_modules/@prisma/client/runtime/library.js:179:10484) May 26 10:33:14 at pn.handleAndLogRequestError (/app/code/node_modules/@prisma/client/runtime/library.js:176:5907) May 26 10:33:14 at pn.handleRequestError (/app/code/node_modules/@prisma/client/runtime/library.js:176:6477) May 26 10:33:14 at pn.request (/app/code/node_modules/@prisma/client/runtime/library.js:176:5786) May 26 10:33:14 clientVersion: '4.13.0', May 26 10:33:14 code: 'P2023', May 26 10:33:14 message: 'Error creating UUID, invalid character: expected an optional prefix of `urn:uuid:` followed by [0-9a-zA-Z], found `u` at 1' May 26 10:33:14 meta: { May 26 10:33:14 }

This can be set to solved ! Cloudflare reply : [image: 1679341157587-c09bd926-0b5e-4850-8e26-b9413779a021-image-resized.png]

Can just pass --redo to the setup script.

@nebulon I'm getting Timing buffered disk reads: 906 MB in 3.01 seconds = 301.48 MB/sec this again seems to be a contabo issue more than anything else

@nebulon This was a strange episode, still unclear what happened, but everything "came back" to normal for some reason.

@benborges allowing to change the port is just a limitation of the platform, where marking specific ports as locked is not yet supported.

@benborges Ah ok. Maybe you can wait for 7.3. Please update to that and try to update again and we can debug further. There are some cgroup v2 related fixes for Ubuntu 22 in 7.3 which affect docker container creation, it's possible you hit that case.

@girish could be - at least for the uid one, but not for the file one I just put another disk on that was fresh and used that with the filesystem mount.

@robi htaccess

Hmm I still have permission denied inside the container to read /media/MyMount EDIT This time, it's working, for future reference, only thing I did was to set the home directory properly in the systemD service for each mount, remount them and then systemctl restart box or from the UI restart the box, my mounts are now visible inside the containers and I can read from them [image: 1734902378511-386b79d8-79cb-47db-8687-019194acef53-image.png]

@girish Haven't' pushed anything cloudron related yet but my repo is here https://git.osintukraine.com/benb/fireshare

@benborges I moved your packaging question as a separate topic - https://forum.cloudron.io/topic/7246/help-packaging-fireshare . That way people can just upvote and discuss the app here.