Open brizzbane opened 3 years ago
More info:
ft_dnsmasq | dnsmasq: query[A] api.binance.com from 10.99.0.2 ft_dnsmasq | dnsmasq: config api.binance.com is 10.99.7.251 ft_hitch | 20210221T194950.366894 [ 9] 10.99.0.2:34214 :0 7:8 proxy connect ft_hitch | 20210221T194950.366915 [ 9] 10.99.0.2:34214 :0 7:8 ssl handshake start ft_hitch | 20210221T194950.366942 [ 9] 10.99.0.2:34214 :0 7:8 ssl client handshake revents=1 ft_hitch | 20210221T194950.367352 [ 9] 10.99.0.2:34214 :0 7:8 ssl client handshake err=SSL_ERROR_WANT_READ ft_hitch | 20210221T194950.367469 [ 9] 10.99.0.2:34214 :0 7:8 ssl client handshake revents=1 ft_hitch | 20210221T194950.367497 [ 9] 10.99.0.2:34214 :0 7:8 ssl client handshake err=SSL_ERROR_SSL ft_hitch | 20210221T194950.367514 [ 9] 10.99.0.2:34214 :0 7:8 Handshake failure: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate ft_hitch | 20210221T194950.367531 [ 9] 10.99.0.2:34214 :0 7:8 proxy shutdown req=SHUTDOWN_SSL ft_hitch | 20210221T194950.367544 [ 9] 10.99.0.2:34214 :0 7:8 proxy shutdown req=SHUTDOWN_HARD
@berlinguyinca Hey ;). I think original author might be MIA.. Was just wondering if you might have any idea? I've been messing with this and have no idea. Have tried updating Hitch thinking maybe SSL would be fixed, but that hasn't worked.
It looks like the author was in contact with you. Were you able to get it running? Did you run into this error? I have tried with other sites like "kraken", and "bittrex", both have same hangup with hitch.
If you can provide any insight or direction that would be awesome! Really looking to get something setup to help w/API cache.
This has been long left behind and is no further being developed.
On Sun, Feb 21, 2021, 2:47 PM brizz notifications@github.com wrote:
More info:
ft_dnsmasq | dnsmasq: query[A] api.binance.com from 10.99.0.2 ft_dnsmasq | dnsmasq: config api.binance.com is 10.99.7.251 ft_hitch | 20210221T194950.366894 [ 9] 10.99.0.2:34214 :0 7:8 proxy connect ft_hitch | 20210221T194950.366915 [ 9] 10.99.0.2:34214 :0 7:8 ssl handshake start ft_hitch | 20210221T194950.366942 [ 9] 10.99.0.2:34214 :0 7:8 ssl client handshake revents=1 ft_hitch | 20210221T194950.367352 [ 9] 10.99.0.2:34214 :0 7:8 ssl client handshake err=SSL_ERROR_WANT_READ ft_hitch | 20210221T194950.367469 [ 9] 10.99.0.2:34214 :0 7:8 ssl client handshake revents=1 ft_hitch | 20210221T194950.367497 [ 9] 10.99.0.2:34214 :0 7:8 ssl client handshake err=SSL_ERROR_SSL ft_hitch | 20210221T194950.367514 [ 9] 10.99.0.2:34214 :0 7:8 Handshake failure: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate ft_hitch | 20210221T194950.367531 [ 9] 10.99.0.2:34214 :0 7:8 proxy shutdown req=SHUTDOWN_SSL ft_hitch | 20210221T194950.367544 [ 9] 10.99.0.2:34214 :0 7:8 proxy shutdown req=SHUTDOWN_HARD
@berlinguyinca https://github.com/berlinguyinca Hey ;). I think original author might be MIA.. Was just wondering if you might have any idea? I've been messing with this and have no idea. Have tried updating Hitch thinking maybe SSL would be fixed, but that hasn't worked.
It looks like the author was in contact with you. Were you able to get it running? Did you run into this error? I have tried with other sites like "kraken", and "bittrex", both have same hangup with hitch.
If you can provide any insight or direction that would be awesome! Really looking to get something setup to help w/API cache.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/creslinux/freqcache/issues/8#issuecomment-782915684, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAD73BW6SAIUVRE76II6OLTAGERNANCNFSM4X6I73DA .
Yea, kind of got that. Isn't the idea behind it still relevant though? I started looking into this more after going live, and having errors of 'DDOS' IP backoff protection errors from Freqtrade, running only one bot.
Right now I'm looking into just using varnish. I guess I'm still wondering what your thoughts are about the project though. Is idea behind caching requests to API still revelant?
I'm personally using an nginx proxy and wrote my own bot due to the issues with freqtrade and lack of scalability
On Sun, Feb 21, 2021, 3:55 PM brizz notifications@github.com wrote:
Yea, kind of got that. Isn't the idea behind it still relevant though? I started looking into this more after going live, and having errors of 'DDOS' IP backoff protection errors from Freqtrade, running only one bot.
Right now I'm looking into just using varnish. I guess I'm still wondering what your thoughts are about the project though. Is idea behind caching requests to API still revelant?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/creslinux/freqcache/issues/8#issuecomment-782954270, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAD73FNQR2ISXLAUEQ77NDTAGMP5ANCNFSM4X6I73DA .
Yea...I've even thought about doing something similar, looking into using Zipline and https://github.com/bmoscon/cryptofeed.
really appreciate your feedback and insight.
Well it took about 3 years to write a working bot. So you will be in for the long run. And that's really before strategies. Still working on better strategies.
On Sun, Feb 21, 2021, 4:10 PM brizz notifications@github.com wrote:
Yea...I've even thought about doing something similar, looking into using Zipline and https://github.com/bmoscon/cryptofeed.
really appreciate your feedback and insight.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/creslinux/freqcache/issues/8#issuecomment-782957063, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAD73AKH52XQ45EBGQZX73TAGOGRANCNFSM4X6I73DA .
Yea..I was thinking to myself when working with Freqtrade--so glad all I have to worry about is the strategies.
If you are up for sharing anything, I... I don't know. Figure I might as well ask. I can work on it full time. If you have any interest in working something out :.
Sadly not at liberty to share it at this stage.
On Sun, Feb 21, 2021, 4:45 PM brizz notifications@github.com wrote:
Yea..I was thinking to myself when working with Freqtrade--so glad all I have to worry about is the strategies.
If you are up for sharing anything, I... I don't know. Figure I might as well ask. I can work on it full time. If you have any interest in working something out :.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/creslinux/freqcache/issues/8#issuecomment-782968645, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAD73DXLCEVVHPCXD6XIF3TAGSJHANCNFSM4X6I73DA .
Getting the error:
I'm guessing this means that it can't connect to the binance api. I went to the URL manually (since project hasn't been updated in a while)--and the URL is still valid.
Would love if you could comment about any insights as to what my issue might be.
Trying to debug myself,if I comment out the dns entry (dns: 10.99.7.249) it DOES connect/work. But I think that the whole point is to go through the dns?