Found the problem. For any connection using NodeJS, you must enable the following global setting: process.env['NODE_TLS_REJECT_UNAUTHORIZED'] = '0'; This is due to the fact that something is wrong with the SSL certificate on the server - it either doesn't match domain, does not support subdomains, s...

Right now, my theory is that either autobahn and wampy packages both use somehow incompatible websocket module or server has some type of cross-origin policy that allows only web browser to connect.. Do you have "Access-Control-Allow-Origin" type of setting in whatever serves the WAMP webs...

arguments is a JavaScript keyword which contains an object of arguments of the function...

https://developer.mozilla.org/en/docs/W ... /arguments

@steve - what technology is the core that manages miner assignment is written in?

I have tried everything and am unable to connect to WAMP from NodeJs. Funny thing is that I see that site UI is connecting properly with same credentials and practically the same code. I tried autobahn and wampy, all with no results. As if the websocket doesn't respond. Here is some test code: var a...

CleverMining is shutting down as of 26th of April, that is the immediate reason. BitMain shipping L9s in May-June is the upcoming reason. You should re-invest in your infrastructure as well as look at horizontal scaling solutions. If I may also suggest to remove some real-time features of the UI and...