-
-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Yet another SSL::SSLError issue #90
Comments
I'm seeing this on two of my servers (Ubuntu 14.04) but haven't been able to track it down. In those cases a simple call with curl also fails for the same reason (cert validation). Can you try a request with curl to confirm this? I am not yet sure whether this is an environment issue or actually an issue with MailChimp's SSL certs. Thanks, Sent from my iPhone
|
Sent a call to |
Note: Part of problem is because gibbon not set correct datacenter, and maybe the other issue is because don't delete |
I think I found the bugs, send a pull request with details asap. |
Thank you Thanks, Sent from my iPhone
|
Yesterday while I was debugging started to to work again. Definitely was Mailchimp problems. Anyway I had look to gibbon code and have refactored a bit, IMO only Is incomplete at the moment, Tell me if are interested on this. |
Closing this for now. I'll take a look when I get a moment. Sorry but the last few weeks have been a whirlwind for me in many ways. |
Hi,
if call
gb = Gibbon::API.new('XXXXXXXXXXXXXXXXXXX-us4')
get:note
us1
in the url. This happens both with api_keys created with mailchimp panel that those generated withomniauth-mailchimp
.Have tried also with:
Same error but in this case the url have
us4
.The text was updated successfully, but these errors were encountered: