lolMiner cannot connect to MiningRigRentals (MRR) - EXP/ETH

[PSLLSP]

lolMiner_v1.46a_Lin64.tar.gz

One more issue with lolMiner and MRR pool. This one is not about client.reconnect. I do not know what is wrong in this case, lolMiner doesn't have any parameter for troubleshooting (like --debug, --verbose, --protocol-dump). I first found this problem when I tried to mine ETH but I use example for EXP, the same algo and the same result. Error is Error: Worker not authorized, it means that miner uses credentials in a wrong way.

Example:

$ cat mine-exp-mrr-6.sh
#!/bin/sh

# EXP@MRR

POOL="eu-de01.miningrigrentals.com:3344"

USER="droidMiner.218797"
PASS="TEST6"

ALGO="ETHASH"
OPTS=""
#OPTS="--worker TEST6"

./lolMiner --algo "$ALGO" --pool "$POOL" --user "$USER" --pass "$PASS" $OPTS "$@"

$ sh mine-exp-mrr-6.sh --nocolor
...
Setup Miner... 
OpenCL driver detected.
Number of OpenCL supported GPUs: 1 
Cuda driver detected.
Number of Cuda supported GPUs: 1 
Device 0: 
    Name:    NVIDIA GeForce GTX 1060 3GB 
    Address: 1:0 
    Vendor:  NVIDIA Corporation
    Drivers: Cuda
    Memory:  3019 MByte 
    Active:  true (Selected Algorithm: ETHash Cuda) 

Connecting to pool... 
DNS over HTTPS resolve succeeded 
Connected to eu-de01.miningrigrentals.com(188.166.161.62):3344  (TLS disabled)
Set Ethash stratum mode: Ethereum Proxy
Error: Worker not authorized: droidMiner.218797 
Authorization problem on all configured pools 
Terminating lolMiner

Proof, that miner configuration is correct, miniZ can mine at MRR:

$ cat test-exp.mrr-7.sh
#!/bin/sh
  
# mine some ETHASH crypto @ MRR

POOL="eu-de01.miningrigrentals.com:3344"

USER="droidMiner.218797"
PASS="TEST7"

ALGO="ETHASH"
OPTS=""

./miniZ --par="$ALGO" --server="$POOL" --user="$USER" --pass="$PASS" $OPTS "$@"

$ sh test-exp.mrr-7.sh
************ miniZ v1.8y3 ************
Number of CUDA[8.0] devices found: 1
miniZ<ethash>[99:1:00.0:2921]: Selecting GPU#0[0] NVIDIA GeForce GTX 1060 3GB
Driver:         470.10
Algo:           EQ[ethash] [smart-pers]
Pool#0:         user[droidMiner.218797]
                server[eu-de01.miningrigrentals.com] port[3344] ssl[no] pers[ethash]
Telemetry:      [http://localhost:20000]
Temp. limit:    [90°C]
[INFO   ] Mining fee set to 0.75%
[INFO   ] GPU[0]: Generating DAG #199 [2615+40=2656MB]
[INFO   ] GPU[0]: Generated DAG in 17.785
[ 0d 0h 0m29s] 0>GTX 1060 3GB ` 100% [58°C/44%]  18.69(18.69)MH/s  71( 70.8)W clk=1657MHz mclk=3802MHz MH/W=0.26

---

UPDATE. I used Wireshark and I see the BUG in lolMiner. It uses username in a wrong way...

Note that lolMiner uses as username only droidMiner, but the correct username is droidMiner.218797!

lolMiner, communication:

{"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"218797","params":["droidMiner", "TEST6"]} 
{"jsonrpc": "2.0","result": false,"error": "Client Pre-authorization was not accepted (incorrect workername, check your settings).","id":1}

miniZ, communication:

{"id":1,"method":"mining.subscribe","params":["miniZ/1.8y3","EthereumStratum/1.0.0"]}
{"jsonrpc":"2.0","id":1,"result":true}
{"id":2,"method":"mining.authorize","params":["droidMiner.218797","TEST7"]}
{"id":2,"jsonrpc":"2.0","result":true,"error":null}
{"id":3,"method":"mining.extranonce.subscribe","params":[]}
{"id":0,"method":"mining.notify","params":["074bf54a80e638d03b97502da3f577e3a70e7ef2ea716d2b94897b601120c5c7","0x074bf54a80e638d03b97502da3f577e3a70e7ef2ea716d2b94897b601120c5c7","0xe3344270250ed430ef80a4c1001cfccccf351da0cbbc36dc3c29bfd26baa25b2","0x7e00000007e00000007e00000007e00000007e00000007e00000007e",true]}
{"jsonrpc":"2.0","id":3,"result":true}

[jgonzis]

Many thanks for the feedback information...