Cloudron Forum

Ollama is now packaged as a standalone app. The app package is as usual still published as unstable until we get some feedback how it works and iron out any initial issues. Forum category is at https://forum.cloudron.io/category/212/ollama so please report any issues there The docs will be at https://docs.cloudron.io/packages/ollama/ Package repo is https://git.cloudron.io/packages/ollama-app

I am having an issue with setting up a new app on my Cloudron system. I registered the domain on Namecheap two days ago, and immediately set up the domain in Cloudron using the API method, which has always worked fine. It has been over 24 hours. But when I attempt to install a WordPress site (Managed), some weird things are happening. The installation process gets stuck at Installing - Waiting for propagation of EXAMPLE.org (anonymized). And the logs for the app look like this: Oct 27 09:43:44 box:dns/waitfordns waitForDns: nameservers are ["dns2.registrar-servers.com","dns1.registrar-servers.com"] Oct 27 09:43:44 box:dns/waitfordns resolveIp: Checking A for EXAMPLE.org at 156.154.133.200 Oct 27 09:43:44 box:dns/waitfordns isChangeSynced: EXAMPLE.org (A) was resolved to 192.64.119.184,193.46.198.90 at NS dns2.registrar-servers.com (156.154.133.200). Expecting 193.46.198.90. Match false Oct 27 09:43:44 box:dns/waitfordns resolveIp: Checking A for EXAMPLE.org at 2610:a1:1025::200 Oct 27 09:43:44 box:dns/waitfordns isChangeSynced: EXAMPLE.org (A) was resolved to 192.64.119.184,193.46.198.90 at NS dns2.registrar-servers.com (2610:a1:1025::200). Expecting 193.46.198.90. Match false Oct 27 09:43:44 box:dns/waitfordns waitForDns: EXAMPLE.org at ns dns2.registrar-servers.com: not done Oct 27 09:43:44 box:dns/waitfordns Attempt 187 failed. Will retry: ETRYAGAIN Here's where it gets a little weirder. If I renew the domain certificates across Cloudron while it is stuck there, the website starts working; if I go to EXAMPLE.org, I see a WordPress website. But I can't get the installation process unstuck. And if I try reinstalling, the site disappears until I try the renewal again, which once again does not unstuck the installation process. I attempted to install Surfer at that domain to see if it was a WordPress issue, but the same problem occurred. Are there other diagnostics you'd recommend? Thanks in advance for your assistance.

We use https://github.com/panva/node-oidc-provider internally and that is supposed to support PKCE. Not sure yet how to use it to test what this needs. Until that is working, the options are a keycloak instance or a small backend which gives the SPA some kind of session while handling the oidc login bits.

Hello @zack13532 Glad to read that this solution suits you well. Oh, and since that was your first post. Welcome to the Cloudron forum.

Some logs as well below. So until ~19:34 this is the original configuration. Then I did reboot to emergency mode, fixed the brackets, and then rebooted. When I reboot the container and it works, which prisma correctly prints the path. If the host is rebooted, then it fails again (as the fix / workaround is, as expected, not retained) I assume that adding the brackets would have no adverse effects. Oct 27 19:34:15 /app/pkg/start.sh: line 54: prisma: command not found Oct 27 19:34:15 => Setting up OIDC Oct 27 19:34:15 => Updating permissions Oct 27 19:34:15 => prisma migrate Oct 27 19:35:12 Repair mode. Use the webterminal or cloudron exec to repair. Sleeping Oct 27 19:37:55 => Setting up OIDC Oct 27 19:37:55 => Updating permissions Oct 27 19:37:55 => prisma migrate Oct 27 19:37:58 2025-10-27T19:37:58+01:00 Oct 27 19:37:58 2025-10-27T19:37:58+01:00 Oct 27 19:37:58 2025-10-27T19:37:58+01:00 Oct 27 19:37:58 > Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 0%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 1%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 3%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 4%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 6%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 7%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 8%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 11%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 16%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 20%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 22%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 25%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 27%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 28%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 31%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 33%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 35%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 37%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 39%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 43%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 46%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 48%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 50%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 55%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 60%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 64%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 69%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 73%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 78%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 82%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 88%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 91%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 93%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 95%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 97%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 98%> Downloading Prisma engines for Node-API for debian-openssl-3.0.x [] 100%Environment variables loaded from .env Oct 27 19:37:58 Datasource "db": PostgreSQL database "dbe49f54e745c046d38f7e4a0e61387c84", schema "public" at "postgresql:5432" Oct 27 19:37:58 Prisma schema loaded from ../../../pkg/prisma/schema.prisma Oct 27 19:37:58 No pending migrations to apply. Oct 27 19:37:58 96 migrations found in prisma/migrations Oct 27 19:37:58 => Starting Rallly Oct 27 19:37:59 2025-10-27T19:37:59+01:00 Oct 27 19:37:59 ▲ Next.js 15.4.6 Oct 27 19:37:59 ✓ Ready in 430ms Oct 27 19:37:59 ✓ Starting... Oct 27 19:37:59 - Local: http://e49f54e7-45c0-46d3-8f7e-4a0e61387c84:3000 Oct 27 19:37:59 - Network: http://e49f54e7-45c0-46d3-8f7e-4a0e61387c84:3000 [image: 1761591692362-77a5f7c7-5a46-4567-b730-cb2a986b374f-image-resized.png]

This is why we can't have nice things: https://github.com/alam00000/bentopdf/releases/tag/v1.1.4 It recently came to my attention from a user of ours that a company was taking advantage of our open Apache 2.0 license. They repackaged BentoPDF, sold it as a proprietary product at a high price, and offered zero credit or contributions back to the community. To be blunt, that’s not okay. It undermines the work of every single contributor and the entire spirit of the project. That’s why we are switching BentoPDF to the AGPLv3 license. [...] Here’s what you need to know: Commercial use is still allowed. You can continue to use BentoPDF in your products and for your company. If you modify BentoPDF and run it as a public-facing service (like a SaaS product), you must now share your source code under the same AGPLv3 license. [...] Most importantly BentoPDF is still free and open source and always will be.

@tronical personally I do this process : fork the repo make changes docker build etc. docker push etc cloudron install etc. Maybe I should learn cloudron build but I am an old dog with limited brain space My build script (usually in folder above the app dev folder) : #!/bin/bash if [ "$#" -lt 1 ]; then echo "Usage: $0 <image-name> [cache|nocache] <appname.yourdomain.tld>" exit 1 fi # Get the directory from which the script was called BUILD_DIR="$(pwd)" if [ "$2" = "cache" ]; then echo "Building with cache ..." docker build --platform linux/amd64 -t $1 "$BUILD_DIR" else echo "Building with no cache ..." docker build --no-cache --platform linux/amd64 -t $1 "$BUILD_DIR" fi docker push $1 cloudron install --image $1 --location $3 e.g. ../cld.sh dockerregistry.yourdomain.tld/appname:version cache appname.yourdomain.tld

Oh sorry, I totally missed this. Thanks and noted!