> For the complete documentation index, see [llms.txt](https://docs.navigator.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigator.exchange/community/helpful-guides/online-issues.md).

# Online Issues

Here are some common errors you might encounter when using **Navigator**. If you encounter one of the errors listed below, please follow the instructions provided to resolve these issues.

If your error isn’t listed or you're unable to resolve it, please visit the [**Navigator Discord**](https://discord.gg/uugCsntkCm) to open a ticket and report the issue. Our community contributors and support team will assist you as quickly as possible.

## Internal JSON-RPC Error

If your transactions fail to process and you encounter the "Internal JSON-RPC error," it means the RPC used in your wallet is causing the issue.\
To resolve this, follow these steps for Navigator on Sonic:\
Go to your Wallet Settings.\
Navigate to Networks > Sonic.\
Change the New RPC URL.

<figure><img src="/files/5QKtA3vFGuOQcRkicsGA" alt=""><figcaption></figcaption></figure>

You can use [Chainlist ](https://chainlist.org/chain/146)to find a list of available Sonic RPC URLs. Try different listed RPC URLs until your transaction can be successfully processed.\
\
You can try changing the **RPC** on **Navigator**, refreshing the cache, or clearing your browser’s cache if the issue persists. This can help resolve connectivity or loading issues with the platform.<br>

<figure><img src="/files/cjbW7vSELfnd090Pr4QD" alt=""><figcaption></figcaption></figure>

## I**nsufficient {symbol} balance, unable to pay gas**

This error indicates that you don’t have enough gas in your wallet to complete the transaction. Please transfer more gas tokens $S to your wallet and try again.<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.navigator.exchange/community/helpful-guides/online-issues.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.