Common problems

Here you will find common problems when using the Elven Tools. In the future, there will be more improvements, good error messages, etc.

CLI deploy transaction error

Request error on url [transactions]: [{"statusCode":400,"message":""}]

Problem: The problem occurs when deploying the smart contract with Elven Tools CLI with elven-tools deploy nft-minter
Cause: You either don't have funds on the wallet that you are using with Elven Tools, or you have mismatched the configuration with the actual PEM file
Solution: Ensure that the PEM file corresponds to your chain type configuration (the devnet by default, even without the configuration file). The PEM file should be derived from the seed phrase corresponding to the chain you want to deploy the smart contract. Also, make sure that you have funded the wallet.

'Token not issued' - the error from smart contract results

Problem: The problem occurs when setting the roles for the collection token with elven-tools nft-minter set-roles
Cause: There is a time required between issuing the token and assigning the roles. The transaction can fail if the setting roles command is fired too quickly.
Solution: Wait a couple of seconds and call the command again.

'Account not found' - problem with the account

Request error on url [accounts/erd1...]: [Account not found]

Problem: The problem can occur with any CLI command, any transaction
Cause: The problem occurs when something is wrong with the network, or the devnet/testnet was reset, and your wallet doesn't exist anymore (doesn't have funds).
Solution: Double check your wallet, check if it works properly, and check if there are no problems with devnet/testnet if you use them. If so, then wait till the network works again.

Ttimeout of 10000ms exceeded

Request error on url [accounts/erd1...]: [Error: timeout of 10000ms exceeded]

Problem: The public API which is in use by default isn't responding on time
Cause: The problem occurs when the network isn't responding fast. There is a limit of 10 seconds. Then the connection is closed.
Solution: You could try again, and if a couple of tries don't help, you would need to change the API provider. Check how here. Or you can wait some time for the public API to be in better shape.

Contents