Rest API output "code: "internal_issue""

Klever Blockchain Developers
1

The indexer produces an error message while retrieving data.
Maybe someone can point out how to check such issues and how to fix this, besides, why this error happens.

https://api.mainnet.klever.org/v1.0/address/klv1pycejkx23lr7r5fymvdn8dwylyxee5fm2svrfkcgl4fvdnsm4ryqztud2z/allowance?asset=kfi

{

data: {

result: {

interestType: "",

allowance: 0,

stakingRewards: 0,

allStakingRewards: [ ],

buckets: null,

lastClaim: {

timestamp: 0,

epoch: 0

}

}

},

error: "",

code: "successful"

}

Same request on my Index with following output:

{

data: null,

error: "could not get rewards for requested account asset: staking was not found",

code: "internal_issue"

}
2

Hello @Maik we’re investigating this situation and we’ll circle back soon.

TY

1 Like
3

Hi Maik,
Is the node you’re using as an observer in the proxy configuration fully synced?

This error occurs because the proxy request depends on the nodes you’ve defined as observers in the config.yaml. When the proxy cannot retrieve the required data from those nodes, it returns this type of error.

Here’s an example of the configuration:

observers:
  - address: "https://node.testnet.klever.org"

fullHistoryNodes:
  - address: "https://node.testnet.klever.org"
4

Hi Beroni,

yes, this observer is fully synced and set up according your documentation:

This documentation does not state anything about adjusting your 2 mentioned parameters, which are not existent at the config file which we have to download to get the node running.

Does it mean these 2 parameters need to be manually added if one wants to run their own Indexer and has to point to the local node or must it always point to the https://node.mainnet.klever.org URL in case of mainnet?

observers:
- address: " http://localhost:8080"
fullHistoryNodes:
- address: " http://localhost:8080"

5

Initially, I thought the issue was coming from the proxy, since the example URL you sent was from api.mainnet.klever.org. That’s why I shared those proxy-specific configuration settings.

But now that you mentioned you only followed the tutorial to run the node indexer, the proxy is not involved at all. Looking at it again, the problem is just in the URL query parameters. The allowance endpoints on the node are case-sensitive, so the asset must be KFI instead of kfi.

For example:

  • This will return the error:
    https://node.mainnet.klever.org/address/klv1pycejkx23lr7r5fymvdn8dwylyxee5fm2svrfkcgl4fvdnsm4ryqztud2z/allowance?asset=kfi

  • But this works correctly:
    https://node.mainnet.klever.org/address/klv1pycejkx23lr7r5fymvdn8dwylyxee5fm2svrfkcgl4fvdnsm4ryqztud2z/allowance?asset=KFI

3 Likes