Community App: CloudronVersions.json Response timeout
-
Not sure why this is timing out as the URL seems to be available for me:
https://bind.0data.app/CloudronVersions.json
Mar 20 14:00:10 { Mar 20 14:00:10 path: '/api/v1/community/app', Mar 20 14:00:10 status: 500, Mar 20 14:00:10 error: ServerError [ServiceUnavailableError]: Response timeout Mar 20 14:00:10 at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/connect-timeout/index.js:84:8) Mar 20 14:00:10 at IncomingMessage.emit (node:events:508:28) Mar 20 14:00:10 at Timeout._onTimeout (/home/yellowtent/box/node_modules/connect-timeout/index.js:49:11) Mar 20 14:00:10 at listOnTimeout (node:internal/timers:605:17) Mar 20 14:00:10 at process.processTimers (node:internal/timers:541:7) { Mar 20 14:00:10 code: 'ETIMEDOUT', Mar 20 14:00:10 timeout: 60000 Mar 20 14:00:10 } Mar 20 14:00:10 } Mar 20 14:00:10 HttpError: Could not resolve CloudronVersions.json from URL Mar 20 14:00:10 at BoxError.toHttpError (file:///home/yellowtent/box/src/boxerror.js:86:16) Mar 20 14:00:10 at getAppVersion (file:///home/yellowtent/box/src/routes/community.js:13:37) Mar 20 14:00:10 at process.processTicksAndRejections (node:internal/process/task_queues:103:5) Mar 20 14:00:20 box:apphealthmonitor app health: 19 running / 3 stopped / 0 unresponsive Mar 20 14:00:30 box:apphealthmonitor app health: 19 running / 3 stopped / 0 unresponsive Mar 20 14:00:40 box:apphealthmonitor app health: 19 running / 3 stopped / 0 unresponsive Mar 20 14:00:50 box:apphealthmonitor app health: 19 running / 3 stopped / 0 unresponsive Mar 20 14:01:00 box:apphealthmonitor app health: 19 running / 3 stopped / 0 unresponsive Mar 20 14:01:10 box:apphealthmonitor app health: 19 running / 3 stopped / 0 unresponsive Mar 20 14:01:20 box:apphealthmonitor app health: 19 running / 3 stopped / 0 unresponsive Mar 20 14:01:20 { Mar 20 14:01:20 path: '/api/v1/community/app', Mar 20 14:01:20 status: 500, Mar 20 14:01:20 error: ServerError [ServiceUnavailableError]: Response timeout Mar 20 14:01:20 at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/connect-timeout/index.js:84:8) Mar 20 14:01:20 at IncomingMessage.emit (node:events:508:28) Mar 20 14:01:20 at Timeout._onTimeout (/home/yellowtent/box/node_modules/connect-timeout/index.js:49:11) Mar 20 14:01:20 at listOnTimeout (node:internal/timers:605:17) Mar 20 14:01:20 at process.processTimers (node:internal/timers:541:7) { Mar 20 14:01:20 code: 'ETIMEDOUT', Mar 20 14:01:20 timeout: 60000 Mar 20 14:01:20 } Mar 20 14:01:20 }Noticing also that it seems to resolve immediately the first time, but subsequent attempts time out until I restart the server.
Mar 20 14:06:28 box:network/generic getIP: querying https://ipv4.api.cloudron.io/api/v1/helper/public_ip to get ipv4 Mar 20 14:06:29 box:community downloading manifest from https://bind.0data.app/CloudronVersions.json version latest Mar 20 14:06:29 box:reverseproxy writeDefaultConfig: writing configs for endpoint "ip" Mar 20 14:06:29 box:shell reverseproxy: /usr/bin/sudo --non-interactive /home/yellowtent/box/src/scripts/restartservice.sh nginx Mar 20 14:06:29 box:platform onActivated: finishedBut from there when I install it it times out again:
Mar 20 14:07:20 { Mar 20 14:07:20 path: '/api/v1/apps', Mar 20 14:07:20 status: 500, Mar 20 14:07:20 error: ServerError [ServiceUnavailableError]: Response timeout Mar 20 14:07:20 at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/connect-timeout/index.js:84:8) Mar 20 14:07:20 at IncomingMessage.emit (node:events:508:28) Mar 20 14:07:20 at Timeout._onTimeout (/home/yellowtent/box/node_modules/connect-timeout/index.js:49:11) Mar 20 14:07:20 at listOnTimeout (node:internal/timers:605:17) Mar 20 14:07:20 at process.processTimers (node:internal/timers:541:7) { Mar 20 14:07:20 code: 'ETIMEDOUT', Mar 20 14:07:20 timeout: 60000 Mar 20 14:07:20 } Mar 20 14:07:20 } Mar 20 14:07:20 TypeError: Cannot read properties of undefined (reading 'manifest') Mar 20 14:07:20 at install (file:///home/yellowtent/box/src/routes/apps.js:136:32) Mar 20 14:07:20 at process.processTicksAndRejections (node:internal/process/task_queues:103:5) -
@rosano it works here. Did you change anything on your side? And also on the demo Cloudron . This looks like maybe there is some connectivity issue between your Cloudron and the app hosting the versions file. Have you run
cloudron-support --troubleshootalready?
-
@rosano it works here. Did you change anything on your side? And also on the demo Cloudron . This looks like maybe there is some connectivity issue between your Cloudron and the app hosting the versions file. Have you run
cloudron-support --troubleshootalready?
And also on the demo Cloudron.
Hmm yes it does work on the demo. Would there be an issue if the versions file is also hosted on the same Cloudron?
cloudron-support --troubleshootseems to be mostlyOKexcept for some kind of mail issue:[FAIL] Database migrations are pending. Last migration in DB: /20260217120000-mailPasswords-create-table.js. Last migration file: /package.json. Please run 'cloudron-support --apply-db-migrations' to apply the migrations. -
And also on the demo Cloudron.
Hmm yes it does work on the demo. Would there be an issue if the versions file is also hosted on the same Cloudron?
cloudron-support --troubleshootseems to be mostlyOKexcept for some kind of mail issue:[FAIL] Database migrations are pending. Last migration in DB: /20260217120000-mailPasswords-create-table.js. Last migration file: /package.json. Please run 'cloudron-support --apply-db-migrations' to apply the migrations. -
And also on the demo Cloudron.
Hmm yes it does work on the demo. Would there be an issue if the versions file is also hosted on the same Cloudron?
cloudron-support --troubleshootseems to be mostlyOKexcept for some kind of mail issue:[FAIL] Database migrations are pending. Last migration in DB: /20260217120000-mailPasswords-create-table.js. Last migration file: /package.json. Please run 'cloudron-support --apply-db-migrations' to apply the migrations. -
-
-
-
@rosano I meant the missing db migration issue is fixed and not the timeout issue.
Could there be some IPv4/IPv6 issue? Have you tried with curl -4 and curl -6 ?
Have you tried with curl -4 and curl -6 ?
Both
curl -4 https://bind.0data.app/CloudronVersions.jsonandcurl -6 https://bind.0data.app/CloudronVersions.jsonjust return the content.Well I guess as long as other people can install it maybe it's fine for now, but eventually I would like to run it with the same process so I know what it's like.
-
J joseph has marked this topic as solved on
-
Just for reference: I tried using a versions file hosted externally and I can install my app from there just fine, so maybe it does have to do with fetching a versions file on my own Cloudron. Not sure why as it's just over https but both hosted via Surfer and a custom app it seems to timeout.
-
Also similarly: I could start installing my app, but it fails on downloading the icon, which is also hosted on my Cloudron.
Mar 21 16:07:20 apptask: downloadIcon: Downloading community icon https://bind.0data.app/identity.svg Mar 21 16:08:20 community: Attempt 1 failed. Will retry: Network error downloading icon: The operation was aborted Mar 21 16:09:25 community: Attempt 2 failed. Will retry: Network error downloading icon: The operation was aborted Mar 21 16:10:31 community: Attempt 3 failed. Will retry: Network error downloading icon: The operation was aborted Mar 21 16:11:36 community: Attempt 4 failed. Will retry: Network error downloading icon: The operation was abortedAgain, not sure why this would behave differently but maybe I will write to support to go deeper.
-
@rosano yeah, not sure what the issue is. If it's important, write to us on support@cloudron.io and we will have to debug further.
-
Also similarly: I could start installing my app, but it fails on downloading the icon, which is also hosted on my Cloudron.
Mar 21 16:07:20 apptask: downloadIcon: Downloading community icon https://bind.0data.app/identity.svg Mar 21 16:08:20 community: Attempt 1 failed. Will retry: Network error downloading icon: The operation was aborted Mar 21 16:09:25 community: Attempt 2 failed. Will retry: Network error downloading icon: The operation was aborted Mar 21 16:10:31 community: Attempt 3 failed. Will retry: Network error downloading icon: The operation was aborted Mar 21 16:11:36 community: Attempt 4 failed. Will retry: Network error downloading icon: The operation was abortedAgain, not sure why this would behave differently but maybe I will write to support to go deeper.
-
@robi I tried with png in case you mean SVG is an issue, same thing.
Mar 23 09:51:19 tasks: updating task 16295 with: {"percent":15,"message":"Downloading icon"} Mar 23 09:51:19 apptask: downloadIcon: Downloading community icon https://static.rosano.ca/0data/identity.png Mar 23 09:52:19 community: Attempt 1 failed. Will retry: Network error downloading icon: The operation was aborted -
@robi I tried with png in case you mean SVG is an issue, same thing.
Mar 23 09:51:19 tasks: updating task 16295 with: {"percent":15,"message":"Downloading icon"} Mar 23 09:51:19 apptask: downloadIcon: Downloading community icon https://static.rosano.ca/0data/identity.png Mar 23 09:52:19 community: Attempt 1 failed. Will retry: Network error downloading icon: The operation was aborted -
Ok, I've solved this for my purposes.
Seems like when I try
curl -v https://bind.0data.app/CloudronVersions.jsonfrom my Cloudron, it fails.* Trying •••.••.••.••:443... * connect to •••.••.••.•• port 443 failed: Connection timed out * Failed to connect to bind.0data.app port 443 after 129437 ms: Connection timed out * Closing connection 0 curl: (28) Failed to connect to bind.0data.app port 443 after 129437 ms: Connection timed outWhich tells me there's some issue with loading URLs from the same server.
Interestingly, if I find the internal IP via
docker inspect <process> | grep '"IPAddress"'and port via
docker inspect <process> | grep -A5 '"Ports"'I can call successfully load the file with
curl -v -H "Host: bind.0data.app" http://<ip>:<port>/CloudronVersions.jsonBut I have decided it's easier for me to simply host a kind of URL masking thing on another server. Anyway thanks for the help and attention from everyone who chimed in


️ -
Similarly described in Unusable application:
Pushing/pulling an image from a remote works correctly. However, attempting to pull an image from the same server doesn't work at all.
I tried upgrading to Ubuntu 24.04 and it seems to work as expected now (versions file + icon on the same server without issue).
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login