$scope.configureBackup is undefined
-
@mehdi said in $scope.configureBackup is undefined:
trying to import the backup configuration into the new server
FWIW, you can just fill that form manually instead of importing from the json file and see if that helps. If you open up the json, you can just fill up those values in the form.
-
@girish said in $scope.configureBackup is undefined:
Does curl -k https://ip/restore.html work OK?
Yes, it does work OK.
-
@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).
-
@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 havesystemctl stop box
for the time being. Can I enablegenerate-setup-token
after the initial install, with the CLI ? -
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.
-
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 theSETUP_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. -