No, no changes to secrets. I actually disabled https to investigate this issue further and it works again without https.
On Monday, August 17, 2015 at 1:21:22 AM UTC-4, Daniele Testa wrote: > > Hi! > > Did you make any changes to the scalr-server-secrets.json file? > > Regards, > Daniele > > > On Monday, August 17, 2015 at 1:12:13 PM UTC+8, Dmitri Toubelis wrote: >> >> I'm testing Scalr open source 5.8.29 and I set it up and I was able to >> create and start instances in amazon cloud. Then I followed instructions >> from you wiki on how to enable SSL/TLS and I was able to loging into Scalr >> web interface in web browser via https (redirect is enabled as well). Right >> after that if I start any new instance it will stay in Pending state it is >> terminated upon timeout. I was able to log in into the new instance and >> check Slaraizr log files. I found the following: >> >> ... >> 2015-08-16 21:58:53,532-07:00 - WARNING - >> scalarizr.messaging.p2p.producer - Message 'HostInit' not delivered >> (message_id: 319dc9f3-0f9b-44f8-a677-f73388e2902f) >> 2015-08-16 21:58:53,533-07:00 - WARNING - >> scalarizr.messaging.p2p.producer - Cannot authenticate on message server. >> 401 Client Error: Signature doesn't match >> ... >> >> What did I do wrong? >> > -- 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/d/optout.
