-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error retrieving a new deposit address in testnet.blinktrade.com #24
Comments
Yes, this issue remains for a while (#19 #21) i will talk to @pinhopro about it, but for now, i suggest you to create a account on foxbit testnet instead (https://testnet.foxbit.exchange) and create a fiat deposit, and then, logged as foxbit testnet admin (username: foxbit, password: abc12345, and don't forget to click on footer admin link) and approve your own deposit on the admin tab. |
The foxbit testnet https://testnet.foxbit.exchange is not working. |
It's working fine here. |
@cesardeazevedo The problem here is the DNS. The foxbit testnet tries to connect wss://api.testnet.blinktrade.com/trade/ but when I ping the the IP is not resolved. $ ping api.testnet.blinktrade.com
ping: unknown host api.testnet.blinktrade.com
|
Can you login as rodrigo/abc12345 directly on testnet.blinktrade.com ? This is also a testnet account that we use. The testnet.foxbit hasn't been updated for a long time, and the correct endpoint for testnet is |
Thanks @cesardeazevedo. |
@cesardeazevedo I replaced the endpoint in all files and the api works, but you should consider update the code. The issue #25 also occurs in testnet. Thanks. |
Yes indeed, i need to update this as well, thanks for reporting. |
same issue, is there a way to fix that? |
Hi,
I'm trying to use the platform in https://testnet.blinktrade.com
I'm signed up new account.
When I'm trying to generate new deposit address I'm receiving the error bellow:
Message from server: Error retrieving a new deposit address. Please, try again - <urlopen error [Errno 111] Connection refused>
The text was updated successfully, but these errors were encountered: