# Troubleshooting

### AppError.General: Invalid Configuration

<figure><img src="https://3513762394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHnfaXqsjt2Q8hoDykMmk%2Fuploads%2Fnzm7fYIdZhXOKiK3jWQW%2Fimage_2023-04-17_181050276.png?alt=media&#x26;token=cb81909e-a7ca-4b19-8dd9-12b6d31d4240" alt=""><figcaption></figcaption></figure>

If you facing error like screenshot above, your goracle binary is not match to the latest version. Make sure you update to the latest version to solve this issue by the following command below.

{% hint style="danger" %}
Make sure you copy this command one by one.
{% endhint %}

{% code overflow="wrap" %}

```bash
goracle docker-stop

rm /usr/bin/goracle

sudo wget -qO /usr/bin/goracle https://staging.dev.goracle.io/downloads/latest-staging/goracle && sudo chmod u+x /usr/bin/goracle

goracle docker-start --background
```

{% endcode %}

Now check your logs using this command.

```
docker logs -f goracle-nr
```

### TransactionPool.Remember: txn dead round: xxx

<figure><img src="https://3513762394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHnfaXqsjt2Q8hoDykMmk%2Fuploads%2FjLEo8PZlxkgrJ56QH9Bk%2Fimage_2023-04-16_035154286.png?alt=media&#x26;token=e042ae74-26c8-42a9-b6fe-37163642135e" alt=""><figcaption></figcaption></figure>

This error is related to your algorand node did not catch up to the latest block. Make sure you check the algorand node status by the following command below.

```bash
goal node status -d /var/lib/algorand
```

<figure><img src="https://3513762394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHnfaXqsjt2Q8hoDykMmk%2Fuploads%2FA5Ktsv3AmhY7o3kLkszd%2Fimage_2023-04-16_035344015.png?alt=media&#x26;token=4706399b-ab55-4f53-9290-192bbe5a75aa" alt=""><figcaption></figcaption></figure>

Make sure your Sync Time is **`0.0s`** and check Last commited block is same as the [algoexplorer testnet](https://testnet.algoexplorer.io). If your algorand node catch up slowly, you can restart by the following command below.

```bash
sudo systemctl restart algorand
```

After use this command, you can go back to check the algorand status.

### Request Not Coming

Don't worry about this error, because this error is normal. The oracle request sometime not coming because this is related to their server temporary stopped.

### AppError.General: Error getting Goracle info for

This error also related to **RangeError: Maximum call stack size exceeded** and also some mistake on your `.goracle` file, your `.goracle` file configuration should be like this.

{% code title=".goracle" %}

```javascript
{
  "blockchain": {
    "server": "http://127.0.0.1:8080", // your server from algod.net. port may be different
    "token": "yourtoken", // your token from algod.token
    "mnemonic": "xxx", // this mnemonic is from generated using goracle init
    "mainAddr": "xxx" // this is your main address from pera wallet
  }
}
```

{% endcode %}

\
Delete all related to `authKey` and `authHeader` and save your `.goracle` file. Then do this command to restart your node.

```bash
goracle docker-stop
docker rm goracle-nr
goracle docker-start --background
docker logs -f goracle-nr
```

### Error to get vote

<figure><img src="https://3513762394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHnfaXqsjt2Q8hoDykMmk%2Fuploads%2FSL2RLJ3tXFtxGiarbtqO%2Fimage.png?alt=media&#x26;token=6c4ae378-d0e6-4cd7-82f9-a77daa1d1466" alt=""><figcaption><p>Screenshot from users discord</p></figcaption></figure>

If you facing error like this, you need to top up the participation address. You can go to this link below.

{% embed url="<https://testnet-app.goracle.io/nodes>" %}

{% hint style="warning" %}
Participation address is different from your Pera Wallet. Participation address generated from **goracle init**.&#x20;
{% endhint %}

Next step, you need to copy the participation address and top up your participation address from top up button from link above.

### RangeError: Maximum call stack size exceeded

{% hint style="info" %}
**Update**: In the new version of goracle binary, they already fixed for this error. So you if you get this error, you can update to latest version in [upgrade](https://docs.strnan.top/testnet/goracle/upgrade "mention").
{% endhint %}

* **Solution 1**

Your node is running in the docker and you need to stop it using this command below.

```
goracle docker-stop
docker rm goracle-nr
```

This command will stop and remove your container. Then try again to start your goracle node.

```
goracle docker-start --background
```

Check your logs

```
docker logs -f goracle-nr
```

* **Solution 2**

If didn't work, you can check the `.goracle` file if there is something mistake in your configuration. Then try again. This is the example :&#x20;

{% code lineNumbers="true" %}

```javascript
{
  "blockchain": {
    "server": "http://127.0.0.1:8080",
    "token": "xxx",
    "mnemonic": "xxx",
    "mainAddr": "xxx", // see this comma (incorrect)
  }
}
```

{% endcode %}

As you can see in the line 6, You see the **comma** on the last line, you need to remove it in order to run the node again. So this is example if your `.goracle` file didn't have any mistake.

{% code lineNumbers="true" %}

```javascript
{
  "blockchain": {
    "server": "http://127.0.0.1:8080",
    "token": "xxx",
    "mnemonic": "xxx",
    "mainAddr": "xxx" // this is without comma (correct)
  }
}
```

{% endcode %}

* **Solution 3**

Also another solution is make sure your server configuration is correct.

This is correct

```javascript
"server": "http://127.0.0.1:8080",
```

This is not correct

```javascript
"server": "127.0.0.1:8080",
```

* **Solution 4**

Remove all exited container using this following command.

```bash
docker rm $(docker ps --filter status=exited -q)
```

After doing that, back to **Solution 1**.

### Your participation address not configured

You can solve this issue by adding sudo in goracle init section. here is the example.

{% code overflow="wrap" %}

```bash
sudo goracle init
```

{% endcode %}

{% hint style="info" %}
add **sudo** every command if that command are needed to access using root.
{% endhint %}

### ERROR URLTokenBaseHTTPError: Network request error. Received status 404 (Not Found)

If you're using Purestake, don't worry about this error. As long as your goracle node still submitted vote, your node is fine. Because this error is from Purestake API, maybe their server are overloaded.

### Node Stopped

This problem is from your API (Purestake or Algonode), maybe have some problem with their server or not sure what's the problem. The only way is running own algorand node or wait for goracle team to fix this issue. Because this issue is from their server. But you can use this command to make your goracle node when stopped will automatically restarted.

```docker
docker update --restart on-failure:5 goracle-nr
```

With this command, the container will attempt to maximum of 5 retries to restart when it failure, but it will not attempt to restart if you stop it manually.

Check to make sure this command already applied to your goracle node.

```
docker inspect --format='{{.HostConfig.RestartPolicy}}' goracle-nr
```

Ping me on discord (*Lightbulb#0667*) if this step is working or not, since i haven't tested it yet.

Thanks to **Moon1215i#4745** for sharing this guide how to restart node.