It seems that the Backup options don't provide a full list of regions for the DigitalOcean Spaces.
See: https://docs.digitalocean.com/products/spaces/details/availability/
Cloudron options:
PS: Currently, i have been able to work around this by using the "S3 API (v4)" option instead, but it would be nice if the native dialog for DO Spaces included the entire list of available regions.
Hi @timconsidine, i would certainly like to try out your Grist package.
After initially not finding Grist on Cloudron, i ended up deploying it on another VPS, using a Portainer/docker-compose based setup.
Would be great if the complete Grist package can be managed within Cloudron itself!
Just came here for the same issue.
Can't see any way to change the admin default password!
@james said in Error: Domain nameservers are not set to NameCheap:
This could be a bug. Can you try to cancel the change location task and create it again?
Done!
Sorry, my first time with this sort of Subdomain delegations.
In the Retry Task, I had to change the location to the newly added, 'subdomain as root' option.
Thanks again!
@james said in Error: Domain nameservers are not set to NameCheap:
This could be a bug. Can you try to cancel the change location task and create it again?
I tried that. But this is the only option available:
And every time i try the "Retry task", it falls back into the same loop.
@james @girish Thanks for the quick replies!
It seems that i had missed setting the proper value for the "Zone Name", which is necessary in my case as the Domain and the concerned Subdomain are hosted in 2 different places..
I have now added the value and Synced DNS. But, i'm still facing issue in bringing up the app. It seems the Retry Location change tasks is still checking against the earlier Nameservers, and not the latest ones.
Nov 24 14:59:10 box:dns/waitfordns waitForDns: nameservers are ["ns02.one.com","ns01.one.com"]
Nov 24 14:59:11 box:dns/waitfordns resolveIp: Checking A for <subdomain> at 185.10.11.10
Nov 24 14:59:11 box:dns/waitfordns resolveIp: No A. Checking CNAME for <subdomain> at 185.10.11.10
Nov 24 14:59:11 box:dns/waitfordns isChangeSynced: NS ns02.one.com (185.10.11.10) errored when resolve <subdomain> (A): Error: queryCname ENODATA <subdomain>
Nov 24 14:59:11 box:dns/waitfordns resolveIp: Checking A for <subdomain> at 2001:67c:3c0::10
Nov 24 14:59:11 box:dns/waitfordns resolveIp: No A. Checking CNAME for <subdomain> at 2001:67c:3c0::10
Nov 24 14:59:11 box:dns/waitfordns isChangeSynced: NS ns02.one.com (2001:67c:3c0::10) errored when resolve <subdomain> (A): Error: queryCname ENODATA <subdomain>
Nov 24 14:59:11 box:dns/waitfordns Attempt 10 failed. Will retry: ETRYAGAIN
(Sub-)Domain setup error:
Domain nameservers are not set to NameCheap
Where can i check which values are being compared with, by Cloudron, for the nameservers belonging to NameCheap?
My initial suspicion is that only the default Nameservers of NameCheap might be used for checking, and not the additional options like FreeDNS (which i'm using) [See: NameCheap FreeDNS]
Additionally, it seems like if:
Start recording > [time elapses] > Stop recording > Start Recording again > [time elapses] > Stop Recording/Exit Meeting
Only the last recording gets saved (overwriting the first part).
@james
Current behaviour:
/app/data/rec but not in S3.If, in Step 3:
i stop the Recording and then stop the meeting, only then the Recording gets uploaded to S3.
Expectation:
Recording should get uploaded to S3 regardless of the path taken to 'stop' the meeting and without explicitly stopping the recording.
@james said in MiroTalk SFU: Recording not possible?:
Change AWS_S3_BUCKET_NAME to AWS_S3_BUCKET restart and it should be working.
Thanks!
That did get it working.
@mirotalk-57bab571 Just one more kink remaining:
When i 'disconnect' the call without stopping the recording, the Recording seems to get saved only in the local directory, and not S3. The S3 upload seems to be triggered only when an ongoing recording is stopped explicitly.
@MiroTalk Thanks for sharing the details and the screenshot.
In my case, i'm getting this error:
Nov 18 08:28:31 "app": "Server",
Nov 18 08:28:31 "level": "error",
Nov 18 08:28:31 "message": "Rec Finalization error"
Nov 18 08:28:31 "timestamp": "2025-11-18T02:58:31.414Z",
env ->
# Recording
RECORDING_ENABLED=true # Enable recording functionality (true|false)
RECORDING_UPLOAD_TO_S3=true # Upload recording to AWS S3 bucket [true/false]
# AWS S3 Configuration
AWS_S3_ENABLED=true # Enable AWS S3 storage (true|false)
AWS_S3_BUCKET_NAME=<bucket> # Name of your S3 bucket (must exist)
AWS_ACCESS_KEY_ID=<key_id> # AWS Access Key ID (leave empty for IAM roles)
AWS_SECRET_ACCESS_KEY=<key_secret> # AWS Secret Access Key (leave empty for IAM roles)
AWS_REGION=<region> # AWS region (e.g., us-east-2, eu-west-2)
AWS_S3_ENDPOINT=https://<region>.digitaloceanspaces.com
AWS_S3_FORCE_PATH_STYLE=true
@MiroTalk said in MiroTalk SFU: Recording not possible?:
Just out of curiosity, on DigitalOcean, the web video preview work there?
No idea. I'm yet to figure out why uploading to S3 (DigitalOcean Spaces) is not working for me.
Hi @james , thanks for the screenshots. I can now see that there's a "Save on server" option in the UI, and it's working for me as well.
Now, just S3 is left to work.
My env file ->
# Recording
RECORDING_ENABLED=true # Enable recording functionality (true|false)
RECORDING_UPLOAD_TO_S3=false # Upload recording to AWS S3 bucket [true/false]
# AWS S3 Configuration
AWS_S3_ENABLED=true # Enable AWS S3 storage (true|false)
AWS_S3_BUCKET_NAME=<bucket-name> # Name of your S3 bucket (must exist)
AWS_ACCESS_KEY_ID=<key-id> # AWS Access Key ID (leave empty for IAM roles)
AWS_SECRET_ACCESS_KEY=<key-secret> # AWS Secret Access Key (leave empty for IAM roles)
AWS_REGION=<region> # AWS region (e.g., us-east-2, eu-west-2)
AWS_S3_ENDPOINT=https://<region>.digitaloceanspaces.com
Note: Although i didn't find the "AWS_S3_ENDPOINT" key in the env template, i configured it because it seems to work with most S3 client libraries, and is a necessity to be able to connect to S3 spaces other than AWS.
It seems like 2 separate updated packages have been released for this.
Just came across the 2nd one and updated the app again.
rec folder is now available in /app/data/I restarted the updated app, but i still get only this:
No rec folder available, and no default recording taking place.
Hi @nebulon @mirotalk-57bab571
So, i'm still unable to boot up the app after setting RECORDING_ENABLED=true :
Nov 15 09:36:54 node:fs:1364
Nov 15 09:36:54 const result = binding.mkdir(
Nov 15 09:36:54 ^
Nov 15 09:36:54 2025-11-15T04:06:54Z
Nov 15 09:36:54 Error: ENOENT: no such file or directory, mkdir '/app/code/app/rec/'
Nov 15 09:36:54 at Object.mkdirSync (node:fs:1364:26)
Nov 15 09:36:54 at Object.<anonymous> (/app/code/app/src/Server.js:280:12)
Nov 15 09:36:54 at Module._compile (node:internal/modules/cjs/loader:1554:14)
Nov 15 09:36:54 at Object..js (node:internal/modules/cjs/loader:1706:10)
Nov 15 09:36:54 at Module.load (node:internal/modules/cjs/loader:1289:32)
Nov 15 09:36:54 at Function._load (node:internal/modules/cjs/loader:1108:12)
Nov 15 09:36:54 at TracingChannel.traceSync (node:diagnostics_channel:322:14)
Nov 15 09:36:54 at wrapModuleLoad (node:internal/modules/cjs/loader:220:24)
Nov 15 09:36:54 at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)
Nov 15 09:36:54 at node:internal/main/run_main_module:36:49 {
Nov 15 09:36:54 errno: -2,
Nov 15 09:36:54 code: 'ENOENT',
Nov 15 09:36:54 syscall: 'mkdir',
Nov 15 09:36:54 path: '/app/code/app/rec/'
Nov 15 09:36:54 }
Nov 15 09:36:54 2025-11-15T04:06:54Z
Nov 15 09:36:54 Node.js v22.14.0
Nov 15 09:36:54 \
When i try to enable Recording via the env file, the app errors out. Main error:
{
Nov 13 19:11:04 errno: -2,
Nov 13 19:11:04 code: 'ENOENT',
Nov 13 19:11:04 syscall: 'mkdir',
Nov 13 19:11:04 path: '/app/code/app/rec/'
Nov 13 19:11:04 }
So, is it not currently possible to enable Recording at all (Local/S3) ?
Hi @james
@james said in Vikunja update strategy:
In the meanwhile, how comfortable are you changing the app yourself?
What would that entail?
P.S. Never packaged a Cloudron app before
Hi. I'd like to request to:
Because, the maintainers of this tool don't seem to favour stable releases. Instead, they focus primarily on "unstable" releases, even using those versions for their cloud offering.