T-Rex - I can't connect to the pool

Miners
1

20211026 09:42:59 T-Rex NVIDIA GPU miner v0.24.5 - [Linux]

20211026 09:42:59 r.3ed63f02e8cb

20211026 09:42:59

20211026 09:42:59

20211026 09:42:59 NVIDIA Driver v470.74

20211026 09:42:59

20211026 09:42:59 + GPU #0: [00:01.0|2489] GeForce RTX 3060 Ti, 7981 MB

20211026 09:42:59 + GPU #1: [00:06.0|2489] GeForce RTX 3060 Ti, 7982 MB

20211026 09:42:59

20211026 09:42:59 WARN: DevFee 1% (progpow-veriblock)

20211026 09:42:59

20211026 09:42:59 URL : stratum+tcp://vbk-reb0rn.ddns.net:8502

20211026 09:42:59 USER: V3JYieSmYLWiqZsQixfEiEgZr43LD2

20211026 09:42:59 PASS: x

20211026 09:42:59

20211026 09:42:59 WARN: Built-in watchdog has been disabled!

20211026 09:42:59 Starting on: vbk-reb0rn.ddns.net:8502

20211026 09:42:59 Using protocol: stratum2.

20211026 09:42:59 WARN: failed to stratum2-subscribe on vbk-reb0rn.ddns.net:8502: can’t parse json:

  • Line 1, Column 1

Syntax error: value, object or array expected.

20211026 09:42:59 ERROR: No connection with vbk-reb0rn.ddns.net:8502, retry after 10 seconds

20211026 09:42:59 ApiServer: HTTP server started on 127.0.0.1:4059

20211026 09:42:59 ---------------------------------------------------

20211026 09:42:59 For control navigate to: http://127.0.0.1:4059/trex

20211026 09:42:59 ---------------------------------------------------

20211026 09:43:00 GPU #1: intensity 20

20211026 09:43:00 GPU #0: intensity 20

20211026 09:43:09 Using protocol: stratum2.

20211026 09:43:10 WARN: failed to stratum2-subscribe on vbk-reb0rn.ddns.net:8502: can’t parse json:

  • Line 1, Column 1

Syntax error: value, object or array expected.

i have upgraded the T-Rex, i have downgraded the Hiveos, i have changed the miner and nothing helps. Yesterday everything was ok

2

other pool

20211026 12:41:21 Starting on: vbk.qp.be:8502
20211026 12:41:21 Using protocol: stratum2.
20211026 12:41:21 ApiServer: HTTP server started on 127.0.0.1:4059
20211026 12:41:21 ---------------------------------------------------
20211026 12:41:21 For control navigate to: http://127.0.0.1:4059/trex
20211026 12:41:21 ---------------------------------------------------
20211026 12:41:21 GPU #1: intensity 20
20211026 12:41:21 Authorizing…
20211026 12:41:21 GPU #0: intensity 20
20211026 12:41:21 Authorized successfully.
20211026 12:41:21 progpow-veriblock epoch: 652, block: 2632595, period: 521659, diff: 429.50 M
20211026 12:41:22 WARN: Connection with pool vbk.qp.be:8502 timed out. Trying to reconnect…
20211026 12:41:22 Using protocol: stratum2.
20211026 12:41:22 Authorizing…
20211026 12:41:22 Authorized successfully.

after a few minutes of operation, the same happens as in the first post

20211026 12:47:31 ERROR: No connection with vbk.qp.be:8502, retry after 10 seconds

----------20211026 12:47:32 ----------
Mining at vbk.qp.be:8502, diff: 1.39 G
GPU #0: RTX 3060 Ti - 0.00 H/s, [T:43C, P:48W, F:71%, E:0.00H/W], 17/17 R:0% I:0%
GPU #1: RTX 3060 Ti - 0.00 H/s, [T:40C, P:37W, F:52%, E:0.00H/W], 12/12 R:0% I:0%
Hashrate: 0.00 H/s, Shares/min: 6.658 (Avg. 6.327), Avg.P: 85W, Avg.E: 0.00H/W
Max diff share was found by GPU #1, diff: 25.32 G
Uptime: 6 mins 11 secs | Algo: progpow-veriblock | T-Rex v0.24.5

20211026 12:47:42 Using protocol: stratum2.
20211026 12:47:42 WARN: failed to stratum2-subscribe on vbk.qp.be:8502: can’t parse json:

  • Line 1, Column 1
    Syntax error: value, object or array expected.

20211026 12:47:42 ERROR: No connection with vbk.qp.be:8502, retry after 10 seconds
20211026 12:47:52 Using protocol: stratum2.
20211026 12:47:52 WARN: failed to stratum2-subscribe on vbk.qp.be:8502: can’t parse json:

  • Line 1, Column 1
    Syntax error: value, object or array expected.
3

I’m having the same issue and I have tried multiple pools and servers with in the pool and continue to get the same error when I try to dual mine. Any Ideas what is wrong.

4

now the SERO coin gives the most profit for cards with LHR

5

By the way… the fix was to switch your rig under Lan Configuration … To static IP.
Bingo… worked 5 seconds after for me.

6

This topic was automatically closed 416 days after the last reply. New replies are no longer allowed.