Public-pool connection

General
1

I had my bitaxe pointed to my start9.local:3333. It was working fine…then I moved to parasite.wtf…and when I tried to move back to start9.local:3333…suddenly it keeps defaulting to my fallback pool…whats going on? Whybcant I connect?

2

I can’t imagine why. Perhaps there’ll be clues looking to see if your server is up and running, if Public Pool is in a good state and looking at the Public Pool logs. Those would be good places to start.

3

I’m having the same issue. Running Knots and Datum Gateway which I believe points to OCEAN mining pool on my StartOS. Also have a bitaxe gamma.
I’ve set both the primary and fallback pools in my AxeOS to my node IP because I cannot leave the fallback blank. On reboot, Bitaxe keeps switching between the pools and doesn’t connect immediately. Pooled mining is disabled on Datum. Could this be a timing issue with the node starting, or is there another workaround to ensure it connects reliably to my Node without switching to the fallback?”

4

I can’t really speak to the behavior of AxeOS, but I’d assume that switching to the fallback means it can’t connect to the first. OK, so they next step is to work out why.

Looking at AxoOS logs, Datum logs, actions you might have taken (you mention node starting – why was it even turned off?)

5

The bee link must’ve powered off some how…brown out maybe…but when I rebooted…I could access my start9 server…andvthe public-pool:3333 had some uptime, not long tho

6

Hi
I have pointed my bitaxe to both the IPV4 address and .local address of my Start9 server with the port 3333 but the Bitaxe logs keep reporting a network error (errno 128)?
The logs show connecting to the server → Socket created → then the error

edit: The logs in public pool show that it is listening on port 3333 suggesting that it is opening the port OK on the Start9 machine. DNS resolution of the .local address is working on the Nerdaxe log also.

Any idea why I can’t connect to this local instance of public pool?

Thanks
Garry

7

Public Pool isn’t going to know what simpleproxy is doing, it’s always going to know its ports are open, because from it to StartOS they are. To make the ports open in StartOS to your network is what simpleproxy does, and it’s something here where you’ll have to have made a small mistake.