View Single Post
Old 04-09-2015, 04:33 AM   #14
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,467
Karma: 8025600
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by bossanova808 View Post
Hmm, ok, it seems it is using verifypeer with ssl? I changed from GoDaddy to RapidSSL certificate a while back...but it's still a full certificate.
Did you add the certificate chain to your server? I have a cheap comodo "positiveSSL" cert and peer verification didn't work until I added both the intermediate and the root cert to the server's SSL chain bundle. For apache, this involves adding something like the following to ssl-sites.conf:
Code:
    SSLCertificateFile /etc/ssl/tho.new/tho.crt
    SSLCertificateKeyFile /etc/ssl/tho.new/tho.key
    SSLCertificateChainFile /etc/ssl/tho.new/bundle.crt
Quote:
Most stuff turns verifypeer off in general, for compatibility with self signed etc.
Browsers and the like have dialogs to accept certs that are not verifiable, expired, or have the wrong site name. My guess is that you had to do that the first time you connected from your device using chrome or whatever.

I am not willing either to add those dialogs or to turn off peer verification.
chaley is offline   Reply With Quote