Bobcat 300 Diagnoser Tool / Utility Guide (Helium Mining)

Bobcat 300 Diagnoser Utility
Bobcat 300* Diagnoser Utility

The Bobcat 300* Helium Miner finally has an interface you can use to be able to tell what it’s doing! Better yet, it lets you do a few things like conduct an internet speed test. You can even get a detailed breakdown of which block your miner is on!

In this guide I’ll break down how to access the web interface (easy) and run through some of the features that are available at launch (1.0). The utility started installing on Bobcat 300’s via OTA updates on August 3rd 2021. Let’s begin!

Hardware Used

Bobcat 300 Helium Miner
Bobcat 300 Helium Miner

The Nebra outdoor miner is a Helium miner designed to be installed permanently outdoors. It is powered by a Raspberry Pi Compute Module 3 and uses a eMMC chip for storage via a

Links: Amazon.com*

Finding IP Address

Hopefully you already know what the IP address of the Bobcat 300 is on the network as you will need to know that to get your miner out of relayed status and set up the “port forward”.

If you haven’t set up your port forward yet follow my Getting Out of Relayed Status Helium Mining Guide.

You can find your IP by logging into your router’s web interface / app or you can use the Helium app’s “Diagnostics” feature to get it as well!

Accessing Web Interface

Once you’ve determined your miner’s IP type it in your web browser like this:

http://192.168.X.X

It does not like https (port 443) and will only work with http (port 80).

Diagnoser Utility Options

Let’s cover what you can do using this utility at launch.

Temperature

Temperature is a serious obstacle for Bobcat 300 miners. If they are outside or in a very hot / poorly ventilated place they are well known to overheat. This feature helps you manage this and make sure your miner isn’t getting cooked.

If you choose the temperature option you will get the temperature of your unit (as temp.json in JSON format, useful if you are a developer) like this:

{
  "time": "2021-08-07 00:30:51 +0000 UTC",
  "temp0": 47,
  "temp1": 49,
  "unit": "°C"
}

This lets you keep an eye on your miner’s temperature. This one is inside an air conditioned building and it’s still nearly 49C or roughly 120F degrees but would be considered a “good” temperature reading!

Goldshell ASIC     Goldshell ASIC     Goldshell ASIC     Goldshell ASIC     Goldshell ASIC     Goldshell ASIC    

Sync Status (Update 9/3/2021)

New option added in 1.0.3 that is described as:

Introducing the sync status feature on the Bobcat Diagnoser, which answers the very simple yet important question of whether or not your Bobcat miner is properly synced to the network. Stop incessantly rebooting or waiting for the helium app to update the miner’s status. Now you’ll have access to real time information at the push of a button!

Bobcat Miner 9/2/201 Update

The Helium app really is agonizingly slow to update so this is a useful feature. Here’s an example of how it looks:

{
  "status": "synced",
  "gap": "-2",
  "miner_height": "995790",
  "blockchain_height": "995788",
  "epoch": "25674"
}

The “gap” is how many blocks behind you are, so I am 2 blocks behind with a gap of -2. The math adds up with the “blockchain_height” representing the height the entire network is at and “miner_height” representing the block height your miner is at / sync’d to.

Miner

The “Miner” choice gives you an extremely detailed breakdown of your miner. You want to be careful with this option because the menus warn you that this option slows down the Bobcat’s mining (it’s a resource intensive / high CPU operation).

Here’s what it looks like:

{
  "time": "2021-08-07 00:11:15 +0000 UTC",
  "temp0": "48 °C",
  "temp1": "50 °C",
  "temp_alert": "normal",
  "ota_version": "1.0.2.10",
  "miner": {
    "State": "running",
    "Status": "Up About an hour",
    "Names": [
      "/miner"
    ],
    "Image": "quay.io/team-helium/miner:miner-arm64_2021.08.02.0_GA",
    "Created": 1628292218,
    "Ports": [
      {
        "IP": "0.0.0.0",
        "PrivatePort": 1680,
        "PublicPort": 1680,
        "Type": "udp"
      },
      {
        "IP": "0.0.0.0",
        "PrivatePort": 44158,
        "PublicPort": 44158,
        "Type": "tcp"
      }
    ]
  },
  "miner_alert": "",
  "miner_desc": "",
  "pubkey": "1125RGgX5aXXXXX",
  "animal": "shallow-maroon-xxx",
  "region": [
    "US915",
    ""
  ],
  "height": [
    "24468    955285",
    ""
  ],
  "ports": {
    "1680": "closed",
    "44158": "open"
  },
  "p2p_status": [
    "+---------+------+",
    "|  name   |result|",
    "+---------+------+",
    "|connected| yes  |",
    "|dialable | yes  |",
    "|nat_type | none |",
    "| height  |955285|",
    "+---------+------+",
    "",
    ""
  ],
  "onboarding": [
    "",
    "********************",
    "General Manufacturing Info",
    "********************",
    "",
    "+-------------+----------------------------------------------------+",
    "|    name     |                       result                       |",
    "+-------------+----------------------------------------------------+",
    "|    batch    |                     bobcat_609                     |",
    "|  createdAt  |              2021-06-09T09:41:12.706Z              |",
    "|heliumSerial |                        null                        |",
    "|     id      |                       82510                        |",
    "|   macEth0   |                 e8:78:29:51:XX:XX                  |",
    "|  macWlan0   |                 48:e7:da:13:XX:XX                  |",
    "|   makerId   |                         6                          |",
    "|onboardingKey|112xxxx                                             |",
    "|publicAddress|1125RGg                                             |",
    "|  rpiSerial  |                  7cdf8xxx                          |",
    "|  updatedAt  |              2021-06-18T22:30:18.486Z              |",
    "+-------------+----------------------------------------------------+",
    "",
    "",
    "********************",
    "Manufacturer Info",
    "********************",
    "",
    "+------------------+---------------------------------------------------+",
    "|       name       |                      result                       |",
    "+------------------+---------------------------------------------------+",
    "|     address      |14sKxxx                                            |",
    "|    createdAt     |             2021-02-24T22:16:39.379Z              |",
    "|        id        |                         6                         |",
    "|locationNonceLimit|                         1                         |",
    "|       name       |                      Bobcat                       |",
    "|    updatedAt     |             2021-02-24T22:16:39.379Z              |",
    "+------------------+---------------------------------------------------+",
    "",
    ""
  ],
  "errors": null
}

I told you it was a lot of information!

We can actually see a lot of stuff that was previously not possible to see on your Bobcat like the enrollment key, various internal components and their serial numbers, etc.

Our P2P connection status (what the light represents on your Bobcat, green yellow etc.) is revealed in great detail as well. Look at this detailed breakdown here:

   "p2p_status": [
    "+---------+------+",
    "|  name   |result|",
    "+---------+------+",
    "|connected| yes  |",
    "|dialable | yes  |",
    "|nat_type | none |",
    "| height  |955285|",
    "+---------+------+",

Explorer

This is just a link to the Helium blockchain explorer. Not very useful!

Helium API

Connects to the Helium API and returns some information in JSON format about your specific miner. This is Helium-specific information that is tracked across all miners and not Bobcat specific.

Onboarding

This one is a little more interesting. It redirects you to your hotspot’s onboarding entry at onboarding.dewi.org. The results are given to you in JSON like the other commands.

I had not seen this site before but sure enough my onboarding entry appeared as expected!

Net Speed (Internet Speed Test) (Update 9/3/2021: Removed, Secret Link Available)

Finally a fun one! This one lets you test your Bobcat 300’s internet connection speed.

I ran the connection test (using WiFi) and this was my output:

{
  "DownloadSpeed": "27 Mbit/s",
  "UploadSpeed": "33 Mbit/s",
  "Latency": "16.586062ms"
}

Those results are actually terrible for my connection speed (gigabit fiber) but not unexpected for WiFi using G/N speeds.

At any rate this is very useful information to have whether you’re using wired / wireless. Having a tool like this lets you test the Bobcat’s connection specifically instead of running a general speed test on your computer. That only diagnoses your internet connection in general and not the Bobcat’s connection specifically so having this tool is a giant leap forward and worth using.

It does make your miner slow down / stop mining for about 30 seconds so don’t overdo it!

UPDATE 9/3/2021: In 1.0.3 this option is no longer in the list of options. It’s still available on the miner as speed.json. To access the option replace the IP in the URL below with your own miner’s IP address and go to:

http://192.168.X.X/speed.json

After a 20 second pause or so you will see the speed test (for now, they removed the menu option but the JSON request is still available/permitted):

{
  "DownloadSpeed": "25 Mbit/s",
  "UploadSpeed": "42 Mbit/s",
  "Latency": "9.81852ms"
}

Resync Miner (Update 9/2/2021)

This is the first really serious troubleshooting option we’ve been given for the Bobcat. It was added in 1.0.2 and the description given by hovering your mouse over the option is “It will delete the miner data, let the miner resync to the blockchain from scratch”.

Basically they’re saying this will wipe the local blockchain data from your miner and let it resync from scratch. You would only want to do this if your miner is completely stuck / corrupted.

Do you remember how long it took to sync your Bobcat when you got it? You definitely don’t want to have to go through that again unless your miner is completely broken and won’t sync and nothing else has worked / troubleshooting has led you to this conclusion.

This finally gives users the ability to clear and resync their Bobcat though which is a fantastic improvement from the launch 1.0.0 version!

Also requires a username / password:

Username:  bobcat
Password:  miner

Reboot (Update 9/2/2021)

This was a new option added in version 1.0.2. It’s as simple as it sounds and allows you to reboot the miner through the web GUI. Very handy!

This option will prompt you for a username and password. Here they are:

Username:  bobcat
Password:  miner

Blockchain Height

Blockchain height just gets the current height of the Blockchain from the official Helium API. This would be useful if you wanted to write a very simple script that wanted to compare if your hotspot’s block matched the current block on the blockchain.

A lot of the other available commands give the blockchain_height already (such as “Sync Status” and “Miner”) so it’s not extremely useful.

Bobcat OTA Update / Troubleshooting (Community Res)

Don’t get too excited about these ones. These are not at all what they sound like. They’re both just web links to community resources (at least at 1.0.0 release).

Fast Sync (Alpha) (Update 9/11/2021)

This new feature was added in 1.0.4. It’s meant to help catch you up quickly to the blockchain. I had the chance to use it today as Bobcat has had a lot of issues with hotspots falling out of sync and mine has been impacted.

The function takes about 30 minutes to sync and you should be at least 400 blocks behind to use it. From Bobcat:

Fast Sync

This is an alpha feature that gives healthy miners a sync boost, so they can quickly catch up to the top of the blockchain from the block they are syncing at.

IMPORTANT: this feature will NOT work for healthy miners whose gap to the blockchain is smaller than 400 blocks.

Bobcat Miner 9/10/2021 Post

As usual the credentials will be:

Username:  bobcat 
Password:  miner 

Conclusion

The whole time I’ve had my Bobcat it has been a “black box”. Who knows what it’s doing. You can’t log into it with SSH or using the serial console (set your speed to 1,500,000 baud (yes, 1.5 million) and the serial console “data port” does work over USB in something like Putty, this is some kind of security through obscurity baud rate) because all the accounts are either disabled or have a nologin shell.

There’s only a couple of useful “tools” in 1.0.0 release that actually make the Bobcat do anything but it’s so nice to be able to finally see and be able to do *SOMETHING*! I’d imagine that more menu options will continue to be added to the Bobcat 300’s new “Diagnoser” tool over time.

I definitely at least recommend running the “Speed Test” and checking your unit’s temperature to make sure everything is running well!

Other Resources

For the best place to exchange your Helium (HNT) to other tokens like Bitcoin (BTC) check out my Best Altcoin Mining Pools and Exchanges article

If you have a Nebra hotspot check out my getting root and SSH access to the Nebra guide

To understand what is happening with Ethereum mining and when it is ending see my Why GPU / Ethereum Mining Is Toast – Stop Buying GPUs article

guest

131 Comments
Inline Feedbacks
View all comments

Alex
Alex
1 year ago

Hello guy, it’s possible to access this “Diagnoser Tool” outside the network somehow remotely using the router or something?

David bobcat
David bobcat
1 year ago

James, fantastic website/ guides. Super easy to use and understand, thank you for doing this. I am having an issue with my miner ever since the update 4 days ago (1.0.2.23S).
The miner had no issues and was synced/mining, then it went to a syncing status and got stuck at 99 percent. I went ahead and use the new feature, fastsync last night and it did clear up errors that were previously there.
This morning it’s still syncing and now says it needs attention. Below are the lastest logs, the only thing i noticed is that im behind on blocks. Any advice on a way forward?
timestamp "2021-09-14 15:55:55 +0000 UTC"
temp0 "72 °C"
temp1 "71 °C"
temp_alert "alert"
ota_version "1.0.2.23S"
sync_status ""
miner
State "running"
Status "Up 10 hours"
Names
0 "/miner"
Image "quay.io/team-helium/miner:miner-arm64_2021.09.03.0_GA"
Created 1631590913
height
0 "25850 1001680"
1 ""
epoch "25850"
miner_height "1001680"
blockchain_height "1010832"

David bobcat
David bobcat
1 year ago

James, great observation and feedback. The miner is inside on the third floor/attic space. It does get pretty hot and I’ve been turning off the AC to save on power. I will crank the AC and see what happens.

Insightful about the blocks as well, I calculated that I was 9,152 blocks behind. I subtracted the blockchain height with the miner height to get that answer, am I doing that wrong? If so if you have any resource on how to determine how far back I am it would be truly appreciated. Also, hope you don’t mind, but I’ve shared your site with my friends on discord :).

David bobcat
David bobcat
1 year ago

timestamp "2021-09-14 17:50:40 +0000 UTC"
temp0 51
temp1 50
unit "°C"

Thanks for the clarification on the math and owning the error! Also, you are brilliant. I fortunately can just put my miner in front of my AC and got the above results. The “needs attention” alert on the app went away so it’s a step in the right direction. I will now try the fast sync feature once more and report back on the result. I love when you troubleshoot something and actually get to a resolution, best feeling ever.

David bobcat
David bobcat
1 year ago

status ""
gap ""
miner_height "timeout"
blockchain_height "1011114"
epoch "RPC"

temps are super cool now

timestamp "2021-09-14 20:55:10 +0000 UTC"
temp0 42
temp1 40
unit "°C"

Here is the latest, it looks like my miner height timed out now, the bobcat miner is stuck on yellow. I gave it some time (a couple hours) and am wondering if I should unplug the miner and try the fast sync again. Any thoughts James before I try that?

Here are my current next steps for troubleshooting :
Power cycle then try Fast Sync again
Resync Miner
Reset Miner
Try these troubleshooting steps off the Helium site.

David bobcat
David bobcat
1 year ago

Just stopping in to give an update, I went ahead and rebooted and used fast sync again and the same thing happened, I was stuck on the same block height as before, which was “1001680”.

I went ahead and used the full re-sync feature and things seem to be moving towards the right direction, kinda. I checked my block height and it did change to “994345”, then I checked about an hour later and it’s “994475” currently. It’s at the very least moving so I will be patient and check in a few hours.

David bobcat
David bobcat
1 year ago

Interesting about the importance about the temperatures, but also you brought up a pretty interesting point. Since it’s early I may go ahead and give this a shot and just restart if things get messed up again but, I think I should use the fast sync option now since my miner is “healthy”. The gap is currently 16,000 so it would be a good benchmark. Thank you for the consultation, I love the bouncing of ideas. I am going to give this a shot and will report back here the results.

David bobcat
David bobcat
1 year ago

Don’t appear to be lucky with the fast sync, climbing slowly though.. at this rate ill be done in 8 or 9 days lol
"994345"
"994475"
"994577"
"994696"
"994720"

David bobcat
David bobcat
1 year ago

Hey James – You were right that it wouldn’t take 8-9 days, currently my gap is around 2272, “1010118” gap “2272”. Looks like things are going to be working here by this evening.

I wanted to ask, what should my height block be to be syncing? I think I read somewhere that it had to be at or above the blockchain height for it to be synced, is that accurate? A friend of mine just used the fast sync feature with success and he’s around 30 blocks behind, is that considered to be synced?

David bobcat
David bobcat
1 year ago

Thank for your response, I agree with your logic that it doesn’t make sense for the miner block to pass the blockchain height.

status "syncing"
gap "1964"
miner_height "1010983"
blockchain_height "1012947"
epoch "26130"

the gap is getting smaller but the progression slowed down. Do you think I should try the fast sync again or be patient? I would hate for the progress made thus far to be for nothing.

David bobcat
David bobcat
1 year ago

I haven’t done the net speed, below is the results for the first one. The miner is direct connected to an ethernet.

DownloadSpeed "63 Mbit/s"
UploadSpeed "14 Mbit/s"
Latency "13.768562ms"

Current sync status

status "syncing"
gap "1881"
miner_height "1011614"
blockchain_height "1013495"
epoch "26149"

The gap has closed a little but at this rate I don’t think it will ever catch up so I will consider the power cycle today. Another variable that I just thought of is the antenna, would this have anything to do with syncing? I don’t think it would but I purchased x2, 8dbi and x2, 5.8dbi. The antennas that have the 5.8 seem are both operating while the ones that have the 8dbi antennas don’t. Should I try swapping to the 4 dbi antenna the miner came with?

David bobcat
David bobcat
1 year ago

Thanks for info as always James, I didn’t get a chance to mess with the miner today but may have some time this evening/ tomorrow. I am going to go ahead and power cycle as it seems based on my snapshots the miner is starting to lag behind the gap.

(Yesterday)
status "syncing"
gap "1881"
miner_height "1011614"
blockchain_height "1013495"
epoch "26149"

(Today/ right now) status
"syncing"
gap "1886"
miner_height "1012234"
blockchain_height "1014120"
epoch "26168"

For the latest helium firmware update, is there any indication where I can see if its been applied or what version I am on? I believe that update you mentioned is 2021.09.14.0.

For now I am going to do a fast sync (if that doesn’t work)–> then a power cycle into a fast sync and see what happens. But of course first I need to figure out if I got the latest firmware update.

David bobcat
David bobcat
1 year ago
Reply to  David bobcat

Also, this is crazyyyyy lol I also wish they didn’t cheap out —> “It’s their software/firmware. They always manage to get it barely working again somehow but it never lasts more than a week or so before the same problem start again. I honestly think they just put way too little RAM / CPU power on the Bobcat and really cheaped out. All the hotspot manufacturers I’m sure wish at this point they would have got an extra 1GB of RAM and not been so cheap. They are paying for it now by trying to get a relatively demanding application at this point (Helium) to run on SBCs/embedded computers with 1GB of RAM (or less) on board which is slow/underequipped even by SBC standards (I was buying bigger Pis than the manufacturers gave us with these hotspots literally 5-8 years ago).”

David bobcat
David bobcat
1 year ago
Reply to  David bobcat

Welp great news, it seems like your deduction at putting two and two together worked. Identifying that the issue was related to the recent update, then advising on the fast sync again.

status "syncing"
gap "44"
miner_height "1014128"
blockchain_height "1014172"
epoch "26226"

While the status is still showing syncing, I am sure it will be remedied here in a much shorter time. Do you happen to have a discord or anything like that? I’d love to stay in touch james… otherwise I will keep bugging you on here :)! .. and will 100 percent confirm if the miner comes out of its flatlined state.

David bobcat
David bobcat
1 year ago
Reply to  David bobcat

challenge created, the miner is back! ty james!

Dennis Boboc
Dennis Boboc
1 year ago

Can someone help?? My miner is showing Relayed and I went thru all of the steps (at least I think I did) and I can’t get it to completely sync.

{
“timestamp”: “2021-09-13 23:54:46 +0000 UTC”,
“temp0”: “51 °C”,
“temp1”: “47 °C”,
“temp_alert”: “normal”,
“ota_version”: “1.0.2.23S”,
“sync_status”: “”,
“miner”: {
“State”: “running”,
“Status”: “Up 3 minutes”,
“Names”: [
“/miner”
],
“Image”: “quay.io/team-helium/miner:miner-arm64_2021.09.03.0_GA”,
“Created”: 1631577105
},
“height”: [
“26085 1009505”,
“”
],
“epoch”: “26085”,
“miner_height”: “1009505”,
“blockchain_height”: “1009896”,
“ports”: {
“44158”: “open”
},
“region”: “US915”,
“pubkey”: “112W3h1C4rUpjFp5F26xYw2o9xeXihMvWaDGmsgSAGgfQrTM28ku”,
“animal”: “boxy-goldenrod-huskie”,
“p2p_status”: [
“+———+——-+”,
“| name |result |”,
“+———+——-+”,
“|connected| yes |”,
“|dialable | yes |”,
“|nat_type | none |”,
“| height |1009505|”,
“+———+——-+”,
“”,
“”
],
“onboarding”: [
“”,
“********************”,
“General Manufacturing Info”,
“********************”,
“”,
“+————-+—————————————————-+”,
“| name | result |”,
“+————-+—————————————————-+”,
“| batch | bobcat_902 |”,
“| createdAt | 2021-09-02T20:27:33.577Z |”,
“|heliumSerial | null |”,
“| id | 263390 |”,
“| macEth0 | e8:78:29:53:94:d2 |”,
“| macWlan0 | 48:e7:da:65:22:15 |”,
“| makerId | 6 |”,
“|onboardingKey|112W3h1C4rUpjFp5F26xYw2o9xeXihMvWaDGmsgSAGgfQrTM28ku|”,
“|publicAddress|112W3h1C4rUpjFp5F26xYw2o9xeXihMvWaDGmsgSAGgfQrTM28ku|”,
“| rpiSerial | 7ac2c4d23eb55f59 |”,
“| updatedAt | 2021-09-10T22:40:37.944Z |”,
“+————-+—————————————————-+”,
“”,
“”,
“********************”,
“Manufacturer Info”,
“********************”,
“”,
“+——————+—————————————————+”,
“| name | result |”,
“+——————+—————————————————+”,
“| address |14sKWeeYWQWrBSnLGq79uRQqZyw3Ldi7oBdxbF6a54QboTNBXDL|”,
“| createdAt | 2021-02-24T22:16:39.379Z |”,
“| id | 6 |”,
“|locationNonceLimit| 1 |”,
“| name | Bobcat |”,
“| updatedAt | 2021-02-24T22:16:39.379Z |”,
“+——————+—————————————————+”,
“”,
“”
],
“errors”: “”
}

Kevin
Kevin
1 year ago

Hello James, first off i wanna say your information on your blogs are wonderful and your insight is greatly appreciated!!! I cannot connect to my bobcat diagnoser at all. I can confirm i am using the rite IP address of my miner, i am on the same local network, and the format i am entering is httx://192.168.X.X/. Google chrome gives me this error ERR_CONNECTION_TIMED_OUT everytime i try.

I do not want to open port 80 because of the security risk you have mentioned in the previous comments referring to a miner takeover (Please correct me if i am misunderstood). So how do i connect to my miner via google chrome (windows) with my private IP address instead of my public, as i assume this is what is causing the issue after reading what has previously been commented. Sorry if this is a silly question but any help would be appreciated!!!

Kevin
Kevin
1 year ago

tried this but no luck, no my understanding isnt this the way to do it if you have opened port 80. i have not done this, should i do this to be bale to use the diagnoser? i assumed opening the port would put my miner at more of a risk?

Kevin
Kevin
1 year ago

my bobcat is on wifi, and i am trying to access it via my windows 10 laptop on wifi, and they are both on the same wireless network. and i am using a unfi setup with no double NAT. i have gotten on to my other miners at my other locations where the wifi is alot more simple. I have somewhat of an idea what im doing when it comes to networking kinda haha. this is why i decided the use a whole unfi setup but at my home. sadly out of the 5 bobcats i have this is the only one i cannot connect to via IP.

Kevin
Kevin
1 year ago

thanks so much for your help so far no luck yet :/……how do you recommend pinging the minor from my laptop (windows 10)???… The minor and the laptop both have similar Ip addresses only differing by the last 4 numbers. and both devices are connected to the same unifi wireless access point on the same floor at my house and they are all on the same LAN…

Kevin
Kevin
1 year ago
Reply to  Kevin

after trying tp ping within windows cmd, it says destination host unreachable 4x then it loads to 4 packets sent / 4 packets received / 0 Lost…. it does this everytime i try running the ping command, im not sure if this is means its successfully communicating with my network or not.

Kevin
Kevin
1 year ago
Reply to  Kevin

the IP adress that is coming back through the cmd ping is not the one im entering in, it looks as if its coming from the public IP adress of the miner. my reasoning for this is it specifically says, reply from (ip address, which is not the private one i entered to ping) destination host unreachable 4x then it loads to 4 packets sent / 4 packets received / 0 Lost

Kevin
Kevin
1 year ago

thanks for your help, i believe you have identified the problem now i must find the remedy as i am still new to unifi. the unifi setup is actually my home i did this setup for a hobbyish approach but i can see this is going to be interesting. Do you have any idea on where to look to figure the rules needed within unifi to establish connection to the miner? i most certainly have full admin access to the network but nor full admin knowledge lol!

Kyle Smith
Kyle Smith
1 year ago

Hello James,

I’m getting relayed on 6 of my seven deployed miners. I’m using mifi and I have them all port forwarded with the bobcat diagnostic show the port open. However, I notice my “nat” settings in the diagnostic showed symmetric. Yours showed none. Any advice. My home unit works great!

Oliwer
Oliwer
1 year ago

Do you know credentials for Reboot option? It would be great to have that option, but without credentials it’s dummy option

Daniel V
Daniel V
1 year ago

Hi James, some great detailed info here! Thank you for that. I do have an issue though and perhaps you’d be able to give me some advise. Since 2 days ago everything flatlined. I logged in, saw that my miner “desynced” so to speak. Block height 1, epoch 1… that is all the way from being fully synced.
However, the main issue now is that I can not login to it from the Web, being on the same subnet and all, I also can not turn on the Bluetooth on it to run any diagnostics from my mobile app… so basically nothing at all… I’m lost to be honest. The lights switch from short timed yellow to long timed red. Rarely cyan.
My other bobcat is accessible and working…

Any thoughts? Any way to get in otherwise?

Thanks for your time in advance 🙂

Daniel

Daniel V
Daniel V
1 year ago

Thank you very much James for your reply and information! I shall try it as soon as I’m home from work today! 🙂
I’ll update once I have more news…
Have a great day!
Daniel

John R
John R
1 year ago

Hello,

I am having issues getting a browser to access the diagnostic tool. When I enter the ip address of the miner into any browser or device on my network I get a connection refused error “ERR_CONNECTION_REFUSED”.

Is this a known issue, and do you have any experience resolving something like this?

D M
D M
1 year ago

I am also having no luck communicating with my Bobcat. It is in relay mode. I setup up port forwarding as you laid out. In diagnostics it says the firmware is 7.22.2021. I rebooted it to see if it would trigger an update but no luck. Is this possibly because its stuck in relay mode and has no internet access?

Cory
Cory
1 year ago

I had 07.22 when I received it this past Thursday. Now, it’s running current firmware, but it has ERR CONNECTION REFUSED. Seems the Bobcat doesn’t have the webservice running or is just refusing connections on :80

Liviu-Adrian
Liviu-Adrian
1 year ago

hey James,
I have an issue with my bobcat, I cannot connect to it using the private IP, nor can ping it.
I do have port forwarding set up, also binded the IP to the MAC address, but nothing, in the Helium app it says the miner is online (not relayed), has 7 witnesses, but no rewards in the last 48 hours.
Any help will be greatly appreciated. Thank you!

Liviu-Adrian
Liviu-Adrian
1 year ago

And also when Ive try to go in Discovery Mode it says that “unable to initiate discovery mode, hotspot may be behind a relay and is not responding. check your router settings and try again” even though it is not relayed. Help me please

Cory
Cory
1 year ago

I’m on the same IoT VLAN as the miner with my laptop – miner and Mac are on the same subnet (192.168.1.x).

I can ping it by hostname and IP.

PING bobcatminer (192.168.1.101): 56 data bytes
64 bytes from 192.168.1.101: icmp_seq=0 ttl=64 time=3.316 ms

PING 192.168.1.101: 56 data bytes
64 bytes from 192.168.1.101: icmp_seq=14509 ttl=64 time=4.794 ms

% nc -z -v 192.168.1.101 80
nc: connectx to 192.168.1.101 port 80 (tcp) failed: Connection refused

% nc -z -v 192.168.1.101 44158
Connection to 192.168.1.101 port 44158 [tcp/*] succeeded!

Seems like the HTTPD service isn’t running on it.
Strange indeed.

Cory
Cory
1 year ago

I’ve got other things on the network that are functioning normally (a Synology NAS with Docker and services working on various ports). I would say that since :80 isn’t working on that IP, something’s wrong and it’s not worth potentially exposing the miner to the public. . Maybe the next OTA update might patch mine up. I’d reach out to Bobcat, but it’s been days since a ticket was opened for this issue. No reply yet.

Cory
Cory
1 year ago

I just got a reply back from them (Bobcat) from an email I sent them on Sunday (asking to update my unit).
Little did I know that it would update automatically.
I added my query of the diagnose page not working to the email reply back.
Will let you know what they say.

Gary R
Gary R
1 year ago
Reply to  Cory

I had the same issue and then tried httx://192.168.X.X:80 and the web interface loaded!

1 2 3 4