This article describes common errors in ATAS and crypto exchange connections, as well as ways to solve them.
Authorization window stays in the Checking updates state forever
Description: The authorization window stays in the Checking updates state forever.
Reason: Something is blocking the connection to the update servers, such as antivirus software, firewall, internet provider restrictions, or network limitations. This often happens in offices of large companies.
Solution: The Autoupdater.cnf file may have been damaged after an update due to OneDrive, cleaning software such as CCleaner, antivirus software, or the operating system itself.
Steps to fix:
- Close the ATAS platform.
- Go to C:\Users\Username\AppData\Roaming\ATAS and delete the Autoupdater.cnf file.
- Start ATAS again.
After pressing Connect, the error Remote host terminated the connection appears
Description: After pressing Connect, the error Remote host terminated the connection appears.
Reason: Something is blocking the connection to the servers, such as antivirus software, firewall, internet provider restrictions, or network limitations. This often happens in offices of large companies.
Solution: Disable protective software, change the internet connection, or ask the office system administrator to unblock the necessary ports.
Orders have been sent but the answer wasn't received
Description: The message Orders have been sent but the answer wasn't received appears.
Reason: This means that something went wrong while ATAS was trying to receive a response from the connector.
Solution: Disconnect the connector and reconnect it again, or restart ATAS.
Error receiving data. Storage is not empty
Description: The error Error receiving data. Storage is not empty appears when opening a chart.
Reason: There are issues with the data storage.
Solution: Close ATAS and delete the Cachev2 folder. You can find it here: C:\Users\Username\Documents\ATAS\Cachev2.
Crypto exchange errors and solutions
Invalid API Key
Description: The API key provided is incorrect.
Reason: The API key used is invalid or incorrect.
Solution: Verify that the API key entered is correct. Generate a new key if necessary and make sure it is properly configured in the exchange settings.
Forbidden
Description: Access is blocked due to IP restrictions, regional restrictions, or a ban on the exchange.
Reason: Access is restricted due to the exchange security settings, such as IP or regional blocks, or the account may be banned.
Solution: Check the exchange policies regarding IP and regional restrictions. If the account is banned, contact the exchange support team to resolve the issue.
Parameter Error
Description: A required parameter is missing or incorrect.
Reason: One-way position mode needs to be enabled on the exchange.
Solution: Enable one-way position mode in your exchange settings to resolve this issue.
Permission Denied
Description: There are insufficient permissions to access the API or perform certain actions.
Reason: API permissions are not configured properly.
Solution: Verify the API permissions in the settings according to the exchange API documentation and make the necessary adjustments.
IP Mismatch
Description: Access is blocked due to incorrect settings selected on the exchange.
Reason: Access is restricted due to exchange settings, such as IP restrictions.
Solution: Select the No IP Restrictions option in the exchange settings to resolve this issue.
Bad Input
Description: The Bad Input error appears.
Reason: The date and time format on the PC is not set to the Gregorian calendar.
Solution: Change the date and time format on the PC to the Gregorian calendar.
```
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article