KeyError: 'cloudronId' during 7.5 setup

[potemkin_ai]

Things are not going well for me for 7.5 release...

wget https://cloudron.io/cloudron-setup
chmod +x ./cloudron-setup
./cloudron-setup --setup-token <reducted>
--2023-07-15 08:48:48-- 
https://cloudron.io/cloudron-setup
Resolving cloudron.io (cloudron.io)... 165.227.67.76, 2604:a880:800:10::b66:f001

Connecting to cloudron.io (cloudron.io)|165.227.67.76|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 11377 (11K) [application/octet-stream]
Saving to: ‘cloudron-setup’

cloudron-setup                            100%[====================================================================================>]  11.11K  --.-KB/s    in 0s

2023-07-15 08:48:49 (217 MB/s) - ‘cloudron-setup’ saved [11377/11377]


##############################################
         Cloudron Setup (latest)
##############################################

 Follow setup logs in a second terminal with:
 $ tail -f /var/log/cloudron-setup.log

 Join us at https://forum.cloudron.io for any questions.

=> Updating apt and installing script dependencies
=> Checking version
=> Downloading Cloudron version 7.5.0 ...
=> Installing base dependencies and downloading docker images (this takes some time) ...
=> Installing Cloudron version 7.5.0 (this takes some time) ...
Traceback (most recent call last):
  File "<string>", line 1, in <module>
KeyError: 'cloudronId'


$ tail /var/log/cloudron-setup.log
[INFO] Processed migration 20220922194751-tokens-add-scopeJson
[INFO] Processed migration 20230309095335-blobs-rename-sftp-key-names
[INFO] Processed migration 20230316134353-oidc-clients-add-table
[INFO] Processed migration 20230318141011-apps-add-enableTurn
[INFO] Processed migration 20230329084726-apps-add-enableRedis
[INFO] Processed migration 20230404140451-oidc-clients-add-tokenSignatureAlgorithm
[INFO] Done
2023-07-15T08:54:43 ==> start: Changing ownership
2023-07-15T08:54:43 ==> start: Starting Cloudron
2023-07-15T08:54:45 ==> start: Almost done

[girish]

@potemkin_ai Thanks for reporting, I tested this in Digital Ocean , Vultr and Linode by now and cannot reproduce this. Which server provider are you using?

[girish]

I could reproduce it when the setup token was not valid anymore. I guess you might have given a wrong key or revoke the key in cloudron.io before installation. I have fixed this now, the new setup script will be deployed along side 7.5.1 .

[potemkin_ai]

@girish setup token was valid, instance appeared on the console. But, it appeared as 7.5, while I set up 7.4.3 (after removing 7.5 due to all of the issues).

[girish]

@potemkin_ai I see, . I have improved the cloudron-setup script now so that it checks for the token before hand (way before installation starts). That way if the token is bad, it will fail and you can re-run intsall command. There is also the case where maybe api.cloudron.io is unreachable to validate the token. Both the cases were unhandled before and are handled now and reported accordingly. Thanks for reporting!

[potemkin_ai]

@girish Thank you!