Quote from: Kazuldur on November 21, 2016, 09:02:52 PM

Quote from: ePay.info on November 21, 2016, 08:54:05 PM

Hi
I think some servers have problem connect to HTTPS over SOAP
can you try catche it ?

try{
   $client = new SoapClient('https://apis.epay.info/?wsdl');
}catch(Exception $e){
   $client = new SoapClient('http://api.epay.info/?wsdl');
}

Altough we prefer SOAP

No way I'll allow HTTP connections in Faucet in a BOX script Wink

. Catching and displaying human-readable error is a good idea though.

What CloudFlare plan do you have on ePay.info? SSL with the Free plan doesn't work with old OpenSSL's and old browsers (there's no "Legacy browser support" for free plans). You can read details here: https://support.cloudflare.com/hc/en-us/articles/214770928-Legacy-Browser-Support . I remember that was a big problem on FaucetBOX.com when we disabled this legacy browser support.

However it's almost 2017 now. I'd argue that connection problems in this case aren't ePay.info's fault. If those faucets can't connect to your API using modern HTTPS, it's their problem and they should change/update their hostings.

We have pro plan
I agree that no https should be used and it is 2017
but there are still some people that cant update their system and we must have them in mind too