-
Notifications
You must be signed in to change notification settings - Fork 27
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
Unable to connect to exchange API #97
Comments
So I applied the latest update. According to the notes,
I applied the update by going to the page /server/maintenance/ I also rebuilt BTCTransmuter by rerunning the deployment instructions found Not sure if that did anything. In either case, now the exchange box is empty. Can't select any exchange. ApplicationException: Failed to get type from exchange name Did I fail to apply the update properly? Do I need to rebuilt Transmuter from scratch? Is this an active bug? |
Ran the update again today - my 2nd post's error is gone so I can select an exchange again.
I have confirmed that my API key works, I can query my balance using a basic python script. |
I added some XMR to my account, and now it works! The Balance request api call returns an empty value if there's no wallet with some funds in your account. Because the External Exchange Service seems to be testing the api by making a balance call, at least for Kraken it seems to fail when parsing out the reply. It might assume that the return value will always contain a value, and just throws an exception when it fails to retrieve any data, as opposed to just looking at the status of the reply. |
I am trying to set up an Exchange External Service using my Kraken account, but I get the following error:
"Could not connect with current settings. Transmuter tests against fetching your balance amount from the exchange so you would need to enable that option if available"
My Kraken account is verified, and the API key I generated has all permissions set to true.
Is there a log with more information about this error?
The text was updated successfully, but these errors were encountered: