Giter VIP home page Giter VIP logo

Comments (15)

trexminer avatar trexminer commented on August 23, 2024

The miner tries to connect to *.trex-miner.com:443 to get the list of dev fee pools and then shuts down if failed. Please make sure connections to port 443 of those servers are not blocked by your firewall.

from t-rex.

teshy avatar teshy commented on August 23, 2024

My ISP (spectrum) does block ping so I cant see if I can hit trex-miner.com
I tried wget and the response is:
~$ wget trex-miner.com:443
--2019-10-03 11:58:24-- http://trex-miner.com:443/
Resolving trex-miner.com (trex-miner.com)... 45.77.35.138
Connecting to trex-miner.com (trex-miner.com)|45.77.35.138|:443... connected.
HTTP request sent, awaiting response... 400 Bad Request
2019-10-03 11:58:24 ERROR 400: Bad Request.

I get the same response on other networks as well, so this seams to be the expected response?

Any recommendations on how to test why it wont connect?

from t-rex.

trexminer avatar trexminer commented on August 23, 2024

Try curl -k https://srv1.trex-miner.com:443, you should get:

<head><title>400 No required SSL certificate was sent</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<center>No required SSL certificate was sent</center>
<hr><center>nginx</center>
</body>
</html>```

from t-rex.

android116 avatar android116 commented on August 23, 2024

0.14.4

TREX: T-Rex instance wasn't validated
WARN: Messy shutdown...

tсpdump shows that there are requests for srv5.trex-miner.com

but :

root@proxy:~ # nslookup srv5.trex-miner.com
Server:         127.0.0.1
Address:        127.0.0.1#53
** server can't find srv5.trex-miner.com: NXDOMAIN

root@proxy:~ # nslookup srv5.trex-miner.com 8.8.8.8
Server:         8.8.8.8
Address:        8.8.8.8#53
** server can't find srv5.trex-miner.com: NXDOMAIN

Substitution of srv5.trex-miner.com for 45.77.35.138 gives nothing. The miner still falls off.
:(

from t-rex.

trexminer avatar trexminer commented on August 23, 2024

The miner tries to connect to srv1.trex-miner.com first, and then proceeds to servers 2, 3, 4 and 5. What about srv1 and srv2? Are those accessible from your machine? Try curl -k https://srv1.trex-miner.com:443 as suggested above.

from t-rex.

android116 avatar android116 commented on August 23, 2024

The miner tries to connect to srv1.trex-miner.com first, and then proceeds to servers 2, 3, 4 and 5. What about srv1 and srv2? Are those accessible from your machine? Try curl -k https://srv1.trex-miner.com:443 as suggested above.

With srv1 and srv2 all is well. Resolve and respond, but there are no requests for srv1 or srv2 in the tcpdump log. Only on srv5.
In addition, it is at the time of the dump that no requests go anywhere.

upd: Also if that helps. the miner works for 3.5 minutes, after which it crashes.

from t-rex.

trexminer avatar trexminer commented on August 23, 2024

I've set up srv5 as an alias to srv2. Please try again and run tcpdump as well

from t-rex.

android116 avatar android116 commented on August 23, 2024

:(

Uptime: 3 mins 27 secs | Algo: x16rv2 | T-Rex v0.14.4
TREX: T-Rex instance wasn't validated
WARN: Messy shutdown...

tcpdump log from the start of the miner to its stop, but I don’t think it will help

tcpdump -v -i eth0 src trex-miner.com or dst trex-miner.com > /temp/tcp1.log

13:12:03.542174 IP (tos 0x0, ttl 64, id 23501, offset 0, flags [DF], proto TCP (6), length 60)
    cm04.lan.33166 > 45.77.35.138.vultr.com.https: Flags [S], cksum 0x8160 (correct), seq 2938108392, win 29200, options [mss 1460,sackOK,TS val 1216662325 ecr 0,nop,wscale 7], length 0
13:12:03.542608 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    45.77.35.138.vultr.com.https > cm04.lan.33166: Flags [S.], cksum 0x92f1 (correct), seq 2437345130, ack 2938108393, win 65228, options [mss 1460,nop,wscale 7,sackOK,TS val 2469481918 ecr 1216662325], length 0
13:12:03.542644 IP (tos 0x0, ttl 64, id 23502, offset 0, flags [DF], proto TCP (6), length 52)
    cm04.lan.33166 > 45.77.35.138.vultr.com.https: Flags [.], cksum 0xbfa4 (correct), ack 1, win 229, options [nop,nop,TS val 1216662326 ecr 2469481918], length 0
13:12:03.542955 IP (tos 0x0, ttl 64, id 23503, offset 0, flags [DF], proto TCP (6), length 52)
    cm04.lan.33166 > 45.77.35.138.vultr.com.https: Flags [F.], cksum 0xbfa3 (correct), seq 1, ack 1, win 229, options [nop,nop,TS val 1216662326 ecr 2469481918], length 0
13:12:03.543421 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    45.77.35.138.vultr.com.https > cm04.lan.33166: Flags [.], cksum 0xbe87 (correct), ack 2, win 513, options [nop,nop,TS val 2469481918 ecr 1216662326], length 0
13:12:03.588888 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    45.77.35.138.vultr.com.https > cm04.lan.33166: Flags [F.], cksum 0xbe58 (correct), seq 1, ack 2, win 513, options [nop,nop,TS val 2469481964 ecr 1216662326], length 0
13:12:03.588923 IP (tos 0x0, ttl 64, id 51052, offset 0, flags [DF], proto TCP (6), length 52)
    cm04.lan.33166 > 45.77.35.138.vultr.com.https: Flags [.], cksum 0xbf46 (correct), ack 2, win 229, options [nop,nop,TS val 1216662372 ecr 2469481964], length 0
13:12:13.556761 IP (tos 0x0, ttl 64, id 54757, offset 0, flags [DF], proto TCP (6), length 60)
    cm04.lan.33172 > 45.77.35.138.vultr.com.https: Flags [S], cksum 0x0545 (correct), seq 2146795017, win 29200, options [mss 1460,sackOK,TS val 1216672340 ecr 0,nop,wscale 7], length 0
13:12:13.557192 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    45.77.35.138.vultr.com.https > cm04.lan.33172: Flags [S.], cksum 0xa9c7 (correct), seq 545953499, ack 2146795018, win 65228, options [mss 1460,nop,wscale 7,sackOK,TS val 1928373337 ecr 1216672340], length 0
13:12:13.557221 IP (tos 0x0, ttl 64, id 54758, offset 0, flags [DF], proto TCP (6), length 52)
    cm04.lan.33172 > 45.77.35.138.vultr.com.https: Flags [.], cksum 0xd67a (correct), ack 1, win 229, options [nop,nop,TS val 1216672341 ecr 1928373337], length 0
13:12:13.559194 IP (tos 0x0, ttl 64, id 54759, offset 0, flags [DF], proto TCP (6), length 52)
    cm04.lan.33172 > 45.77.35.138.vultr.com.https: Flags [F.], cksum 0xd677 (correct), seq 1, ack 1, win 229, options [nop,nop,TS val 1216672343 ecr 1928373337], length 0
13:12:13.559631 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    45.77.35.138.vultr.com.https > cm04.lan.33172: Flags [.], cksum 0xd558 (correct), ack 2, win 513, options [nop,nop,TS val 1928373340 ecr 1216672343], length 0
13:12:13.603675 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    45.77.35.138.vultr.com.https > cm04.lan.33172: Flags [F.], cksum 0xd52b (correct), seq 1, ack 2, win 513, options [nop,nop,TS val 1928373384 ecr 1216672343], length 0
13:12:13.603718 IP (tos 0x0, ttl 64, id 52475, offset 0, flags [DF], proto TCP (6), length 52)
    cm04.lan.33172 > 45.77.35.138.vultr.com.https: Flags [.], cksum 0xd61b (correct), ack 2, win 229, options [nop,nop,TS val 1216672387 ecr 1928373384], length 0
13:12:23.577271 IP (tos 0x0, ttl 64, id 45349, offset 0, flags [DF], proto TCP (6), length 60)
    cm04.lan.33174 > 45.77.35.138.vultr.com.https: Flags [S], cksum 0x2f46 (correct), seq 2822964371, win 29200, options [mss 1460,sackOK,TS val 1216682361 ecr 0,nop,wscale 7], length 0
13:12:23.577701 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    45.77.35.138.vultr.com.https > cm04.lan.33174: Flags [S.], cksum 0x7ebf (correct), seq 2832793170, ack 2822964372, win 65228, options [mss 1460,nop,wscale 7,sackOK,TS val 2900545450 ecr 1216682361], length 0
13:12:23.577730 IP (tos 0x0, ttl 64, id 45350, offset 0, flags [DF], proto TCP (6), length 52)
    cm04.lan.33174 > 45.77.35.138.vultr.com.https: Flags [.], cksum 0xab72 (correct), ack 1, win 229, options [nop,nop,TS val 1216682362 ecr 2900545450], length 0
13:12:23.578077 IP (tos 0x0, ttl 64, id 45351, offset 0, flags [DF], proto TCP (6), length 52)
    cm04.lan.33174 > 45.77.35.138.vultr.com.https: Flags [F.], cksum 0xab71 (correct), seq 1, ack 1, win 229, options [nop,nop,TS val 1216682362 ecr 2900545450], length 0
13:12:23.578521 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    45.77.35.138.vultr.com.https > cm04.lan.33174: Flags [.], cksum 0xaa54 (correct), ack 2, win 513, options [nop,nop,TS val 2900545451 ecr 1216682362], length 0
13:12:23.624269 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    45.77.35.138.vultr.com.https > cm04.lan.33174: Flags [F.], cksum 0xaa26 (correct), seq 1, ack 2, win 513, options [nop,nop,TS val 2900545496 ecr 1216682362], length 0
13:12:23.624302 IP (tos 0x0, ttl 64, id 53409, offset 0, flags [DF], proto TCP (6), length 52)
    cm04.lan.33174 > 45.77.35.138.vultr.com.https: Flags [.], cksum 0xab14 (correct), ack 2, win 229, options [nop,nop,TS val 1216682408 ecr 2900545496], length 0

from t-rex.

teshy avatar teshy commented on August 23, 2024

Try curl -k https://srv1.trex-miner.com:443, you should get:

<head><title>400 No required SSL certificate was sent</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<center>No required SSL certificate was sent</center>
<hr><center>nginx</center>
</body>
</html>```

I do get the expected response:

<html>
<head><title>400 No required SSL certificate was sent</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<center>No required SSL certificate was sent</center>
<hr><center>nginx</center>
</body>
</html>

Here is my tcpdump:

tcpdump -v -i eno1 src trex-miner.com or dst trex-miner.com > tcp1.log
07:59:08.703399 IP (tos 0x0, ttl 64, id 40558, offset 0, flags [DF], proto TCP (6), length 60)
    teshy.ddns.net.54978 > 45.77.35.138.vultr.com.https: Flags [S], cksum 0x5c6f (incorrect -> 0x87db), seq 951759153, win 29200, options [mss 1460,sackOK,TS val 733023 ecr 0,nop,wscale 7], length 0
07:59:08.903143 IP (tos 0x0, ttl 50, id 2365, offset 0, flags [none], proto TCP (6), length 60)
    45.77.35.138.vultr.com.https > teshy.ddns.net.54978: Flags [S.], cksum 0x1578 (correct), seq 3562343289, ack 951759154, win 28960, options [mss 1460,sackOK,TS val 1113346327 ecr 733023,nop,wscale 7], length 0
07:59:08.903197 IP (tos 0x0, ttl 64, id 40559, offset 0, flags [DF], proto TCP (6), length 52)
    teshy.ddns.net.54978 > 45.77.35.138.vultr.com.https: Flags [.], cksum 0x5c67 (incorrect -> 0xb3b8), ack 1, win 229, options [nop,nop,TS val 733222 ecr 1113346327], length 0
07:59:08.903645 IP (tos 0x0, ttl 64, id 40560, offset 0, flags [DF], proto TCP (6), length 52)
    teshy.ddns.net.54978 > 45.77.35.138.vultr.com.https: Flags [F.], cksum 0x5c67 (incorrect -> 0xb3b6), seq 1, ack 1, win 229, options [nop,nop,TS val 733223 ecr 1113346327], length 0
07:59:09.102304 IP (tos 0x0, ttl 50, id 28029, offset 0, flags [none], proto TCP (6), length 52)
    45.77.35.138.vultr.com.https > teshy.ddns.net.54978: Flags [F.], cksum 0xb2ef (correct), seq 1, ack 2, win 227, options [nop,nop,TS val 1113346527 ecr 733223], length 0
07:59:09.102341 IP (tos 0x0, ttl 64, id 40561, offset 0, flags [DF], proto TCP (6), length 52)
    teshy.ddns.net.54978 > 45.77.35.138.vultr.com.https: Flags [.], cksum 0x5c67 (incorrect -> 0xb227), ack 2, win 229, options [nop,nop,TS val 733421 ecr 1113346527], length 0
07:59:18.913062 IP (tos 0x0, ttl 64, id 28747, offset 0, flags [DF], proto TCP (6), length 60)
    teshy.ddns.net.54980 > 45.77.35.138.vultr.com.https: Flags [S], cksum 0x5c6f (incorrect -> 0x5c13), seq 3334809355, win 29200, options [mss 1460,sackOK,TS val 743232 ecr 0,nop,wscale 7], length 0
07:59:19.121301 IP (tos 0x0, ttl 50, id 52033, offset 0, flags [none], proto TCP (6), length 60)
    45.77.35.138.vultr.com.https > teshy.ddns.net.54980: Flags [S.], cksum 0x0964 (correct), seq 3401567608, ack 3334809356, win 28960, options [mss 1460,sackOK,TS val 1113356537 ecr 743232,nop,wscale 7], length 0
07:59:19.121351 IP (tos 0x0, ttl 64, id 28748, offset 0, flags [DF], proto TCP (6), length 52)
    teshy.ddns.net.54980 > 45.77.35.138.vultr.com.https: Flags [.], cksum 0x5c67 (incorrect -> 0xa79b), ack 1, win 229, options [nop,nop,TS val 743440 ecr 1113356537], length 0
07:59:19.121646 IP (tos 0x0, ttl 64, id 28749, offset 0, flags [DF], proto TCP (6), length 52)
    teshy.ddns.net.54980 > 45.77.35.138.vultr.com.https: Flags [F.], cksum 0x5c67 (incorrect -> 0xa799), seq 1, ack 1, win 229, options [nop,nop,TS val 743441 ecr 1113356537], length 0
07:59:19.330522 IP (tos 0x0, ttl 50, id 31369, offset 0, flags [none], proto TCP (6), length 52)
    45.77.35.138.vultr.com.https > teshy.ddns.net.54980: Flags [F.], cksum 0xa6c8 (correct), seq 1, ack 2, win 227, options [nop,nop,TS val 1113356747 ecr 743441], length 0
07:59:19.330565 IP (tos 0x0, ttl 64, id 28750, offset 0, flags [DF], proto TCP (6), length 52)
    teshy.ddns.net.54980 > 45.77.35.138.vultr.com.https: Flags [.], cksum 0x5c67 (incorrect -> 0xa5f5), ack 2, win 229, options [nop,nop,TS val 743650 ecr 1113356747], length 0
07:59:29.130377 IP (tos 0x0, ttl 64, id 50695, offset 0, flags [DF], proto TCP (6), length 60)
    teshy.ddns.net.54982 > 45.77.35.138.vultr.com.https: Flags [S], cksum 0x5c6f (incorrect -> 0x9064), seq 3630545197, win 29200, options [mss 1460,sackOK,TS val 753450 ecr 0,nop,wscale 7], length 0
07:59:29.320218 IP (tos 0x0, ttl 50, id 32126, offset 0, flags [none], proto TCP (6), length 60)
    45.77.35.138.vultr.com.https > teshy.ddns.net.54982: Flags [S.], cksum 0x4218 (correct), seq 2298798823, ack 3630545198, win 28960, options [mss 1460,sackOK,TS val 1113366754 ecr 753450,nop,wscale 7], length 0
07:59:29.320264 IP (tos 0x0, ttl 64, id 50696, offset 0, flags [DF], proto TCP (6), length 52)
    teshy.ddns.net.54982 > 45.77.35.138.vultr.com.https: Flags [.], cksum 0x5c67 (incorrect -> 0xe062), ack 1, win 229, options [nop,nop,TS val 753639 ecr 1113366754], length 0
07:59:29.320538 IP (tos 0x0, ttl 64, id 50697, offset 0, flags [DF], proto TCP (6), length 52)
    teshy.ddns.net.54982 > 45.77.35.138.vultr.com.https: Flags [F.], cksum 0x5c67 (incorrect -> 0xe060), seq 1, ack 1, win 229, options [nop,nop,TS val 753640 ecr 1113366754], length 0
07:59:29.513168 IP (tos 0x0, ttl 50, id 65161, offset 0, flags [none], proto TCP (6), length 52)
    45.77.35.138.vultr.com.https > teshy.ddns.net.54982: Flags [F.], cksum 0xdfa1 (correct), seq 1, ack 2, win 227, options [nop,nop,TS val 1113366946 ecr 753640], length 0
07:59:29.513208 IP (tos 0x0, ttl 64, id 50698, offset 0, flags [DF], proto TCP (6), length 52)
    teshy.ddns.net.54982 > 45.77.35.138.vultr.com.https: Flags [.], cksum 0x5c67 (incorrect -> 0xdedf), ack 2, win 229, options [nop,nop,TS val 753832 ecr 1113366946], length 0

from t-rex.

android116 avatar android116 commented on August 23, 2024

Try curl -k https://srv1.trex-miner.com:443, you should get:

curl -k https://srv1.trex-miner.com:443
<html>
<head><title>400 No required SSL certificate was sent</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<center>No required SSL certificate was sent</center>
<hr><center>nginx</center>
</body>
</html>

This works, only the miner falls off anyway.
I even tried the tor as a proxy, but it didn't help either. It seems to me that the matter is something else.
I took another miner.
Yours will try when there is any next release.

from t-rex.

trexminer avatar trexminer commented on August 23, 2024

Could you please connect with me via discord channel or whatever comfortable to you? I will give you a debug miner assembly so as to try to find a problem.

from t-rex.

zohead avatar zohead commented on August 23, 2024

This also happens in my network, cURL output is normal,
while T-Rex always returns instance wasn't validated.

~ # curl -k https://srv1.trex-miner.com:443
<html>
<head><title>400 No required SSL certificate was sent</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<center>No required SSL certificate was sent</center>
<hr><center>nginx</center>
</body>
</html>
~ # curl -k https://srv2.trex-miner.com:443
<html>
<head><title>400 No required SSL certificate was sent</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<center>No required SSL certificate was sent</center>
<hr><center>nginx</center>
</body>
</html>
~ # curl -k https://srv3.trex-miner.com:443
curl: (6) Couldn't resolve host 'srv3.trex-miner.com'
~ # curl -k https://srv4.trex-miner.com:443
curl: (6) Couldn't resolve host 'srv4.trex-miner.com'
~ # curl -k https://srv5.trex-miner.com:443
<html>
<head><title>400 No required SSL certificate was sent</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<center>No required SSL certificate was sent</center>
<hr><center>nginx</center>
</body>
</html>

from t-rex.

trexminer avatar trexminer commented on August 23, 2024

This should be fixed in https://github.com/trexminer/T-Rex/releases/tag/0.14.6
Please let me know if it works

from t-rex.

zohead avatar zohead commented on August 23, 2024

Cool, 0.14.6 version fixed 'instace wasn't validated' bug.

from t-rex.

olegofff avatar olegofff commented on August 23, 2024

Error again - "instance wasn't validated"
Version 0.14.6
https://ibb.co/QvChMNJ
The miner gets the Internet through a local proxy.
If direct access to the Internet, then there is no problem

from t-rex.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.