SSL error

Shawn Mclean's Avatar

Shawn Mclean

05 Aug, 2012 03:08 AM

When I use cURL to run a test on get_account_info, I get this error:

  • About to connect() to api.postageapp.com port 443 (#0)
  • Trying 69.164.203.212...
  • connected
  • Connected to api.postageapp.com (69.164.203.212) port 443 (#0)
  • SSLv3, TLS handshake, Client hello (1):
  • SSLv3, TLS handshake, Server hello (2):
  • SSLv3, TLS handshake, CERT (11):
  • SSLv3, TLS alert, Server hello (2):
  • SSL certificate problem: self signed certificate in certificate chain
  • Closing connection #0 curl: (60) SSL certificate problem: self signed certificate in certificate chain

When I run it with --unsecure, I get this error:

  • Connected to api.postageapp.com (69.164.203.212) port 443 (#0)
  • SSLv3, TLS handshake, Client hello (1):
  • SSLv3, TLS handshake, Server hello (2):
  • SSLv3, TLS handshake, CERT (11):
  • SSLv3, TLS handshake, Server key exchange (12):
  • SSLv3, TLS handshake, Server finished (14):
  • SSLv3, TLS handshake, Client key exchange (16):
  • SSLv3, TLS change cipher, Client hello (1):
  • SSLv3, TLS handshake, Finished (20):
  • SSLv3, TLS change cipher, Client hello (1):
  • SSLv3, TLS handshake, Finished (20):
  • SSL connection using DHE-RSA-AES256-SHA
  • Server certificate:
  •  subject: O=*.postageapp.com; OU=Domain Control Validated; CN=*.postagea
    

    pp.com

  •  start date: 2011-04-06 14:21:55 GMT
    
  •  expire date: 2013-05-10 16:50:28 GMT
    
  •  subjectAltName: api.postageapp.com matched
    
  •  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://
    

    certificates.godaddy.com/repository; CN=Go Daddy Secure Certification Authority;
    serialNumber=07969287

  •  SSL certificate verify result: self signed certificate in certificate c
    
    hain (19), continuing anyway.

    POST /v.1.0/get_account_info.json HTTP/1.1 User-Agent: curl/7.26.0 Host: api.postageapp.com Accept: / Content-type: application/json Content-Length: 2

  • upload completely sent off: 2 out of 2 bytes < HTTP/1.1 401 Authorization Required
    < Date: Sun, 05 Aug 2012 03:07:29 GMT
    < Server: Apache/2.2.22 (Fedora) DAV/2 Phusion_Passenger/3.0.11 mod_ssl/2.2.22 O
    penSSL/1.0.0h-fips
    < X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.11
    < Cache-Control: no-cache
    < X-Runtime: 2
    < Content-Length: 94
    < Status: 401
    < Connection: close
    < Content-Type: text/html; charset=utf-8
    <
    {#0
  • SSLv3, TLS alert, Client hello (1):

It has been happening for about 2 days now on my free account.

  1. 2 Posted by Scott Tadman on 08 Aug, 2012 02:44 PM

    Scott Tadman's Avatar

    This problem has been reported on OS X 10.7. It seems to be related to a particular version of cURL which doesn't recognize certain kinds of root-level certificates. The equivalent test on other systems does not have the same failure. Strangely even the certificate from the certificate provider suffers from the same sort of problem.

    In an effort to eliminate this problem, the SSL certificate for api.postageapp.com will be replaced with one from a different vendor.

  2. Postage Admin closed this discussion on 07 May, 2013 02:38 PM.

Discussions are closed to public comments.
If you need help with PostageApp please start a new discussion.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions

16 Apr, 2014 02:30 PM
13 Feb, 2014 06:11 PM
13 Feb, 2014 04:08 PM
06 Feb, 2014 03:27 PM
21 Jan, 2014 04:08 PM