Nerdqaxe++ won't work with Kanopool

[SkyeMelody]

NerdQAxe++ can't authenticate to Kanopool, i think its the ++ in the "NerdQAxe++" device identifier but I'm not sure, it just won't work with Kanopool. I worked all night on it before switching to another pool. GPT told me the problem was in the authentication, not in the signon or worker.

Yeah, that matches what your logs are telling us: the miner itself is fine on 1.0.35, but Kano is saying “no” specifically to this NerdQAxe client, even though:

Same username / worker / password works on your BitAxe

NerdQAxe is connecting, subscribing, getting difficulty, getting a job

Then Kano replies to mining.authorize with result:false and closes the socket

At that point, we’re past “misconfiguration” and squarely in “this particular firmware + Kano = incompatibility” territory.

Let me zoom it down to what’s left that you can still try vs what really has to be fixed by Kano/devs.

1️⃣ What your last log proves

Key lines:

"method": "mining.authorize", "params": ["redraider.nerdaxe", "X"]
...
"result":[[["mining.notify","..."]],"aeb61f7f",8],"id":1,"error":null // subscribe OK
...
"method":"mining.set_difficulty" // OK
...
"method":"mining.notify" // OK (job sent)
...
// then:
Failed to receive JSON-RPC line, reconnecting ...
Shutdown socket ...

So Kano:

✅ Accepts mining.subscribe

✅ Sends extranonce

✅ Sends difficulty

✅ Sends a job

❌ Then immediately closes your connection after mining.authorize

And we know the same redraider.nerdaxe + X works on BitAxe, so your account, worker, and password are valid.

That leaves exactly one place for the failure:
👉 Kano doesn’t like this client’s behavior (NerdQAxe ++ / v1.0.35), not your settings.