CorralPeltzer / newTrackon

newTrackon, a public open BitTorrent trackers monitoring tool
https://newtrackon.com
MIT License
612 stars 58 forks source link

Why HTTP connection failed? #301

Closed renfei closed 2 days ago

renfei commented 4 days ago

WX20241121-100757

My monitoring

WX20241121-101307

Cloudflare

WX20241121-101420

My Test

curl http://[2400:cb00:f00e::29a1:401c]:8080/announce -H "Host:tracker.renfei.net" -v

*   Trying 2400:cb00:f00e::29a1:401c:8080...
* Connected to 2400:cb00:f00e::29a1:401c (2400:cb00:f00e::29a1:401c) port 8080 (#0)
> GET /announce HTTP/1.1
> Host:tracker.renfei.net
> User-Agent: curl/7.81.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 400 Invalid Request
< Date: Thu, 21 Nov 2024 02:08:39 GMT
< Content-Type: text/html
< Transfer-Encoding: chunked
< Connection: keep-alive
< CF-Cache-Status: DYNAMIC
< Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=L4hHzCO4J%2Bh5y8xhEKQ7wD3utN51UR8wzEb9pC%2Fvut6Hp4gZGSAUkoIQPOyp3zRhqCoxOOSRG0N1dBEq2JcZWYBfxQOpsX0Uj3aie2d6F1NV57gBjrJenQpg7H0haUcrdbhazW5m26z9iBDcc2w5ZeY%3D"}],"group":"cf-nel","max_age":604800}
< NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
< Strict-Transport-Security: max-age=0
< Server: cloudflare
< CF-RAY: 8e5d2214c8407cbc-LAX
< server-timing: cfL4;desc="?proto=TCP&rtt=195481&sent=1&recv=3&lost=0&retrans=0&sent_bytes=0&recv_bytes=89&delivery_rate=0&cwnd=249&unsent_bytes=0&cid=0000000000000000&ts=0&x=0"
<
<title>Invalid Request</title>
* Connection #0 to host 2400:cb00:f00e::29a1:401c left intact

WX20241121-100921

p.s. Uptime takes a long time to restore ranking, I am very frustrated.

WX20241121-101027

renfei commented 4 days ago

Oh, I see! It was because of a bug in the BEP34 protocol that it was automatically upgraded to the HTTPS protocol.

I should delete the TXT record in the DNS.

Related issues:

renfei commented 4 days ago

Please help me downgrade to HTTP protocol, thanks.