mirror of
https://github.com/ngosang/trackerslist.git
synced 2026-04-25 09:25:59 +03:00
[GH-ISSUE #572] New Tracker Server #465
Labels
No labels
bug
enhancement
help wanted
pull-request
question
waiting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/trackerslist-ngosang#465
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Ghost-chu on GitHub (Mar 12, 2025).
Original GitHub issue: https://github.com/ngosang/trackerslist/issues/572
Address:
https://tracker.ghostchu-services.top/announcehttp://tracker.ghostchu-servides.top/announcewss://tracker.ghostchu-services.top/announce(for WebTorrent Protocol)udp://utracker.ghostchu-services.top:6969https & http & wss routing via CloudFlare.
UDP direct routing to Luxembourg.
Running PBH-BTN/Trunker as backend.
Live statistics can be viewed here:
https://grafana.ghostchu-services.top/public-dashboards/ae5337f1f1704ae2bd241f957317946c
I am the owner of this Tracker.
@renfei commented on GitHub (Mar 14, 2025):
Error 502
@Ghost-chu commented on GitHub (Mar 14, 2025):
@Ghost-chu commented on GitHub (Mar 14, 2025):
I have noticed that the NF ConnTrack table is full and causing the OS to be rejecting some of the connections.
Now that I have increased it to a more reasonable value, It should no longer have the 502 problem.
Edit: Received massive abnormal traffic and deal with it.
Edit2: Seems resolved.
@Ghost-chu commented on GitHub (Mar 14, 2025):
@renfei We have confirmed that our service suffered a DDoS attack today with over 78,000 per second concurrent requests, which is around the time your visit appeared 502.
I originally thought that a full NF ConnTrack table on our forwarding server was the culprit for the issue, so I adjusted it to a larger value. This action directly resulted in all attack traffic being forwarded to our backend server. Destroying everything including Tengine (nginx's fork), the Tracker program and everything else.
Since the traffic was sent directly through the relay server IP and not through CloudFlare, we didn't notice the attack had started. This directly led to the subsequent service outage.
I apologize for this. However, despite our efforts, I can't guarantee that the service will still be up and running the next time we are attacked.
This was an HTTP DDoS attack against our L7, so the DDoS defenses provided by our host do not cover this part.
I did some WAF work, limiting the request rate, adding request Token validation, and tweaking some kernel parameters.
But honestly, I don't think it will make a fundamental difference, but it should be better.
But I still think we are able and willing to offer Tracker services to the public. So I will keep this Issue open.
@renfei commented on GitHub (Mar 14, 2025):
I looked at your Tracker open source repository, it's a great project!
The Tracker traffic is very huge, which is similar to HTTP DDoS attack, so I lowered the defense threshold in Cloudflare firewall.
You may not be able to correctly distinguish whether it is normal request traffic or malicious HTTP flood attack.
However, in order to ensure the normal operation of the service, I will also limit the flow at the Cloudflare edge node to ensure the stability of the server.
The above is my experience, welcome to communicate.
@ngosang commented on GitHub (Mar 14, 2025):
Added. Thank you!
It looks like wss://tracker.ghostchu-services.top/announce is not working, but the others are fine.
@Ghost-chu commented on GitHub (Mar 14, 2025):
Hi,
I tested the wss protocol and it seems to work well with WebTorrents.
Edit: I've noticed that our Tracker may be too aggressive in recycling WSS connections, which may have something to do with WebSocket processing. I'll check that again later.
@ngosang commented on GitHub (Mar 14, 2025):
You tracker is not working well with WSS. You can check following these steps.
URL => wss://tracker.ghostchu-services.top:443/announce
Body:
Doing some tests in Python I can see your tracker responds these bytes, but they are not well encoded in UTF-8.
b'{"action":"scrape","files":{"\\u0008\xad\xa5\xa7\xa6\\u0018:\xae\\u001e\\t\xd81\xdfgH\xd5f\\tZ\\u0010":{"seeder":0,"complete":0,"incomplete":0,"downloaded":0}}}\n'@Gaojianli commented on GitHub (Mar 14, 2025):
since this isn't a doc of the the websocket tracker, our wss implements is just a reverse engineering of the js client. I will check this and try to fix it next week
@ngosang commented on GitHub (Mar 14, 2025):
Take a look at this bitorrent server too https://github.com/greatest-ape/aquatic
@Gaojianli commented on GitHub (Mar 17, 2025):
fixed
@Ghost-chu commented on GitHub (Mar 17, 2025):
wss://tracker.ghostchu-services.top:443/announce
ws://tracker.ghostchu-services.top:80/announce
both available
@ngosang commented on GitHub (Mar 17, 2025):
Added both!
@1265578519 commented on GitHub (Apr 1, 2025):
cloudflare cf误报http ddos可以搜索描述或者规则ID：Global L7 attack mitigations
c9f18c647ae745c6b81b459d8ed59b32
修改敏感度，默认值为高，设置成中，然后保存。最好直接本质上为关
其实客户端请求频率是正常的，可以抓每个ip的info_hash请求间隔，然后cf经常会tracker误报http ddos拦截访问