-
Notifications
You must be signed in to change notification settings - Fork 36
invalid json request is crashing it #24
Comments
Can you supply a debug of of the crash and json?
…On Feb 17, 2018 9:36 AM, "ethereumpy" ***@***.***> wrote:
any solution available ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#24>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIsrB7Uzugh5wsN6PFS6skrK1JuSNDuUks5tVuPvgaJpZM4SJVJv>
.
|
FWIW this seems to happen consistently on Ethermine but does not happen when connected to Nanopool which leads me to believe it's an Ethermine issue. {"id":999,"jsonrpc": "2.0","result": false,"error": "Invalid JSON request"} 4:21:01 PM <----< [192.168.1.1_52881] 4:21:01 PM: Server error for Miner: Invalid JSON request [192.168.1.1_52881] 4:21:02 PM: Error converting value ":" to type 'MinerProxy.JsonProtocols.EthClientRootObject'. Path '', line 1, position 3. 4:21:02 PM <----< [192.168.1.1_52881] 4:21:02 PM: Server error for Miner: Invalid JSON request |
I am using the proxy on Ethermine and I have not had any issues, what is your minerproxy config? |
FWIW ethermine was giving me an insane amount of stale shares. Greater than 50% so I've switched back to Nanopool for the moment. I know Claymore does the stale share thing... but I'm routing my miner traffic to an external address (not displayed below) so that it goes out my network and back in through my public facing IP address). Here was the config though. I also tried using the default 4444 ports too.
|
Don't see anything wrong with the config. |
any solution available ?
The text was updated successfully, but these errors were encountered: