TKLBAM: "Restore to new cloud server" does not work

Hello,

I am trying to test the "Restore to new cloud server" feature. However, when on the "Launch to Amazon EC2" page, clicking on "Launch" does nothing. There is no JavaScript Error or error message, just nothing.

Here are the details:

TurnKey appliance: LAMP Stack

Region: Ireland

Size: T1.Micro

Any ideas why it is not working?

Replies (8)

Hmmm, sounds weird

Reply 1 2015-11-17

Thanks for reporting. Could you please log into your Hub account and send me a brief note using the "feedback" feature (top of the page, second from the left). That will make it easier for me to find your account and see what I can see...

Oops...

Reply 2 2015-11-17

I just realised that it looks like you have already! No need to send a new one (assuming that you're the same Christian)! I'll reply offline! :)

Seems to be a Firefox-Specific Issue

Reply 3 2015-11-18

It worked when I tried it at home on my Mac with Safari. At work, using a Windows 7 - PC and Firefox 42.0, no luck. Using Microsoft Internet Explorer 11, I was able to launch it. Now waiting for the server to boot ...

Glad you found that...

Reply 4 2015-11-20

I should have probably anticipated that issue... As I noted on that other thread I have just created a docs page detailing that (and other stuff that may need doing)...

It sort of works, but ...

Reply 5 2015-11-18

... I cannot access the HTTPS port. See

/forum/support/20151112/tkl-trac-14-applianc...

Straight 14.0 to 14.0 migration

Reply 6 2015-11-20

Hi Jeremy, thanks, but in my case, it's a straight 14.0 to 14.0 migration, not a restore from a 13.0 backup... I need to test a third option: not restore the backup directly, but launch a LAMP server and then restore the backup. This will allow me to test if the HTTPS access is broken by the restore. BTW is the root password that will be generated by the "Launch server in the cloud" overwritten by the restore or will it remain?

Glad you got it sorted

Reply 7 2015-11-23

NP Christian, it happens to the best of us! :)

Ok, found the error ...

Reply 8 2015-11-20

... and it did not have anyhing to do with the referenced bug: my custom SSL certificate had not been saved in the backup because it was at an non-standard location (/). So sorry for the noise and thanks for looking into the problem.