Exchanges not showing up #105
Comments
|
Proxy settings maybe, when starting the client in dev mode (npm run serve) webpack starts a proxy server that should allow you to fetch the latest products from exchanges. Open the console tab of chrome and you should see if it can reach exchanges api. If not, maybe the proxyurl is wrong (default is 8080 but you can have another app on your pc that use it) so the significanttrades app run on 8081, you need to change proxyurl to use 8081 as well. |
|
Hi From the browser debug console, I noticed this error; net::ERR_CONNECTION_REFUSED. As you suggested, I have already changed the proxy URL port on .env file, but no way. |
|
I have the same issue. Ive tried setting this up on Digitalocean, both on Apache and Nginx, the same issue persists where only ByBit shows up. Did you ever find a fix? |
|
These are the errors I get in console: [bitmex] products data expired |
|
When the app starts it fetch the latest products from all exchanges, and need to access exchange REST api to do so. Setting PROXY_URL env var with your proxy server will fix that cors.aggr.trade should work, but please setup your own, especially for production... -> https://github.com/Freeboard/thingproxy |
|
That worked! Thank you Tucsky :) Going to set up my thingproxy! |
Cors.aggr.trade worked perfectly. I set up my own thingproxy, and tried the following formats in the .env file PROXY_URL=http://localhost:3000/ and also PROXY_URL=http://localhost:3000/fetch/ Neither of which seem to work (they work in browser, though, for example this worked in browser: http://myserverip:3000/fetch/https://google.com But, being set up in the .env file it doesnt seem to work for me If I may ask, are you using thingproxy as well, did you do some modifications to the configuration file? I wonder if its my configuration blocking something right now in thingproxy. |
|
Hmm I don't see why really, is the app using the proxy url at all or ? (maybe you have another .env that override it ?)
|
|
I figured it out! The issue was on my end: I was using cloudflare, and something got messed up in the process. Once I disabled cloudflare and the use of https, everything started working! :) |
|
@Tucsky I was able to deploy my own version of this on vercel. When I run locally all exchanges worked, and appear to have ws connections. I'm using my own proxy setup at heroku. For some reason bitmex doesn't work but all the other exchanges work on my deployed version. Any thoughts why that might be? Also just wanted to give you a heads up on this point, I tried deploying to heroku and for some reason their env variables didn't seem to be working. Was banging my head against the wall and just could not get it working. I ended up just hard coding the proxy url in that vue config file but in case anyone else uses heroku maybe they will see this. |
|
Also this is soooo useful. Thanks for your work. |
|
@blake41 Hard to tell, try look into https://gist.github.com/Tucsky/91060583d326926bbbfef580bb1bdd9e and compare with your proxu, see if there is anything you forgot to pass / remove into the final request |
|
Wow I’m an idiot, totally forgot to look at the proxy logs...will keep debugging there. This proxy server will be helpful to see if there’s something I’m missing. Thanks! |
|
Yup removing those headers in my proxy did it. |
I have exchanges not showing up only one from remote clients. If I try locally it's fine, I opened up the dev tools in firefox and network's showing bunch of connection to api's when I connect locally. From remote client there's only 1 connections.. Everything else works.
Debian 10.2 (Docker)
The text was updated successfully, but these errors were encountered: