Bobber 500 Onboarding Stuck at Step 3: Waiting to Come Online/Waiting for Device Authentication

Article author
Customer Support
  • Updated

This article is to address the Bobber 500 onboarding process being stuck at Step: 3 with the message "Waiting for your Miner to come online" or "Waiting for device authentication". This can be caused by pending OTA updates, the Bobber 500 gateway not having a functional internet connection, or onboarding transaction issues.

NOTE: Ensure the mobile device you're using to onboard the Bobber 500 is on the same network. This means you will need to connect to WiFi provided by the router the Bobber 500 is connected to rather than cellular. You will also need to disable any VPNs active on the mobile device.

Check for Updates and Reboot

Access the local dashboard and try updating the gateway firmware by clicking the "Update Gateway" button. If you're already up-to-date, you should see a message pop up on the top right of the dashboard informing you the gateway is already on the latest version. If you do not see this message, there may be an update processing. Wait 10 minutes, then reboot the gateway by clicking "Reboot" on the local dashboard. Wait 5 minutes for the gateway to fully start and try the onboarding process once more.

If your firmware was up to date, proceed with rebooting the gateway by clicking "Reboot" on the local dashboard. Wait 5 minutes for the gateway to fully start and try the onboarding process once more.

Check for Networking Issues

If you are not able to access the local dashboard, there may be a networking issue. If you are able to access the dashboard, there could still be a networking issue preventing the Bobber 500 gateway from reaching the Magma server.

Ensure the Bobber 500's WAN Ethernet connection was set up correctly by reviewing the gateway setup instructions. The Ethernet connection to the router should go from the Bobber 500's WAN port to a valid router port. There should be activity lights on both the Bobber 500 WAN port and the router port. If there are no lights, try swapping to a different Ethernet cable and try a different router port.

If you have not done so already, reboot the gateway by clicking "Reboot" on the local dashboard. Reboot the router as well, then wait 10 minutes for the gateway and router to fully start and try the onboarding process once more.

Submit a Ticket

If still not able to progress, submit a ticket here for Bobcat Support to investigate. Please include the following information:

Was this article helpful?