#RC#
Most minor errors can be resolved by simply clearing the site data or switching the provider. A frequent issue for rango-client users involves a conflict between different wallet extensions. To resolve the , many recommend manually bumping the gas fee in the settings.
A common mistake is trying to send a transaction while a previous one is stuck. Debugging rango-client issues is easier if you check the console for „failed to fetch“ messages. Learning how to read a block explorer can help you identify exactly where a tx reverted.
An outdated web3 provider is often the hidden reason behind many interaction failures. A conflict between the dApp and the browser’s storage can cause the interface to freeze. Layer 2 network delays can sometimes lead to „ghost“ transactions that appear later.
