dan-bowen
commented
6 years ago The fact that it works on staging seems to indicate a problem on the production server, not the library. I would verify your service can make outbound https requests and double check your chargify credentials.
On Nov 6, 2017, at 4:04 PM, Teneobelgium notifications@github.com wrote:
No matter what I do or try, I keep getting the same error. I have developed everything on a staging server and it works fine. When i move it to our production servers we get the error below. No matter what call I make (subscriptions, transactions, ...) nothing works on server A while on server B the exact same script works fine. I have checked everything again and again but I must overlook something obvious.
The error we are getting in the response is :
{ ["Crucial_Service_Chargify"]=> array(1) { ["networking error"]=> string(11) "no response" } }
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
ghost
No matter what I do or try, I keep getting the same error. I have developed everything on a staging server and it works fine. When i move it to our production servers we get the error below. No matter what call I make (subscriptions, transactions, ...) nothing works on server A while on server B the exact same script works fine. I have checked everything again and again but I must overlook something obvious.
The error we are getting in the response is :
{ ["Crucial_Service_Chargify"]=> array(1) { ["networking error"]=> string(11) "no response" } }