Cloudron Forum

@timconsidine sagte: And the position is still only update to ubuntu 26.04 after cloudron 10.0.4 ? Yes.

Title: Passkey registration failing: "User verification was required" (macOS Golden Gate) I am experiencing a consistent failure when attempting to register a new passkey for my Cloudron account. The registration fails during the verification step. Environment Details: Device: Mac mini (2024) OS: macOS 27.0.1 (26A434) - Golden Gate Browsers Tested: Microsoft Edge and Safari Password Manager: Dashlane (handling the passkey prompt) Vendor: VMware, Inc. Product: VMware Virtual Platform Linux: 5.15.0-191-generic Ubuntu: jammy 22.04 Cloudron: 9.2.0 Execution environment: vmware Processor: Intel(R) Xeon(R) Gold 6148 CPU @ 2.40GHz x 16 RAM: 98838224KB Disk: /dev/mapper/ubuntu--vg-ubuntu--lv 887G [OK] Root disk usage is OK (5%) [OK] Memory usage is OK (8%) [OK] Clock is NTP-synchronized [OK] node version is correct [OK] IPv6 is enabled in kernel. No public IPv6 address [OK] docker is running [OK] docker version is correct [OK] MySQL is running [OK] netplan is good [OK] DNS is resolving via systemd-resolved [OK] unbound is running [OK] IPv4 HTTPS to api.cloudron.io/api/v1/helper/public_ip [SKIP] IPv6 HTTPS to api.cloudron.io/api/v1/helper/public_ip — no public IPv6 address [OK] IPv4 HTTPS to auth.docker.io/token [SKIP] IPv6 HTTPS to auth.docker.io/token — no public IPv6 address [OK] IPv4 HTTPS to acme-v02.api.letsencrypt.org [SKIP] IPv6 HTTPS to acme-v02.api.letsencrypt.org — no public IPv6 address [OK] nginx is running [OK] dashboard cert is valid [OK] dashboard is reachable via loopback [OK] No pending database migrations [OK] Service 'mysql' is running and healthy [OK] Service 'postgresql' is running and healthy [WARN] Service 'mongodb' is not running (may be lazy-stopped) [OK] Service 'mail' is running and healthy [OK] Service 'graphite' is running and healthy [OK] Service 'sftp' is running and healthy [OK] box v9.2.0 is running [OK] Dashboard is reachable via IPv4 (https://my.megaaidsecure.us) [SKIP] Dashboard IPv6 reachability — no public IPv6 address [SKIP] Domain expiry check — whois not installed; run 'apt install whois' to check ======== Summary ======== PASS: 25 WARN: 1 FAIL: 0 SKIP: 5 Warnings: - Service 'mongodb' is not running (may be lazy-stopped) Errors in /home/yellowtent/platformdata/logs/box.log: Sep 28 22:06:31 passkeys: getRegistrationOptions: generated for user uid-xxxxxxx-bd5a-xxxx-xxxx-dc5035d59e6a: Sep 28 22:06:34 passkeys: verifyRegistration: verification failed for user uid-xxxxxxx-bd5a-xxxx-xxxx-dc5035d59e6a: Error: User verification was required, but user could not be verified at verifyRegistrationResponse (file:///home/yellowtent/box/node_modules/@simplewebauthn/server/esm/registration/verifyRegistrationResponse.js:119:15) Sep 28 22:06:37 apphealthmonitor: app health: 12 running / 2 stopped / 2 unresponsive Sep 28 22:06:45 passkeys: getRegistrationOptions: generated for user uid-xxxxxxx-bd5a-xxxx-xxxx-dc5035d59e6a: Sep 28 22:06:46 passkeys: verifyRegistration: verification failed for user uid-xxxxxxx-bd5a-xxxx-xxxx-dc5035d59e6a: Error: User verification was required, but user could not be verified at verifyRegistrationResponse (file:///home/yellowtent/box/node_modules/@simplewebauthn/server/esm/registration/verifyRegistrationResponse.js:119:15)

@timconsidine said: @necrevistonnezr what cloudron version are you on ? 9.2.0 ? or 10.0.5 ? 10.0.5

CR > Email > Mailboxes > Forwarding: Could this be related? Is this the preferred method of forwarding mail now? I have mail forwarded using rules in Roundcube.

The GitLab 19.3.2 image cloudron/com.gitlab.cloudronapp:202609150645580000 occupies 18.5 GB on my server, with 16.1 GB reported as unique size. This is image storage, separate from repositories and other application data. docker history shows these large layers: yarn install --production --pure-lockfile: 5.08 GB Gitaly and bundled Git build/install: 4.40 GB Workhorse compilation: 2.25 GB GitLab Shell dependencies and compilation: 1.28 GB Frontend asset compilation: 1.26 GB The GitLab Shell build also explicitly includes the development test Bundler groups. Would it be possible to review whether build caches, intermediate files and build-only dependencies could be excluded from the final image, using multi-stage builds or cleanup within the same build layer? Some of this may be required at runtime, so these figures are not necessarily reclaimable space. Unused-image pruning is already complete. Reducing the installed image’s footprint would be helpful on servers running many Cloudron apps.

AppsMonitor updated to 0.0.20 in order to make it work on Cluodron 10.0.5. But this means the public page is not working (maybe it’s not even a feature which many want). Public page functionality will be restored when Cloudron 10.1.0 is released.

@Teiluj said: Thanks for considering packaging paperclip. We have created a package for Paperclip and have it running but are waiting to hear from upstream before publishing it.

@girish : SOLVED ! I traced it to (1) the backup in cloudron update failing, triggering update to fail, which was totally caused by (2) my ultra-minimal minibase not having sqlite3 in it and I forgot to add it manually as the packager responsibility when going ultra-minimal. Interestingly I did not discover this in testing, because I was always ticking 'skip backup'. So your approach in the other discussion is proven out ! Ultra-minimal can work but it seems not wise, because darned packagers cannot be trusted . A slightly fatter base is worth it to avoid such mistakes. You win ! Will fatten my minibase while waiting for yours. Sorry for taking up your time again.

@robi neat idea !