Cloudron Forum

Yes; thank you.

Thank you for your in-depth research and description!

Thank you.

My city is in the support timezone.

Further, I don't see a place to specify a timezone. That is, I think Castopod is automatically assigning the timezone.

I get this error when trying to a schedule a podcast episode (I deleted my city):

DateInvalidTimeZoneException
DateTimeZone::__construct(): Unknown or bad timezone (America/CityDeleted)
at /app/code/vendor/codeigniter4/framework/system/I18n/TimeTrait.php:92

When I copy the stack trace:

DateInvalidTimeZoneException: DateTimeZone::__construct(): Unknown or bad timezone (America/CityDeleted) in /app/code/vendor/codeigniter4/framework/system/I18n/TimeTrait.php:92
Stack trace:
#0 /app/code/vendor/codeigniter4/framework/system/I18n/TimeTrait.php(92): DateTimeZone->__construct()
#1 /app/code/vendor/codeigniter4/framework/system/I18n/TimeTrait.php(256): CodeIgniter\I18n\Time->__construct()
#2 /app/code/modules/Admin/Controllers/EpisodeController.php(497): CodeIgniter\I18n\Time::createFromFormat()
#3 /app/code/modules/Admin/Controllers/EpisodeController.php(64): Modules\Admin\Controllers\EpisodeController->attemptPublish()
#4 /app/code/vendor/codeigniter4/framework/system/CodeIgniter.php(932): Modules\Admin\Controllers\EpisodeController->_remap()
#5 /app/code/vendor/codeigniter4/framework/system/CodeIgniter.php(509): CodeIgniter\CodeIgniter->runController()
#6 /app/code/vendor/codeigniter4/framework/system/CodeIgniter.php(355): CodeIgniter\CodeIgniter->handleRequest()
#7 /app/code/vendor/codeigniter4/framework/system/Boot.php(334): CodeIgniter\CodeIgniter->run()
#8 /app/code/vendor/codeigniter4/framework/system/Boot.php(67): CodeIgniter\Boot::runCodeIgniter()
#9 /app/code/public/index.php(61): CodeIgniter\Boot::bootWeb()
#10 {main}

This happens both on the Cloudron demo server and my server.

Is this an upstream issue?

One of our domains is on the Cloudron free tier and has two apps (both with automatic updates).

However, neither app updates automatically.

But when I try to manually update the update, I receive this error:

Your Cloudron subscription has expired. Please set up a subscription to update the app.

Do we now need a subscription to update apps?

Update: cloudron-support --troubleshoot returns:

[WARN]	netplan configuration is empty. this might be OK depending on your networking setup
[FAIL]	DNS is not resolving

Further, /etc/netplan/ is empty. How do I generate the correct .yaml file to include there?

Final Update: I was able to crate a netplan .yaml file by following these instructions.

RackNerd. However, to be fair, their Black Friday promotions are good, and they have been great for what we typically need.

@joseph host s3.nl-ams.scw.cloud returns: Host s3.nl-ams.scw.cloud not found: 2(SERVFAIL)

Two notes:

1. Any host query returns the same error.
2. This does not happen on my other server (which also uses Cloudron and successfully backups to Scaleway -- and is with the same server provider).

I contacted the server provider, but they replied saying they don't offer support.

Am I correct in saying this is a server issue rather than a Scaleway issue?

Our Scaleway backup recently started to fail with the following notification:

Backup failed: Upload error: code: UnknownEndpoint message: Inaccessible host: example.s3.nl-ams.scw.cloud' at portundefined'. This service may not be available in the `nl-ams' region..

Recent logs:

Dec 02 04:18:10 box:backupupload upload completed. error: BoxError: Upload error: code: UnknownEndpoint message: Inaccessible host: `example.s3.nl-ams.scw.cloud' at port `undefined'. This service may not be available in the `nl-ams' region. at Object.finish (/home/yellowtent/box/src/storage/s3.js:129:30) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async tarPack (/home/yellowtent/box/src/backupformat/tgz.js:174:5) at async /home/yellowtent/box/src/backupformat/tgz.js:266:9 at async promiseRetry (/home/yellowtent/box/src/promise-retry.js:17:20) at async Object.upload (/home/yellowtent/box/src/backupformat/tgz.js:262:5) at async Object.upload (/home/yellowtent/box/src/backuptask.js:91:5) { reason: 'External Error', details: {} }
Dec 02 04:18:10 box:backuptask runBackupUpload: result - {"result":"Upload error: code: UnknownEndpoint message: Inaccessible host: `example.s3.nl-ams.scw.cloud' at port `undefined'. This service may not be available in the `nl-ams' region."}
Dec 02 04:18:10 box:shell backuptask: /usr/bin/sudo -S -E --close-from=4 /home/yellowtent/box/src/scripts/backupupload.js snapshot/app_c4f23162-e4a0-4a4b-8c64-ce1dad23f1ca tgz {"localRoot":"/home/yellowtent/appsdata/c4f23162-e4a0-4a4b-8c64-ce1dad23f1ca","layout":[]} errored BoxError: backuptask exited with code 50 signal null
Dec 02 04:18:10 at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:111:19)
Dec 02 04:18:10 at ChildProcess.emit (node:events:519:28)
Dec 02 04:18:10 at ChildProcess._handle.onexit (node:internal/child_process:294:12) {
Dec 02 04:18:10 reason: 'Shell Error',
Dec 02 04:18:10 details: {},
Dec 02 04:18:10 code: 50,
Dec 02 04:18:10 signal: null
Dec 02 04:18:10 }
Dec 02 04:18:10 box:taskworker Task took 1088.331 seconds
Dec 02 04:18:10 box:tasks setCompleted - 5149: {"result":null,"error":{"stack":"BoxError: Upload error: code: UnknownEndpoint message: Inaccessible host: `example.s3.nl-ams.scw.cloud' at port `undefined'. This service may not be available in the `nl-ams' region.\n at runBackupUpload (/home/yellowtent/box/src/backuptask.js:170:15)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async uploadAppSnapshot (/home/yellowtent/box/src/backuptask.js:365:5)\n at async backupAppWithTag (/home/yellowtent/box/src/backuptask.js:387:5)\n at async fullBackup (/home/yellowtent/box/src/backuptask.js:508:29)","name":"BoxError","reason":"External Error","details":{},"message":"Upload error: code: UnknownEndpoint message: Inaccessible host: `example.s3.nl-ams.scw.cloud' at port `undefined'. This service may not be available in the `nl-ams' region."}}
Dec 02 04:18:10 box:tasks update 5149: {"percent":100,"result":null,"error":{"stack":"BoxError: Upload error: code: UnknownEndpoint message: Inaccessible host: `example.s3.nl-ams.scw.cloud' at port `undefined'. This service may not be available in the `nl-ams' region.\n at runBackupUpload (/home/yellowtent/box/src/backuptask.js:170:15)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async uploadAppSnapshot (/home/yellowtent/box/src/backuptask.js:365:5)\n at async backupAppWithTag (/home/yellowtent/box/src/backuptask.js:387:5)\n at async fullBackup (/home/yellowtent/box/src/backuptask.js:508:29)","name":"BoxError","reason":"External Error","details":{},"message":"Upload error: code: UnknownEndpoint message: Inaccessible host: `example.s3.nl-ams.scw.cloud' at port `undefined'. This service may not be available in the `nl-ams' region."}}
Dec 02 04:18:10 BoxError: Upload error: code: UnknownEndpoint message: Inaccessible host: `example.s3.nl-ams.scw.cloud' at port `undefined'. This service may not be available in the `nl-ams' region.
Dec 02 04:18:10 at runBackupUpload (/home/yellowtent/box/src/backuptask.js:170:15)
Dec 02 04:18:10 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Dec 02 04:18:10 at async uploadAppSnapshot (/home/yellowtent/box/src/backuptask.js:365:5)
Dec 02 04:18:10 at async backupAppWithTag (/home/yellowtent/box/src/backuptask.js:387:5)
Dec 02 04:18:10 at async fullBackup (/home/yellowtent/box/src/backuptask.js:508:29)

What's odd is that we have another Cloudron also backing up to the same region in Scaleway (s3.nl-ams.scw.cloud), and it is fine.

This is affecting us as well.

So – just to clarify – we simply need to wait for fix to applied in Cloudron?

Links in emails (such as registration, password reset, etc.) are lacking the domain:

This:

If the button above doesn't work, copy the url below and paste it in your browser's address bar:
?userPasswordReset=IH4EpTZtvYSs4Mv7cX5k7A9s4nn10GS1Z2PBAoOONaaEHrWhvwrqiwWPSK1NfM3q

should be:

If the button above doesn't work, copy the url below and paste it in your browser's address bar:
https://example.com?userPasswordReset=IH4EpTZtvYSs4Mv7cX5k7A9s4nn10GS1Z2PBAoOONaaEHrWhvwrqiwWPSK1NfM3q

Anyway to add the domain into these emails?

Update: Looks like GoDaddy has restricted access to their API.

Could we just use the Wildcard DNS set-up instead?

We only have one domain, and it continues to work (as in, resolve to our website).

But when I try to add a new app, I get the following message:

DNS credentials for indychinesechurch.org are invalid. Update it in Domains & Certs view

But when I create a new GoDaddy API and enter it in Domains & Certs, I get the error in the original post.

Although GoDaddy was working correctly, now when I add an API key and secret under "Domains & Certs" I receive the following error:

Access denied: GoDaddy DNS error [403] Authenticated user is not allowed access

What should my next step be?

Despite adding

FILE_STORAGE=local
FILE_STORAGE_UPLOAD_MAX_SIZE=26214400

(source)

and

MAXIMUM_IMPORT_SIZE=5120000

(source)

to env.sh and restarting, I am stilling getting the Sorry, this file is too large – the maximum size is 1 MB error when I try to attach a file larger than 1 MB.

What am I missing?

Thank you, but don't spend too much time on this.

I did a fresh test install of WordPress and CiviCRM, and it works (and this is with /app/data/wp-content in wp-config.php).

For now, I can just update wp-config.php as needed in my current install.

Yes!

Changing to

define('WP_CONTENT_DIR', '/app/code/wp-content');

in wp-config.php allows content to load.

Thank you so much!

Yes, adding that line causes the problem.

Is that line formatted correctly? I found this and tired to format it accordingly, but still got an error.

(But I'm not sure I formatted it properly.)

Thank you.

I'm able to access the site; I'm just getting the error when interacting with certain plugins.

Yes, the error is from CiviCRM. Disabling the CiviCRM resolves the problem I have with one plugin – but then I can't use CiviCRM.

I cloned a backup that was working off v3.4.2, and everything worked correctly. However, when it updated to v.3.6, the same problems arose. Odd.

Thanks again.