pool connection error error: { code: -1, message: 'Unauthenticated' } }

[cron13]

Hi, I'm constantly getting these messages: pool connection error error: {code: -1, message: 'Unauthenticated'}}

After restarting the proxy, everything becomes fine. I am mine through pool.supportxmr.com 8892 and use scripts from this guide https://github.com/cazala/coin-hive-stratum/wiki/Deploy-to-now.sh-and-GitHub-Pages on frontend

[cazala]

Hi,

which version of the proxy are you using? make sure you are using the latest one v2.6.2.

You can see the version logged as the first line when starting the proxy, or by hitting the /version endpoint.

[osfcacuk]

I have noticed that if I kill the process that is mining rather than exit sometimes the proxy thinks the miner is still connected then after a while I got the same error message. However it didn't affect miners re-joining

[cazala]

If that's the case it shouldn't impact the hashrate, but it does impact on memory (garbage collector is not purging dead miners) and bandwidth usage (if the keepalives from disconnected miners are still being sent).

I'll look into it when I find some time. Thanks for reporting!

[tjosm]

I'm seeing this on V2.6.4

[cazala]

which pool?

[tjosm]

I'm behind XNP

[cron13]

i update proxy to v2.6.2 and problem gone

[matthewlilley]

I see this on 2.6.4 mining on Electroneum pools, not sure about Monero.

[matthewlilley]

Just checked, I see it on Monero pools also.

[patrickbau]

Can anyone help me with this error sometimes i see this error ,But i don't know how to know which version of the proxy and how to update to the version 2.6.4 Thank you

[cazala]

npm install -g coin-hive-stratum@latest if you use it from the CLI, or npm install --save coin-hive-stratum@latest if you use it from node_modules

[patrickbau]

Thank you Is that ok ?

• [email protected] added 32 packages in 3.367s

[cazala]

yes, you can check when you start the proxy it should log the version as the first line in the logs, or you can hit the /version endpoint while it's running to get the version as well.

[procloud]

something is definitely up with 2.6.6... i woke up this morning with a handful of miners connected but none where hashing.

[cazala]

have you tried v2.6.7?

[procloud]

i havent!

[matthewlilley]

Still present in 2.6.7, quite often I see:

pool connection error (7dcffa94-1c68-43a0-b6d0-71488badd4d8): {"code":-1,"message":"Invalid job id"} proxy error: undefined

[procloud]

still same issue, woke up this morning, miners connected, but not hashing with 2.6.7. no jobs coming from pool.

[matthewlilley]

There an issue mining to electroneum pools, I'd avoid it for now.