xmr-node-proxy icon indicating copy to clipboard operation
xmr-node-proxy copied to clipboard

Error: Failed to parse block -- trying to mine Alloy (XAO)

Open tryingtomine opened this issue 7 years ago • 0 comments
trafficstars

My proxy has been working great for both XMR & ETN. I'm now trying to mine some XAO and found a nodejs-pool, which is alloy.west-pool.org. Support there says they are compatible with xmr-node-proxy but I cannot get it to work. I'm wondering if anyone knows what's wrong. I have re-done my config multiple times from a working template. I can mine to their pool directly with xmr-stak. I cannot figure this out. I have tried using their SSL port as well as their regular ports. I have tried enabling self signed SSL certificates. Seems like it's an issue with the block template, if that's the right words.

1|proxy | 2018-02-21 19:45 -05:00: Cluster master setting up 1 workers... 1|proxy | 2018-02-21 19:45 -05:00: Worker 7058 is online 1|proxy | 2018-02-21 19:45 -05:00: Master connected to pool: alloy.west-pool.org 1|proxy | 2018-02-21 19:45 -05:00: Received new block template from alloy.west-pool.org 1|proxy | 2018-02-21 19:45 -05:00: Started server on port: 3333 1|proxy | 2018-02-21 19:45 -05:00: Error: Failed to parse block 1|proxy | at Error (native) 1|proxy | at BlockTemplate.nextBlob (/home/nodeproxy/xmr-node-proxy/lib/xmr.js:70:23) 1|proxy | at Miner.getJob (/home/nodeproxy/xmr-node-proxy/lib/xmr.js:110:36) 1|proxy | at handleMinerData (/home/nodeproxy/xmr-node-proxy/proxy.js:867:28) 1|proxy | at handleMessage (/home/nodeproxy/xmr-node-proxy/proxy.js:992:13) 1|proxy | at TLSSocket. (/home/nodeproxy/xmr-node-proxy/proxy.js:1050:25) 1|proxy | at emitOne (events.js:96:13) 1|proxy | at TLSSocket.emit (events.js:188:7) 1|proxy | at readableAddChunk (_stream_readable.js:176:18) 1|proxy | at TLSSocket.Readable.push (_stream_readable.js:134:10) 1|proxy | 2018-02-21 19:45 -05:00: Worker 7058 died with code: 1, and signal: null

tryingtomine avatar Feb 22 '18 00:02 tryingtomine