$scope.configureBackup is undefined

[mehdi]

@girish Same error when filling the form manually

[mehdi]

@girish Nice trick. Just tried it, i managed to get the page in Chrome. However, I still get the same error : TypeError: Cannot read properties of undefined (reading 'backupFolder') is the exact wording in Chrome

[mehdi]

@girish said in $scope.configureBackup is undefined:

Does curl -k https://ip/restore.html work OK?

Yes, it does work OK.

[girish]

@mehdi OK, just to rule out the obvious, I tried to backup/restore 7.0.4 install myself and it seems to work. I used Vultr Object Storage.

Not sure what the problem is, do you think you can send the IP to support@cloudron.io ? And maybe the json as well (it doesn't have the secrets, so should be safe).

[mehdi]

@girish maybe it's specific to the filesystem backup restore process? I can send you the IP, sure, but to be safe (as I had not seen the new generate-setup-token parameter in the doc ^^) I have systemctl stop box for the time being. Can I enable generate-setup-token after the initial install, with the CLI ?

[mehdi]

I have managed to add a SETUP_TOKEN after the fact (for anyone interested, simply run openssl rand -hex 10 > /etc/cloudron/SETUP_TOKEN as root). I have sent you the IP and token by email.

BTW, I have also tried other backup providers on the interface (with arbitrary data in the form), and they seem to indeed send a web request. So I believe the issue is on the front-end side, and specific to the filesystem backup provider.

[mehdi]

@girish Found the error : https://git.cloudron.io/cloudron/dashboard/-/blob/master/src/js/restore.js#L292

backupConfig.backupFolder = $scope.configureBackup.backupFolder;

should be

backupConfig.backupFolder = $scope.backupFolder;

[mehdi]

Now getting an error 400 setup token required. The setup token is in the URL, and in the network tab i do see it being sent in the request...

[mehdi]

Managed to get the restore working, by fixing the /home/yellowtent/box/dashboard/dist/js/restore.js file manually on the server, with the fix explained above, and removing the SETUP_TOKEN file. I did not go to the length of looking for the root cause of the setup token thing not working, probably the variable being sent inside an object instead of at the root of the JSON request or something.

[nebulon]

Great investigation! I have fixed up that copy and paste error in the restore.js now

[mehdi]

@nebulon Thanks ! I'll let you look for the precise fix for the SETUP_TOKEN problem by yourselves though ^^

[girish]

@mehdi this was indeed a bug in the restore code path. the setupToken, as you guessed, should be sent in the top level object and not as part of the backupConfig . Fixed now.