We are using a Open Source Scalr Server and Chef 12.0.5 with SSL Enabled.. On Wednesday, 3 June 2015 18:50:48 UTC-7, Vikas Gupta wrote: > > Correction: From ProxyScalr Server i can CURL into the Chef Server URL, > From the ScalrUI i cannot > > On Wednesday, 3 June 2015 18:38:46 UTC-7, Vikas Gupta wrote: >> >> Yes, from Proxy Scalr i am able to access the chef server via CURL.. >> however it fails via Chef UI >> >> On Monday, 1 June 2015 04:18:56 UTC-7, Daniele Testa wrote: >>> >>> Hi Vikas! >>> >>> Could you please check the PHP log for errors. It looks like your Scalr >>> installation is not able to connect to the Chef server. >>> Could you also provide details how you configured Scalr to use the proxy. >>> Did you verify that the proxy is able to access the Chef server? >>> >>> Regards, >>> Daniele >>> >>> >>> On Monday, June 1, 2015 at 2:39:35 AM UTC+8, Vikas Gupta wrote: >>>> >>>> I have a private Chef server 12.0.5, while integrating with Scalr it >>>> thorws error "Empty or too short HTTP message: ''" >>>> >>>> I have verified the Chef Server URL using CURL and the response is all >>>> good. >>>> >>>> We have deployed Scalr Open Source and architecture as >>>> https://scalr-wiki.atlassian.net/wiki/display/docs/Production+Deployment+Recommendations >>>> >>>> >>>> The Chef Server URL is hosted via ELB.. we have verified that CURL is >>>> able to reach the Chef Server ELB from Scalr Instances.. >>>> >>>> Via Scalr UI we are unsuccessful....The Proxy is Set for Scalr >>>> Server... >>>> >>>> At this point we are stuck while integrating Chef with Scalr.. Please >>>> help... >>>> >>>
-- 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.
