Datum Gateway Connection To Bitaxe Miner

Services Support
1

For some reason I can’t seem to connect my Bitaxe miner to the Datum Gateway on my Start9 Server.

It used to work well but then it went south when I updated BOTH the Start9 OS and the Bitaxe firmware. I have a feeling the problem has to do with the Datum configuration but for the life of me I can’t figure out what it is.

I want to solo mine so I cleared the Pool Host, Port, and Pubkey fields in Datum settings and chose “Never” for collaborative reward sharing. My miner is pointed to my StartOS IP address (Stratum Host) with stratum port 23334. Both the miner and Datum Gateway have the same valid Bitcoin address entered. Start OS and Datum are the latest versions. I have Bitcoin Knots (pre-RDTS) installed.

Any hints on where I may have messed up? Like I said, it used to work before the updates.

Thanks in advance!

2

Does your expected Datum Server Local IPv4 x.x.x.x:23334 endpoint appear enabled in your Interfaces page for Datum? Does the Datum UI webpage open and show sensible values in each of the tabs? Can you ping the Bitaxe’s IP from the StartOS command-line? My Bitaxes are running against my Datum sever (also Knots pre-RDTS) OK. Similar setup.

3

I can open Datum UI and seems sensible to me. On the Interfaces page my IPv4 address is there and enabled. I’m not sure how to ping the Bitaxe’s IP from the StartOS command line (I do know the IP though). Is this done through a Terminal command on my Mac?

4

If you’ve followed the SSH setup instructions in the docs, you should be able to

ssh start9@servername.local

from your Mac.

5

Thanks. Then what’s the command to ping my Bitaxe’s IP? What do I look for?

6 
start9@start9-server:~$ ping -c 3 192.168.0.85
PING 192.168.0.85 (192.168.0.85) 56(84) bytes of data.
64 bytes from 192.168.0.85: icmp_seq=1 ttl=64 time=2.01 ms
64 bytes from 192.168.0.85: icmp_seq=2 ttl=64 time=8.15 ms
64 bytes from 192.168.0.85: icmp_seq=3 ttl=64 time=66.5 ms

--- 192.168.0.85 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 2.013/25.545/66.475/29.050 ms

replace with your Bitaxe’s IP address. I have seen with mixed wifi and wired networks sometimes devices aren’t able to see each other occasionally.

7

OK

I pinged my server:

Results:

~$ ping 192.168.XXX
PING 192.168.XXX (192.168.XXX) 56(84) bytes of data.
64 bytes from 192.168.XXX icmp_seq=1 ttl=64 time=8.85 ms
64 bytes from 192.168.XXX: icmp_seq=2 ttl=64 time=6.14 ms
ETC…

I hit Control C

Then I got this:

-– 192.168.XXX ping statistics —
153 packets transmitted, 153 received, 0% packet loss, time 152222ms
rtt min/avg/max/mdev = 3.104/5.832/48.669/3.805 ms

Is this good news?

8

Yeah, assuming that was from your start9 and 192.168.1.4 is your bitaxe. Your start9 is some other 192.168.1.x, I presume? Doesn’t look like a connectivity issue.

I don’t think you said if you got an actual error message anywhere. What does the bitaxe say in its logs? You might need to strip out sensitive info

9

I get an error message on my Bitaxe (AxeOS): “Using fallback pool - Share stats reset. Check Pool Settings and / or reboot Device.”

The Bitaxe logs make no sense to me; above my head. I could sample a big chunk but i’d probably unknowingly Doxx myself. They’re all green, if that helps.

Any way, the odds of mining a solo block were infinitesimally small anyway. It’s just frustrating that I didn’t used to get that error message before Start9 and Bitaxe updates. Thanks for your help!!!