What I did: 1. add a DNS entry that points dev to spartalab.com. dev 14400 CNAME spartalab.com. (note the trailing dot) 2. modify security group of www (nginx role) to allow port 443. Do it in command line or use ElasticFox firefox addon. Scalr's security group modification didn't save back then. 3. change /etc/nginx/nginx.conf to use certificates: http://code.google.com/p/scalr/wiki/HTTPS 4. restart nginx: /etc/init.d/nginx stop; sleep 1; /etc/init.d/nginx start
On Tue, Dec 9, 2008 at 12:31 AM, 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 -~----------~----~----~----~------~----~------~--~---
