Hey Rasmus, thanks for contributing your experience with Scalr! Note that this may also be due to a missing Scalr installation ID (which is also generated by testenvironment.php!).
We now have that documented (although we didn't at the time Cristian asked): https://scalr-wiki.atlassian.net/wiki/x/kQIh After seeing your comment, I added a note there indicating that this step matters a lot! Thanks! Thomas On Monday, January 20, 2014 4:22:19 PM UTC+1, Rasmus Kristensen wrote: > > Hey > > I had the same issue which I seem to have fixed by doing the following two > actions: > > running wget http://localhost/testenvironment.php -O /dev/null once after > setup to make sure /var/www/scalr/app/etc/.cryptokey was created > also I had to change the premissions on the /var/www/scalr/app/cache > directory so the apache2 user (www-data) could create files in it, as the > publickey is generated from the private key with ssh-keygen through a > temporary file. > chmod 777 /var/www/scalr/app/cache is the easy way out to check if it is > the problem. > > I hope this helps and avoid this http://xkcd.com/979/ ;) > > On Monday, October 7, 2013 5:26:56 PM UTC, Cristian Carstea wrote: >> >> Hi, >> >> i try to create a role builder in AWS using latest version of Scalr. It >> works ok until connecting to aws instance via SSH: >> Scalr unable to establish SSH connection with server on Error: Cannot >> login to SSH using PublicKey >> If i try to download public key from Scalr ssh keys, file is empty, also >> in DB field public_key is empty for SCALR-ROLESBUILDER-f605e590 key. >> What can be the issue? >> >> Thank you, >> Cristian >> > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
