-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure in evernode reputationd opt-in #427
Comments
Hi, right now the rewards are paused due to a bug in Xahau. While rewards are paused, we recommend to stay opted out of the reputation system until further notice. However in the meantime, could you check if the secret file has the following format?
|
please run these two commands and send the outputs as well |
Please add me in discord no access: [email protected] |
You are still using wss://xahau.network You cant use this Xahau websocket, you need to provide your own or hire a slot off someone |
@liamnibble2020 could you run |
When can Opt-in again? |
Could you run
|
YES, I know the format is crucial, not the first rodeo |
Hi, could you opt in again and check if you are still experiencing this issue? |
evernode reputationd opt-in 9-23-2024 Additionally, I opt-in 7 host last week, some of them getting a bit, not even not even 1 EVER, what is wrong? Are we still Healthy project? Please invite my email [email protected] in DISCORD please |
@liamnibble2020 use this link to join the discord server. Please refer to this documentation to diagnose reward/reputationD related issues in your hosts. If you need any assistance to diagnose the issue, please run the following commands and send the logs you get: Reputation log : MB-XRPL log : Evernode status: Evernode repuationd status: |
"Evernode reputationd status: inactive" means you haven't opted-in for reputation. run |
@du1ana
host address: rw7sNZ6P39qeT4tmHP9CxUrPc2NtBf1goU
when I run "evernode reputationd opt-in" not successful
message:
Waiting for the process to complete...
Sufficient XAH funds have been received.
Secret config file does not exist at /home/ever/secret.key
Run " cat /home/ever/secret.key" - I had my secret for rw7sNZ6P39qeT4tmHP9CxUrPc2NtBf1goU
what is the problem, what is your recommendation?
The text was updated successfully, but these errors were encountered: