Common problems

Checklist

• Did you use active private key, not wallet password, when creating Worker
• Did you use a separate account for each Worker
• Did you write the whole asset name with prefix (BRIDGE.LTC, OPEN.ETH, BTS, USD, STEALTH, etc)
• Did you make sure the account holds both the assets to be traded
• Does the account have some BTS for fee's
• Did you toggle the TURN WORKER ON/OFF button to make the Worker actually work
• Is your computer clock synchronized

Clock problem

If you get the following message at the end of an error message:

bitsharesapi.exceptions.UnhandledRPCError: Assert Exception: now <= trx.expiration Sync your computer's clock. It should fix the error.

Signature / key problems

base58CheckDecode

• Try upgrading the Python cryptography package with: pip3 install --upgrade cryptography and running again
• If you see errors about several private keys for the same account, you need to empty the wallet from keys. First delete all workers. Then run uptick wipewallet. Now there should be no wallet and no keys. Start from zero.

Missing config.yml

If the last line of the error message in the terminal is this:

TypeError: 'NoneType' object is not subscriptable

The ~/.config/dexbot/config.yml might be empty or missing. If it's missing create it and paste the following into it:

node: wss://bitshares.openledger.info/ws
workers: {}

Node connection problems

Change the node defined in config.yml. See file location below. See what node gives you the lowest latency in the DEX, and copy it into the config file.

DEXBot GUI freezes and no orders are created

Restart bot

Unknown order type

In BTS:MPA (Market Pegged Assets such as BitUSD and BitCNY) markets, if a force settlement fills your order, the bot doesn't yet recognize it and consequently disables itself because it isn't sure what happened. This will be fixed eventually but for time being just pause->play or restart the whole DEXBot-gui.

File locations

Sometimes you can solve problems by starting fresh, that is, by removing the files that hold the keys and configuration.

Windows

DEXBot

• DEXBot config: C:\Users\<user>\AppData\Local\Codaone Oy\dexbot\config.yml
• DEXBot log: C:\Users\<user>\AppData\Local\Codaone Oy\dexbot\dexbot.log
• DEXBot storage: C:\Users\<user>\AppData\Local\Codaone Oy\dexbot\dexbot.sqlite
• Orders history: C:\Users\<user>\AppData\Local\Codaone Oy\dexbot\history.csv

Uptick

• Wallet: C:\Users\<user>\AppData\Local\Fabian Schuh\bitshares\bitshares.sqlite

Linux

DEXBot

• DEXBot config: .config/dexbot/config.yml
• DEXBot log: .local/share/dexbot/dexbot.log
• DEXBot storage: .local/share/dexbot/dexbot.sqlite
• Orders history: .local/share/dexbot/history.csv

Uptick

• Wallet: .local/share/bitshares/bitshares.sqlite

OSX

DEXBot

DEXBot log: dexbot.log in the same repository as Makefile

• DEXBot config: ~/Library/Application Support/dexbot/config.yml
• DEXBot log: dexbot.log in the working directory (if you start dexbot from cli)
• DEXBot storage: ~/Library/Application Support/dexbot/dexbot.sqlite
• Orders history: ~/Library/Application Support/dexbot/orders.csv

Uptick

• Wallet: ~/Library/Application Support/bitshares/bitshares.sqlite