Yeah! Works for me now as well. Thanks guys!
Phil On Oct 23, 4:24 am, Kyle Wilkie <[email protected]> wrote: > Kyle Wilkie <k...@...> writes: > > > Chap <chapambr...@...> writes: > > > > Anyone have problems using the Hostname Based Custom SSL and older > > > versions of Safari throwing errors such as "cannot get a secure > > > connection to the server"? > > > I started having the issue in early October on my workhorse machines > > that are running Safari 1.3.2 and OSX 10.3.9 (they're iBooks, can't go > > any higher OS or Safari revisions and I have 50 of them). One day they > > worked fine, the next they are unable to make a secure connection. > > Firefox, Opera both connect securely. Strangely, I can make an SSL > > connection to Amazon, but not Heroku itself or any of my apps. I am > > currently both piggyback and hostname ssl option on different sites, > > this behavior is the same. Found out today that one of my large clients > > is having the same problem with Safari 4.1.2 on OSX 10.4.11. > > > Oren at Heroku said nothing had changed there, but something did > > change somewhere. Any insight into what this is would be great! > > I was able to track down the root problem by getting my cert provider > (Digicert) to run a diagnostic and sent the results to Heroku. From > that, Heroku was able to track down and fix the problem which was that > default SSL ciphers had changed during server upgrades. > Certainly decomplicates my life! -- You received this message because you are subscribed to the Google Groups "Heroku" 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/heroku?hl=en.
