Public pool error conection on umbrel 1.4

1

hi
i have a bitaxe connected to my umbrel server with public pool.
after the update to version 1.4 it does not connect to umbrel.
i can’t get it to stay on Stratum Host and it immediately jumps to Fallback Stratum Host.
this is the message that the public pool log shows:

public-pool_server_1 | Error getmininginfo Error: ESOCKETTIMEDOUT
public-pool_server_1 | Error getmininginfo Error: ESOCKETTIMEDOUT
public-pool_server_1 | Error getmininginfo Error: ESOCKETTIMEDOUT
public-pool_server_1 | block height change
public-pool_server_1 | Killing dead clients
public-pool_server_1 | Deleting statistics
public-pool_server_1 | Deleted 0 old statistics

any suggestions ??

thanks

2

Same issues here running a Canaan Avalon Mini 3. Avalon shows hashing, but pool shows nothing. I’ve restarted the publicpool app several times, but no success. Any help is appreciated.

3

In my case, mysteriously, it started working normally. I just assigned a fixed IP address on the router to my Raspi4.
Although sometimes I have to restart public-pool because it jumps to the alternate server.
In my case, it’s a bitaxe gamma.

4

Same here, not showing any work.

5

I hope someone from the Umbrel or Public-Pool team, or even an advanced user, reads these posts and can help us with this.
On another note, in another matter (related to a server update), it was an advanced user who solved the problem for us.

6

I was able to connect to my Umbrel Home (version 1.4) by setting a static IP address in my router, so it’s always the same for Umbrel. I then did the same for each of my miners. With every mining device and Umbrel Home now on a static IP, I connect to my Umbrel Home Public Pool using my IP address like this example:

For BitAxe’s: Stratum URL: 192.168.0.229 Port: 2018 Stratum User: BTC address.worker

for Avalon’s: Pool Address: stratum+TCP://192.168.0.229:2018 Worker: BTC address.worker

The guidance from Public Pool saying to use “stratum+tcp://umbrel.local:2018” did not work for me. IP addresses do work, and all miners are hashing and pool information matches.

Hope this helps.

7

yes ive ran across some miners that want the URL in one field and the port in another “no stratum” lucky miner does it.. “underrated miners for $”

8

I would open some ports on your router.. ??? try them all its not getting the info its asking for.. ive seen it but it luckily bought up "in a second or 2. rarely have I seen that error tho..

9

I think it was a problem with the router. I assigned the Umbrella server a fixed IP address on the router, and everything is working fine. Thanks.

10

Was getting this same error, a lot. After trying a few things, the fix for me was increasing the - BITCOIN_RPC_TIMEOUT=10000 to 20000. Unverified, but I think this can be up to a max of 120000.

This setting can be found in ~/umbrel/app-data/public-pool/docker-compose.yml

Hope it helps someone