jerrywm / stratum-proxy-xmr Goto Github PK

I added 15 pools to settings.
Then my miner worked for 2 days in one of pool "stratum+tcp://etn-us-west1.nanopool.org:13333". This morning, I added a new pool : “stratum+tcp://pool.electroneum.hashvault.pro:5555” and connected to it. Some strange things happened.

1, When I click on the “Connect” of "stratum+tcp://pool.electroneum.hashvault.pro:5555", the backend is already connected to the "stratum+tcp://pool.electroneum.hashvault.pro:5555", but the pool status is shown as "Connect" instead of "Disconnect" on the front end, after I refresh the browser, it is ok and shown as "Disconnect"

2, On the "Console" page, there are still some new jobs from " stratum+tcp://etn-us-west1.nanopool.org:13333", and diff is 120001, as shown below.

3, On the "Jobs" page, it shows that 2 jobs are alive, and the 2 jobs belong to different pool, as shown below.

4. On the "Pools" page, only one pool is in the state of alive, as shown below:
   

On the pools page, the "connect time" cannot be sorted, as shown in the following diagram:

Proxy support for Monero v7 PoW?

There are 2 miner workers login in the proxy, and then the prxoy connecting the nicehash pool "stratum+tcp://cryptonight.eu.nicehash.com:3355", the following problems arise:

1, if enable "Emu nicehash", then the proxy will be rejected by the nicehash pool.

2, if disable "Emu nicehash", can normally connect nicehash pool, but 2 miners will receive a lot of rejection, as follows:

3、On the nicehash dashboard, there is only 1 worker's hashrate. It seems nicehash pool reject half of the 2 workers's hash.

4、2 miner workers use xmr-stak with "use_nicehash: true".

When connected many xmr-stak-cpu clients, most of the shares are being rejected with the error "Proxy Level Duplicate Shares". Most of the rejected shares have the same nonce and hash.

I do get some accepted shares, but the overall hashrate is very very low.

server: emu nicehash = false and workers = 100 and the server is NOT nicehash.
clients: nicehash_nonce = false

The clients can connect successfully with xmr-node-proxy.

Strange things... am use "xmrig classic" (written on C) with few mod...
found problem and plz confirm who can check....

configure miner:

1. first pool proxy
2. backup pool (some original pool direct connect)

config proxy:

1. start proxy
2. turn off in settings any pool you add
3. start miner

am add log to check, thay even not see that NO connection.. and not change to backup URL
[2018-03-15 19:19:05] JSON invalid job id
[2018-03-15 19:19:05] detected new block
[2018-03-15 19:19:14] JSON invalid job id
[2018-03-15 19:19:34] JSON invalid job id
[2018-03-15 19:19:54] JSON invalid job id
[2018-03-15 19:20:14] JSON invalid job id
[2018-03-15 19:20:34] JSON invalid job id
[2018-03-15 19:20:54] JSON invalid job id
[2018-03-15 19:21:05] check timer NO START backup_url
[2018-03-15 19:21:14] JSON invalid job id

not turn off miner, just turn on any pool in settings and you have set diff without start jub:

[2018-03-15 19:25:59] Set diff to 256
[2018-03-15 19:25:59] detected new block
[2018-03-15 19:27:05] detected new block
[2018-03-15 19:28:59] detected new block

I use three xmr-stack-amd ,ones has 3.8Kh/s ,but 2/3 of the shares are rejected about by the pool,only 1/3 of shares are accpted, please help to solve it.

Hello,
I have 10 rigs , when I plug them directly to the pool I got 64khs on CN-Heavy. When I plug them through the proxy I get 59khs, 5khs loss. Could you explain that?
Thanks

Hi. How to run PHP on your webserver? I don't understand JS, tell me how to do it.

Can you please add usage/compile instructions to the readme?

I'd like to try this, but I do not want to execute compiled code on my machine without building it myself.

Hi,

I just checked your project and it works perfect. Could you please add API endpoint also?

I will share a link just for sample. -> https://github.com/xmrig/xmrig/wiki/API

Thank you in advance.

Here I want to thank you very much for developing such a good software.
I use your latest version , when I edit pool settings "add" or "save", it will lead to the connecting pool becomes disconnected. I do not know if this is a problem or it was designed like this.

Whether the development can support "save" or "add" pool parameters, the pool will not be disconnected, continue to maintain its original state.

Hello, Is it possible to clear logs every 3000 entries?

Hello!
I have a problem whith nicenicehash. I set proxy settings: Emu nicehash = false, Max workers = 1.
Everything works well about 2-10 minutes and then it starts:
[3/21/2018 3:26:52 PM] [APP] [STRATUM-PROXY] [STRATUM-CLIENT #109] [NOTICE] Attempting to connect to [SSL OFF] [KPALV 60] [RSP TO 30] "cryptonight.eu.nicehash.com:3355"
[3/21/2018 3:26:52 PM] [APP] [STRATUM-PROXY] [STRATUM-CLIENT #110] [NOTICE] Attempting to connect to [SSL OFF] [KPALV 60] [RSP TO 30] "cryptonight.eu.nicehash.com:3355"
[3/21/2018 3:26:52 PM] [APP] [STRATUM-PROXY] [STRATUM-CLIENT #111] [NOTICE] Attempting to connect to [SSL OFF] [KPALV 60] [RSP TO 30] "cryptonight.eu.nicehash.com:3355"
[3/21/2018 3:26:52 PM] [APP] [STRATUM-PROXY] [STRATUM-CLIENT #112] [NOTICE] Attempting to connect to [SSL OFF] [KPALV 60] [RSP TO 30] "cryptonight.eu.nicehash.com:3355"
[3/21/2018 3:26:52 PM] [APP] [STRATUM-PROXY] [STRATUM-CLIENT #113] [NOTICE] Attempting to connect to [SSL OFF] [KPALV 60] [RSP TO 30] "cryptonight.eu.nicehash.com:3355"
[3/21/2018 3:26:52 PM] [APP] [STRATUM-PROXY] [STRATUM-CLIENT #114] [NOTICE] Attempting to connect to [SSL OFF] [KPALV 60] [RSP TO 30] "cryptonight.eu.nicehash.com:3355"

I turn off [KPALV 60], it became more stable but the problem still remained (falling proxy every 10-15 minutes).

root@proxy:~/Stratum-Proxy-XMR/src# node ./app/
/root/Stratum-Proxy-XMR/src/app/main.js:28
let config = null;
^^^

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:374:25)
at Object.Module._extensions..js (module.js:417:10)
at Module.load (module.js:344:32)
at Function.Module._load (module.js:301:12)
at Function.Module.runMain (module.js:442:10)
at startup (node.js:136:18)
at node.js:966:3
root@proxy:~/Stratum-Proxy-XMR/src#

I am looking for an "universal" proxy. basically to play around with so that I can change coins to mine easily. Is this proxy what I would be needing? and how do I install this on linux Ubuntu server 16.04?

Does it support failover ?

Pool1 goes down, connects to pool2 then back to 1 when it is live ?

Thanks
Steve

Hey. You have a very good proxy! I liked a different difficulty for miners. But there are several questions.
Why does the hash-rate jump? I have 17 miners, and with a straight line on the pool, it shows a hash rate of 2500 h / s. But when using a proxy, the hash-rate jumps between 800 and 3500 h / s. I understand that you need to wipe the hash-rate for 24 hours, but it's lower than when you dig out a 2300-2100 h / s.
What can I do to solve the problem?

I figured it out , sorry

It is just my localip:8888

Добрый день. Очень нравится ваш проект, но будут ли улучшения в работе прокси? Проект развивается?
Есть предложения в плане улучшения дизайна:
В списке пуллов хотелось бы вносить название монеты напротив используемого пулла. Часто пулл состоит из одного ip адреса и порта, и не совсем понятно что сейчас добывается.

Браузер после работы примерно с неделю-две, на странице прокси начинает сильно тормозить. Я так подозреваю, от того что при каждом переподключении майнера, статистика по майнеру останавливается, и начинается заново. И все старые статистики продолжают висеть в истории. Хотелось бы увидеть привязку работы к имени майнера, что бы не сбрасывал статистику, или сбрасывал отдельным действием.

В работе, с количеством майнеров до 15, с низким хешрейтом, все работает отлично. Как только подключаешь большие риги на прокси, на пулле график скачет очень сильно. При этом средняя добыча при подключении рига на прямую на пулл, получается выше, чем на прокси. На прокси, тем не менее статистику по ригу показывает точную.

С уважением, надеюсь проект будет развиваться.

Getting a lot of rejected shares despite checking the "emu nicehash" option. Any idea what the issue is?