Skip to main content
Version: v3.0.0

Troubleshooting

Troubleshooting HOPR node issues​

How to check if the migration from HOPRd v2 to HOPRd v3 was successful?​

  1. Connect to your node via the HOPR Admin UI. If you encounter an error while connecting to your node, first try a hard refresh of the Admin UI (macOS: Cmd + Shift + R, Windows: Ctrl + Shift + R). If that doesn’t resolve the issue, refer to the error codes for further troubleshooting.

  2. Ensure you are using the latest versions of both HOPRd and the HOPR Admin UI.

    • You can check your current HOPRd node version on the INFO page under the Node section. To find the latest HOPRd version, visit this link.

    • For the HOPR Admin UI version, check the bottom right corner of the interface. The most recent HOPR Admin UI version can be found here.

  3. On the INFO page, navigate to the Network section:

    • If the Eligible status displays Yes, your node has successfully joined the HOPRd network.
    • If it displays No, and your node was recently created, it must reach 100% sync before becoming eligible.

  4. On the TICKETS page, ensure that there are no Neglected or Rejected tickets and that you have already received some Unredeemed or Redeemed tickets.

How to check if my node is performing normally?​

  1. Verify successful HOPR Admin UI connection to your node

    Connect to your node via the HOPR Admin UI. If you encounter an error while trying to connect to your node, please refer to the error codes.

  2. Check for latest HOPRd & HOPR Admin UI versions

    Ensure you are using the latest versions of both HOPRd and the HOPR Admin UI.

    • You can check your current HOPRd node version on the INFO page under the Node section. To find the latest HOPRd version, visit this link.

    • For the HOPR Admin UI version, check the bottom right corner of the interface. The most recent HOPR Admin UI version can be found here.

  3. Check node health

    1. On the INFO page, navigate to the Network section:

      • If the Eligible status displays Yes, your node has successfully joined the HOPRd network.
      • If it displays No, and your node was recently created, it must reach 100% sync before becoming eligible.

    2. On the INFO page, under the Network section, verify that the Sync process is at 100%.

    3. On the INFO page, under the Network section, verify that no Faulty RPC message appears next to the Provider Address.

    4. On the INFO page, check the Balances section and confirm that the xDai: Node balance is at least 0.03 xDai.

    5. On the INFO page, scroll to the Nodes on the network section and ensure the Announced node count exceeds 1061 and the Connected node count is above 100.

  4. Check node configuration

    On the Configuration page, under the Strategies section, verify the following:

    • The !Aggregating setting is not enabled.
    • The minimum_redeem_ticket_value is set between 1 wxHOPR and 9 wxHOPR.
    • The redeem_only_aggregated setting is set to false.

  5. Check your node connectivity quality

    On the PEERS page, ensure that most of your peers have 100% quality (assuming your node has been running for at least 1 hour).

  6. Verify tickets status

    On the TICKETS page, ensure that there are no Unredeemed, Neglected or Rejected tickets.

  7. Verify your node's status on the Network Dashboard

    Visit HOPR Network Dashboard and search for your node by entering your Node address. If your node appears, it indicates that it is reachable by network nodes.

    note

    If one of above mentioned steps doesn't meet requirements, please refer to the topics on this troubleshooting page. If you are still unable to find a solution, feel free to reach out to the Ambassadors via Telegram or Discord channels for further assistance.

How can I verify if Cover Traffic is being relayed through my node(s) and if I'm receiving rewards?​

  1. Ensure your node is performing normally

    Ensure your node is functioning correctly by following the steps outlined in the troubleshooting guide.

  2. Check incoming channels

    Once connected to your node via the Admin UI, navigate to the CHANNELS: IN page, ensure you have at least 5 incoming payment channels from the following Cover Traffic nodes:

    0xd30f8f6e5865d7ec947e101b1d6a183e9776ba40
    0x5a5bf3d3ce59cd304f198b86c1a78adfadf31f83
    0xa4642c066c1f8927db9d34abab599af784a2cff0
    0xcbe8726c80cc0d7751b9545dd5a4b5b0e53e383d
    0x764d3162a4024c5cba8817446ef563b27aa57598

  3. Expected rewards calculation

    Due to recent changes in ticket pricing and win probability, ticket aggregation has been discontinued. The current ticket price on the network is 0.00005 wxHOPR. Due to this low value, redeeming tickets frequently could quickly drain your xDai. To address this, the Cover Traffic Node now issues winning tickets valued at 10 wxHOPR each.

    With an APR of 10%, a node staked at the maximum cap of 75,000 wxHOPR should earn approximately 20 wxHOPR per day. For nodes with a lower stake, you can estimate your expected rewards using the following formula:

    Yearly Reward = (Your staking amount per node) × 10% (wxHOPR/year)
    Daily Reward = (Yearly Reward) ÷ 365 (wxHOPR/day)

    Note: If you run multiple nodes, divide your total staking amount by the number of nodes to determine the staking amount per node.

    Examples:

    75,000 wxHOPR per node: Yearly Reward = 75,000 × 10% = 7,500 wxHOPR/year Daily Reward = 7,500 ÷ 365 ≈ 20.55 wxHOPR/day (approximately 2 tickets/day)

    30,000 wxHOPR per node: Yearly Reward = 30,000 × 10% = 3,000 wxHOPR/year Daily Reward = 3,000 ÷ 365 ≈ 8.22 wxHOPR/day (approximately 1 ticket every 2 days)

    10,000 wxHOPR per node: Yearly Reward = 10,000 × 10% = 1,000 wxHOPR/year Daily Reward = 1,000 ÷ 365 ≈ 2.74 wxHOPR/day (approximately 1 ticket every 4 days)

    Note: These calculations assume optimal node performance and no issues with the RPC provider or other dependencies.

  4. Verify Connectivity to Cover Traffic Nodes

    To ensure stable connectivity and eligibility for rewards, try pinging each Cover Traffic node individually. If you can successfully ping all of them, it indicates that you have a stable connection to the Cover Traffic nodes. Below are the current addresses of the Cover Traffic nodes:

    Cover Traffic node 1​

    Node address: 0xd30f8f6e5865d7ec947e101b1d6a183e9776ba40

    Cover Traffic node 2​

    Node address: 0x5a5bf3d3ce59cd304f198b86c1a78adfadf31f83

    Cover Traffic node 3​

    Node address: 0xa4642c066c1f8927db9d34abab599af784a2cff0

    Cover Traffic node 4​

    Node address: 0xcbe8726c80cc0d7751b9545dd5a4b5b0e53e383d

    Cover Traffic node 5​

    Node address: 0x764d3162a4024c5cba8817446ef563b27aa57598

What should I do if my node is receiving unredeemed, neglected, rejected tickets?​

If your node is receiving rejected tickets, several issues could be causing this, such as:

  • Your node is not properly synced, which may indicate limitations with your RPC provider.
  • There may be off-chain issues where the node deems tickets invalid and marks them as rejected.

Follow these steps to troubleshoot the issue:

  1. Connect to your node via the HOPR Admin UI.

  2. Navigate to the Info page, under the Network section, and verify that no Faulty RPC message appears next to the Provider Address. If a Faulty RPC message is displayed, you must change your RPC provider and resync your node. Follow the guide to resync your node for detailed instructions.

  3. If no Faulty RPC message appears next to the Provider Address, do the following:

  • Navigate to the Channels: In page. Close all incoming payment channels by clicking the Close Incoming Channel icon next to each channel.
  • If you have outgoing payment channels to Cover Traffic nodes, close the payment channels with Cover Traffic nodes and re-open at least one payment channel with a random peer from the connected peers list.
  1. Wait several days and monitor whether you receive rejected tickets again. If you do, contact the ambassadors on the Telegram channel or Discord server for assistance.

What should I do if my node is receiving neglected tickets?​

There might be several causes on why your node received neglected tickets:

  • Tickets are marked as neglected when you close an incoming payment channel with unredeemed value. Since the tickets were not redeemed during the closure, they will be labeled as neglected tickets. This typically occurs when your node experiences issues, such as rejected tickets. To prevent continuous loss of rewards, it’s important to address the underlying issue.

  • When a payment channel is closed and the node's strategy value for minimum_redeem_ticket_value is set higher than the value of the channel’s individual tickets, those tickets will be marked as neglected. This happens because the ticket value does not meet the minimum threshold specified by the strategy. In this case, you need to customize your node strategies by following this guide.

How to re-sync my HOPRd node?​

Note

During the re-sync process, all tickets in your database will be removed, including any unredeemed tickets. This step is necessary to ensure optimal node performance, but please be aware that unredeemed tickets will be lost.

Please select platform to re-sync node:

  1. Stop your node: follow this guide to stop your HOPR node.

  2. Backup your node: ensure you back up your node before proceeding. Refer to this guide for detailed backup instructions follow this guide.

  3. Delete the necessary files: On your machine, navigate to the .hoprd-db-dufour folder and perform the following steps:

    3.1 Delete the tbf file.

    3.2 Locate the db folder and remove all files inside it.

  4. Start your node: once the cleanup is done, start your node again by following this guide.

  5. (Optional) If you want to use the fast synchronization feature during the re-sync process, follow the fast-sync guide.

How to retrieve logs from your node?​

  1. Connect to your machine and execute the command docker ps. This will provide you with a list of Docker containers you are currently running. Among them, locate the container with the label europe-west3-docker.pkg.dev/hoprassociation/docker-images/hoprd:stable and note the container ID.

  2. Get the logs from the docker container using the following command: docker logs -t <Your_Container_ID> >> <File_name.log>. Replace <Your_Container_ID> with your docker container ID. Replace <File_name.log> with your container ID and <File_name.log> with your chosen file name. After executing the command, wait until it finishes writing the logs to the file.

    Example:

    docker logs -t 4951b2990936 >> logs_from_hopr_node.log

Troubleshooting HOPR Admin UI issues​

HTTP Status code 422​

Error description: Your RPC provider is either unavailable or malfunctioning. Please switch to a functional RPC provider. If you are using a local RPC provider, please troubleshoot the issue.

Error message:

Error fetching: {"name":"APIError","status":422,"statusText":"Unprocessable Entity","description":"HTTP Status code 422"}

UNAUTHORIZED/Authenticaltion Failed​

Error description: If you provided incorrect security token.

Error message:

ERROR
Unable to connect.
Error fetching: {"status":"UNAUTHORIZED","error":"authentication failed"}

Network Request Failed​

Error description: If HOPR Admin can't connect to your node, please check if the provided API endpoint is correct, or if your node is working.

Error message:

ERROR
Unable to connect.
Unknown error: "Network request failed"

Balance Too Low​

Error description: When your node has just been created, it will not be funded. You can't connect to the unfunded node.

Error message:

ERROR
Unable to connect.
Your xDai balance seems to low to operate the node.
Please top up your node.
Address: 0xa6512ad...657730b0313

Troubleshooting the migration from Avado​

What should I do if "DappnodeWifi" and my Avado Wi-Fi network don't appear in my computer's Wi-Fi list?​

Please select connection method to your Avado device:

  1. Find your Avado internal IP address

    1. To find the internal IP address of your Avado device, first connect to your router. Then follow only the 2nd step in this guide to identify your router’s gateway IP address.

    2. Log in to your router by entering the router's gateway IP address into your browser's address bar. Since router interfaces vary, search for sections labeled DHCP Clients," Connected Devices," or Connected Clients. Within this section, look for the client named dappnode to find its associated IP address.

  2. Connect to your Avado device

    1. Connect to your Avado device by entering the following command into your terminal/windows powershell:

      ssh dappnode@<avado_internal_ip_address>

      Please replace <avado_internal_ip_address> with your Avado internal IP address.

      Example:

      ssh [email protected]

    2. If this is your first time connecting via SSH, you'll be prompted to confirm the connection to your node. Type yes and press enter. Next, you'll be asked to enter a password; the default password is dappnode.s0.

      note

      On Linux systems, the password entry will not display characters as you type. Ensure you enter the password correctly before pressing enter.

  3. Finalise migration process

    1. Once you've logged in, install kbd package:

      sudo apt-get install -y kbd

    2. Install the prerequisites using the following command:

      sudo wget -O - https://prerequisites.dappnode.io | sudo bash

    3. Install the dappnode package using the following command:

      sudo wget -O - https://installer.dappnode.io | sudo bash

    4. Once the installation is complete, please restart your Avado device by executing the following command:

      sudo reboot

    5. Please wait 5 minutes, then check if DappnodeWifi appears in your computer's Wi-Fi list. The default Wi-Fi password for Dappnode is dappnode.

What should I do if only my Avado Wi-Fi appears but "DappnodeWifi" is missing from my computer's Wi-Fi list?​

If the Avado Wi-Fi appears on your computer's Wi-Fi list, it suggests a problem with the USB's boot settings, as the device did not attempt to initiate the installation process. Please select connection method to your Avado device:

  1. Prerequisites for connection to your Avado device

    Make sure you have:

    • Physical access to your Avado device
    • Micro Phillips head screwdriver
    • A bootable USB stick with Dappnode software

  2. Avado disassembly guide: accessing the internal battery

    1. Remove the power cable and any other cables from your Avado device.

    2. Detach the bottom panel of your Avado using a micro Phillips screwdriver.

    3. Carefully release the RAM module by gently pushing the two clips outward. The module will pop up slightly. Remove the angled module to expose the circular battery located beneath it.

    4. Remove the battery and wait 10 minutes.

    5. Reinsert the battery and the RAM module into the device, then secure the bottom panel by replacing and tightening the screws.

    6. Re-attach the power supply and ethernet cable.

  3. Finalise migration process

    1. Power on the Avado device for 2 minutes.

    2. Turn off Avado device.

    3. Insert the bootable USB stick containing the Dappnode software and power the device back on.

    4. Leave the device running for 15 minutes, then turn it off.

    5. Remove the USB stick and power on the device again.

    6. Wait for 5 minutes and check if DappnodeWifi has appeared in your computer's wifi list. The default Wi-Fi password for Dappnode is dappnode.

What should I do if my Dappnode isn't reachable via Wi-Fi and I've forgotten the SSH password?​

If you've forgotten the SSH password and cannot access your Dappnode, you will need to physically connect to the device and perform a reinstall of the Dappnode software.

  1. Prerequisites for connection to your Avado device

    Make sure you have:

    • An external monitor & HDMI cable.
    • External keyboard.
    • A bootable USB stick with Dappnode software

  2. Connect to your Avado device

    1. Connect your monitor to your Avado device using an HDMI cable.

    2. Connect an external keyboard to your Avado device.

    3. Connect an Ethernet cable to your Avado device.

    4. Attach the bootable USB stick containing the Dappnode software to any Avado USB port.

  3. Finalise migration process

    1. Power on your monitor and Avado device and start pressing the Esc key until you enter the BIOS. This should be visible on the monitor you have connected.

    2. Use the arrow keys to navigate to the Boot tab.

    3. Under Boot Option Priorities, select Boot Option # and then change it to your attached USB.

    4. Now, using your arrow keys, navigate to the Save & Exit tab and save your settings.

    5. Your device should now restart and begin booting from your attached bootable USB stick with Dappnode software. You can now resume the initial installation method but now starting directly from the 3rd step.

Troubleshooting the RPC provider​

How to check public RPC provider's execution client?​

To ensure your RPC provider uses the Nethermind execution client:

  1. Visit Etherflow and enter your RPC endpoint.

  2. Select web3_clientVersion and send the request.

  3. Verify that the response indicates the use of the Nethermind execution client.

Table of Contents