You have www in your farm, but pointed DNS to app. Scalr can create HTTPS-enabled virtual hosts on both www and app. In case if you have www in the farm, nginx handles HTTPs and proxies plain HTTP traffic on Application Servers instances.
HTTPS directly on app was not tested well, we're fixing some issues in virtual host template cert files naming and adding 443 into security groups. I will update here when its finished. On 09.12.08 07:31, "David Allen" <[EMAIL PROTECTED]> wrote: > I enabled SSL and uploaded a self signed certificate and key tonight > with some strange results... > > First, I get a server not found error when I attempt to hit the url > https://dev.spartalab.com/ > . > > Second, on inspection I see the naming convention for the uploaded key/ > cert is dev.spartalab.com.crt & dev.spartalab.com.key which is great > - unambiguous. However, looking at app-default-ssl.vhost.conf (the > conf file apparently modified by scalr based on time date stamp) I > noticed that the expected key/crt were https.key and https.crt. I > edited the conf file to point to the key/crt. No resolution to the > problem. > > Third, when I turned on SSL I expected Scalr to enable 443 on the app > in the Security Groups. It did not so I did so manually. Still no go. > > Have I hosed the config? Farm name is LabCloudDev. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
