User Data: Account Balance Updates, Trade Updates, New Orders, Filled Orders, Cancelled Orders via WebSocket about php-binance-api HOT 10 CLOSED

I'll check it out, i've got limited availability this week but i will try

from php-binance-api.

I have the same error while using trades function (aggTrade), after about 10 minutes the connection closes with 1006 error and php notice for undefined symbol.

It used to work a few days ago, do you know what s happening?

from php-binance-api.

I am not sure. Binance is changing things faster than I can keep up, only now they are not notifying us of changes

from php-binance-api.

I understand, please let us know if you find something, anyway this api is useful and having it to work serverside is way better for data manipulation and backup, thank you for sharing your work with us!

from php-binance-api.

Hi - Firstly thanks for all the hard wok you put into this Jaggedsoft.

Anyone got this working yet?

from php-binance-api.

hey man, ya, I'm trying to just fetch something and its returning an empty array. any idea when you might have a working example? I do see from cointracking.info that they are saying binance's api is unusable right now? weird. Do you know what they're doing or when they might make it usable? thanks for putting all this together. we all appreciate it. Justin

from php-binance-api.

from php-binance-api.

oh ya? wierd. I couldn't get anything to work as is. I just now got it going by adding this to the php-binance-api.php the ssl option to ignore verification...
$opt = [
"http" => [
"method" => $method,
"ignore_errors" => true,
"header" => "User-Agent: Mozilla/4.0 (compatible; PHP Binance API)\r\n"
],
"ssl" => [
"verify_peer"=>false,
"verify_peer_name"=>false,
]

because i kept getting: Warning: file_get_contents(): SSL operation failed with code 1. OpenSSL Error messages: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

Now I'm able to get the contents just fine. I know it isn't as secure but is it that important? I'm guess that has to do with my own ssl cert? Right now I'm just testing on a codeanywhere stack. Maybe that is it.

from php-binance-api.

If anyone else runs into this, your pem file might be outdated or in the wrong location.

First, get the locations of where PHP thinks they are:
$ php -r "print_r(openssl_get_cert_locations());"
Array
(
[default_cert_file] => /usr/local/openssl/cert.pem
[default_cert_file_env] => SSL_CERT_FILE
[default_cert_dir] => /usr/local/openssl/certs
[default_cert_dir_env] => SSL_CERT_DIR
[default_private_dir] => /usr/local/openssl/private
[default_default_cert_area] => /usr/local/openssl
[ini_cafile] =>
[ini_capath] =>
)
Second: Download http://curl.haxx.se/ca/cacert.pem:
$ wget http://curl.haxx.se/ca/cacert.pem
Third: Copy certificate PEM file into default_cert_file location:
$ sudo mv cacert.pem /usr/local/openssl/cert.pem

Verification should now work as expected.

from php-binance-api.

Todo: add error reporting

from php-binance-api.