Not receiving rewards

[Greypimps]

Not receiving rewards. Reputation around 122 on the dashboard. Whats going on? My vps is using shared ipv4 address can that be the issue or do i need a dedicated one?

[Greypimps]

[Greypimps]

[du1ana]

Hi, shared ipv4 should not be an issue if your domain properly resolves to it. Please run the following commands and send the logs you get:

Reputationd log :
sudo -u sashireputationd bash -c 'journalctl --user -u sashimono-reputationd | tail -n 250'

MB-XRPL log :
sudo -u sashimbxrpl bash -c journalctl --user -u sashimono-mb-xrpl | tail -n 250

[Greypimps]

[Greypimps]

[Greypimps]

i actually have dedicated ipv4.

[du1ana]

i don't see any apparent abnormalities in your logs. please refer to this documentation to diagnose reputation contract execution

[Greypimps]

this is no good too complicated.. why not make it a one click for us... was working before this last update, only thing was it does not show my score percentage on dash board but rep was at200

[du1ana]

try decreasing the number of instances to 3 by running evernode config resources 0 0 0 3. lesser number of instances should help if the problem lies in hardware limitations

[Greypimps]

getting a report of without scores alot..reduce the resource to 3 doesnt seem to work

[du1ana]

When a contract is executed "without scores," it means the contract ran but didn’t succeed. This often happens due to poor performance or unmet prerequisites, which are detailed in the documentation I shared earlier.

To improve performance, try increasing the number of CPU cores. This should help the reputation contract run more efficiently on your machine.

Alternatively, before adjusting the CPU, you can try reducing the instance count to 2 by running evernode config resources 0 0 0 2. Check if this improves the "score" on the dashboard. However, note that this will violate the minimum requirement of 3 instances, resulting in 0 reputation during the test. If the score improves with fewer instances, it likely indicates hardware limitations are the issue with your host.