Signut Posted October 1, 2018 Posted October 1, 2018 When installing Stripe Module v1.6.5 , at the point where the Module requests to check TLS1.2 support, activating the 'Button' creates a long page of code: object(GuzzleHttp\Exception\ConnectException)#123 (10) { ["request":"GuzzleHttp\Exception\RequestException":private]=> object(GuzzleHttp\Psr7\Request)#115 (7) { ["method":"GuzzleHttp\Psr7\Request":private]=> string(3) "GET" ["requestTarget":"GuzzleHttp\Psr7\Request":private]=> NULL ["uri":"GuzzleHttp\Psr7\Request":private]=> o....................... Our Server does support TLS1.2. Are there any settings we can change in Thirtybees that would avoid generating this error? We would be grateful for any suggestions to enable the Stripe module to work successfully. Thanks.
datakick Posted October 1, 2018 Posted October 1, 2018 It seems that endpoint https://api-tls12.stripe.com no longer exists -- domain can't be resolved to IP address. Github issue: https://github.com/thirtybees/thirtybees/issues/614
Signut Posted October 1, 2018 Author Posted October 1, 2018 OK, we will stand back from Stripe for now. Thank you for your fast reply. Signut.
datakick Posted October 1, 2018 Posted October 1, 2018 Until this is fixed, you can bypass this validation. Edit file modules/stripe/stripe.php, and change lines 959..971 from php protected function tlsCheck() { $guzzle = new GuzzleClient(); \ThirtyBeesStripe\Stripe\ApiRequestor::setHttpClient($guzzle); \ThirtyBeesStripe\Stripe\Stripe::setApiKey('sk_test_BQokikJOvBiI2HlWgH4olfQ2'); \ThirtyBeesStripe\Stripe\Stripe::$apiBase = 'https://api-tls12.stripe.com'; try { \ThirtyBeesStripe\Stripe\Charge::all(); $this->updateAllValue(static::TLS_OK, static::ENUM_TLS_OK); } catch (\ThirtyBeesStripe\Stripe\Error\Api $e) { $this->updateAllValue(static::TLS_OK, static::ENUM_TLS_ERROR); } } to php protected function tlsCheck() { $this->updateAllValue(static::TLS_OK, static::ENUM_TLS_OK); }
Signut Posted October 1, 2018 Author Posted October 1, 2018 Thank you for the 'Bypass' information. After instigating this change, the Module worked as we hoped and the Data in both the Stripe Account and Thirtybees BO appears correct. We will somehow need to improve the Checkout visual display/layout, (nb. TB 1.0.7 / Warehouse 3.8.6) but at least it now works. We are certainly very grateful for your help. Signut.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now