Answers.Body: <p>Stripe changed up some API URLs, which threw off Charge's legacy method for detecting TLS compatibility.</p>
  
  <p>The erroneous warning is <a href="https://twitter.com/TopShelfCraft/status/1051954976036028416" rel="nofollow noreferrer">fixed</a> in <a href="https://topshelfcraft.com/downloads/Charge-2-2-3.zip" rel="nofollow noreferrer">Charge 2.2.3</a>.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-13T16:16:28.000Z
Answers.Text: When can we expect a fix on this - pretty serious issue
Answers.UserDisplayName: Roi Agneta
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-15T22:06:56.130Z
Answers.Text: Howdy @RoiAgneta — That erroneous warning is actually harmless, but definitely annoying. Update to Charge 2.2.3 to get rid of it. 
Answers.UserDisplayName: Michael Rog
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-17T21:19:26.787Z
Answers.LastActivityDate: 2018-10-15T22:09:29.397Z
Answers.LastEditDate: 2018-10-15T22:09:29.397Z
Answers.UserDisplayName: Michael Rog
Answers.Body: <p>I'm not sure if this is helpful to anyone reading this thread, but I hacked at this a bit and made the Charge_CompatibilityService class testTLS12minimum method echo the message from the exception. It indicated a failure resolving the API host. I commented out line 26 where it sets the $spiBase variable:</p>
  
  <p>//\Stripe\Stripe::$apiBase = "<a href="https://api-tls12.stripe.com" rel="nofollow noreferrer">https://api-tls12.stripe.com</a>";</p>
  
  <p>I assume it now falls back on the API host defined in the /vendor folder. This appears to have resolved the issue, though I haven't finished the rest of my Stripe account setup so I haven't confirmed it is working end to end.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-10-24T18:04:17.797Z
Answers.Text: The erroneous warning is [fixed](https://twitter.com/TopShelfCraft/status/1051954976036028416) in [Charge 2.2.3](https://topshelfcraft.com/downloads/Charge-2-2-3.zip).
Answers.UserDisplayName: Michael Rog
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-09-11T16:22:51.443Z
Answers.LastActivityDate: 2018-09-11T16:22:51.443Z
Answers.UserDisplayName: Bill Bushee
Body: <p>I am getting an error notice in the Squarebit Charge plugin saying This server doesn't support TLS 1.2. but when I check with the hosting provider (Arcustech, the best!) they assure me that the server does indeed support TLS 1.2</p>
  
  <p>Further, I do not see any errors when I look at a charge detail in the connected Stripe account. This has just recently popped up on a few of my projects.</p>
  
  <p>Make sense to anyone?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-08-20T10:02:25.000Z
Comments.Text: If you don't get a response from Michael (answer below), their Plugin changelog is here: https://transition.topshelfcraft.com/software/craft/charge/updates
Comments.UserDisplayName: Jay
Tags: <plugin-charge>
Title: Error declaring TLS Version wrong in Charge plugin
ThreadText: # Error declaring TLS Version wrong in Charge plugin
  
  (Asked by: username_0 on 2018-08-17)
  
  I am getting an error notice in the Squarebit Charge plugin saying This server doesn't support TLS 1.2. but when I check with the hosting provider (Arcustech, the best!) they assure me that the server does indeed support TLS 1.2
  
  Further, I do not see any errors when I look at a charge detail in the connected Stripe account. This has just recently popped up on a few of my projects.
  
  Make sense to anyone?
  
  **Tags:** plugin-charge
  
  > **Comments:**
  > **username_1**: If you don't get a response from username_2 (answer below), their Plugin changelog is here: https://transition.topshelfcraft.com/software/craft/charge/updates  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2018-08-17. Score: 2
  
  Stripe changed up some API URLs, which threw off Charge's legacy method for detecting TLS compatibility.
  
  The erroneous warning is [fixed](https://twitter.com/TopShelfCraft/status/1051954976036028416) in [Charge 2.2.3](https://topshelfcraft.com/downloads/Charge-2-2-3.zip).
  
  > **Comments:**
  > **username_0**: When can we expect a fix on this - pretty serious issue  
  > **username_2**: Howdy @username_0 — That erroneous warning is actually harmless, but definitely annoying. Update to Charge 2.2.3 to get rid of it.   
  
  ---
  
  ### Answer by username_3 on 2018-09-11. Score: 1
  
  I'm not sure if this is helpful to anyone reading this thread, but I hacked at this a bit and made the Charge\_CompatibilityService class testTLS12minimum method echo the message from the exception. It indicated a failure resolving the API host. I commented out line 26 where it sets the $spiBase variable:
  
  //\Stripe\Stripe::$apiBase = "<https://api-tls12.stripe.com>";
  
  I assume it now falls back on the API host defined in the /vendor folder. This appears to have resolved the issue, though I haven't finished the rest of my Stripe account setup so I haven't confirmed it is working end to end.
  
  > **Comments:**
  > **username_2**: The erroneous warning is [fixed](https://twitter.com/TopShelfCraft/status/1051954976036028416) in [Charge 2.2.3](https://topshelfcraft.com/downloads/Charge-2-2-3.zip).  
  
  ---
  
  