XF 2.0 Recent SSL problem

[jul]

Dear Xenforo Community,

Today I've encountered a very nasty error that occurred out of nowhere. On my forums I run the Steam Integration add-on as main login/register. It ran like it should for around two months up until today.

After a conversation with the developers of the add-on we came to a conclusion it wasn't really related to the add-on itself but to the SSL of my webserver.
I've contacted my webhost provider to see what the problem is but unfortunately they came with no answers.

Hopefully there are some Xenforo pro's here or people who have experienced the same kind of issue that may be able to help me out.

Error:

error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

PHP is erroring on curl_exec:

$response = curl_exec($this->_curl);
if ($response === false) {
    throw new \Exception(curl_error($this->_curl), curl_errno($this->_curl));
}

Steps:

1. User presses the login/register button of Xenforo.
2. User uses the Steam (Intergration) button to login/register by steam.
3. User gets redirected to the Steam login page.
4. User fills out account details and logs in Steam.
5. After Steam validation it returns back to my site.
6. Normally in this step the user is logged in into my forums but now they receive the following error:

The strangest thing about all of this is that I had no problems for months and randomly got this issue today without making any changes.


Thanks for reading!

 

[Mike]

Based on the error, it looks like you'r trying to connect using older SSL protocols and that's being rejected.

Based on the code you've shown, it looks like the developer is making direct cURL requests (unless it's coming from an underlying library they've included), which is actually specifically mentioned in our resource standards. So if the author is doing their own HTTP requests, then I would kick this back to them as that's actually a violation of our standards, but beyond that, it means that they're not using the HTTP request system that XF provides, which is based off of a well tested framework and thus using it is likely to reduce instances of these sort of issues.

 

[jul]

Based on the error, it looks like you'r trying to connect using older SSL protocols and that's being rejected.

Based on the code you've shown, it looks like the developer is making direct cURL requests (unless it's coming from an underlying library they've included), which is actually specifically mentioned in our resource standards. So if the author is doing their own HTTP requests, then I would kick this back to them as that's actually a violation of our standards, but beyond that, it means that they're not using the HTTP request system that XF provides, which is based off of a well tested framework and thus using it is likely to reduce instances of these sort of issues.

Thank you very much for your reply.

After having another day of frustration we did find out the problem to this all. My webhost provider apparently had a cURL version out of 2015. After many conversations with their support and them denying anything to be wrong from their side we decided to move over to a different hosting provider. Especially after they mention the only way for me to have an updated cURL is by paying more by upgrading my plan.

This can be considered solved.