mbeam

Unsure of what changed, or what was done but everything is working again with no code changes by me .

yeah i know , i just rambled it off from the top of my head. sounded right when i was typing it

but thats the url i used that returned a csrf error when i submitted twice. 

While researching issues with a curl script  ( https://www.byet.net/index.php?/topic/2388-curl-errors/ )

I've discovered that  byet Server  SSL Version:   OpenSSL/1.0.1e released 2013-02-11 is outdated and unsecure : 

( found via phpinfo info script )

https://www.cvedetails.com/vulnerability-list/vendor_id-217/product_id-383/version_id-157548/Openssl-Openssl-1.0.1e.html

Support for OpenSSL 1.0.1 ended on 31st December 2016 and is no longer receiving security updates

The last 2 tickets I tried starting on ifast.net resulted in either timeout issues or failed to send...

Could someone pass this along to a server admin , to see if it can be updated , ( and to see if it will fix my curl error issues  )?

thanks

Well i bought a cheap domain https://mypodcast.info/  and directed it thru cloudflare back to the  byet.net hosting ,

everything shows the ssl is working  and as shown in the  sample code i gave above,  i am using https in the curl / cron job

and its still not working ..

I also noticed filezilla ftp client also pops up with a certificate warning when connecting to transfer files ..

So im still investigating.. nothing has worked yet , 

Cloudfare : 

Quote

 

We were unable to identify mypodcast.is-great.net as a registered domain

Please ensure you are providing the root domain and not any subdomains (e.g., example.com, not subdomain.example.com) (Code: 1099)

 

I never had to set a ssl cert before to get it to work, im just trying it as a possible solution.

The  site is on free hosting , https://mypodcast.is-great.net/ 

The cron job is at https://mypodcast.is-great.net/cron.php to see the errors

Like i said nothing was changed in my code
 

$ch = curl_init();
curl_setopt_array($ch, array( 
CURLOPT_HTTPHEADER => array('Client-ID: ' . (api_key_removed)),
CURLOPT_RETURNTRANSFER => true,
CURLOPT_URL => https://api.twitch.tv/kraken/streams/(removed), 
) );
$tresponse = curl_exec($ch);
$curl_error = curl_error($ch);
$curl_errno = curl_errno($ch);
$data = curl_exec($ch);
curl_close($ch);

if ($curl_errno > 0) { echo "<br>cURL Error ($curl_errno): $curl_error" ;}

Working version on my home network on a raspberry pi : https://podview.ddns.net/

The same code works fine on my home network using a web server on my raspberry pi,

A server side configuration change has been made from what i can tell with my research.

I have tried re enabling / re issuing a ssl in the control panel to see if it helps and is still a no go.

I have also tried https://letsencrypt.org/  to generate a cert but failed due anti bot security response <script type="text/javascript" src="/aes.js" ></script>

that is returned when trying to validate, 

I have also tried adding  CURLOPT_SSLVERSION => 3, to the curl script to force version and still a no go.

TLDR :

Im still stuck and its not working.

I have a php cron script that uses curl to check  twitch.tv to see if a users stream is live or not.

everything was working fine last week , I didn't change anything in my code

but now im getting :

cURL Error (35): error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol

errors when the cron runs 

any ideas what changed or whats going on ?