New demo UDP tracker in Hetzner is not working in newtrackon.com

[josecelano]

Relates to: #405

I have deployed the new tracker demo to Hetzner using this deployer. I have verified everything manually, and it works.

I have submitted two trackers to newtrackon:

• HTTP tracker: https://http1.torrust-tracker-demo.com:443/announce
• UDP tracker: udp://udp1.torrust-tracker-demo.com:6969/announce

The new HTTP tracker is working fine, but for the UDP one, Hetzner is logging a UDP timeout:

NOTE: that the udp://tracker.torrust-demo.com:6969/announce tracker is the one in the old demo (Digital Ocean)

I don't even see it in the newtrackon rawdata:

udp://tracker.torrust-demo.com:6969/announce

I'm tracking the problems in this project becuase I wanted to document the first deployment to production here. In the future, issues related to the demo will be tracked in https://github.com/torrust/torrust-tracker-demo or https://github.com/torrust/torrust-tracker if it's a bug in the tracker.

cc @da2ce7

[josecelano]

The tracker works using our tracker client:

cargo run --bin udp_tracker_client announce udp://udp1.torrust-tracker-demo.com:6969/announce 9c38422213e30bff212b30c360d26f9a02136422 | jq
    Blocking waiting for file lock on artifact directory
   Compiling torrust-tracker-client v3.0.0-develop (/home/josecelano/Documents/git/committer/me/github/torrust/torrust-tracker/console/tracker-client)
    Finished `dev` profile [optimized + debuginfo] target(s) in 5m 52s
     Running `/home/josecelano/Documents/git/committer/me/github/torrust/torrust-tracker/target/debug/udp_tracker_client announce 'udp://udp1.torrust-tracker-demo.com:6969/announce' 9c38422213e30bff212b30c360d26f9a02136422`

{
  "AnnounceIpv4": {
    "transaction_id": -888840697,
    "announce_interval": 300,
    "leechers": 0,
    "seeders": 1,
    "peers": []
  }
}

I only see one error in the logs for the UDP tracker:

tracker  | 2026-03-05T15:03:18.901288Z ERROR process_request:handle_packet{server_service_binding=ServiceBinding { protocol: UDP, bind_address: [::]:6969 } request_id="663786a8-0b55-43e2-b0f0-9f6c1ff06eee"}:handle_error{req_kind=None client_socket_addr=[::x:x.x.x.x]:60337 server_service_binding=ServiceBinding { protocol: UDP, bind_address: [::]:6969 } request_id=663786a8-0b55-43e2-b0f0-9f6c1ff06eee cookie_valid_range=1772722877.9012663..1772722999.9012663 error=InvalidRequest { request_parse_error: SendableRequestParseError { message: "Invalid action", opt_connection_id: None, opt_transaction_id: None } } opt_transaction_id=None}: UDP TRACKER: response error error=error parsing request: SendableRequestParseError { message: "Invalid action", opt_connection_id: None, opt_transaction_id: None } client_socket_addr=[::x:x.x.x.x]:60337 server_socket_addr=[::]:6969 request_id=663786a8-0b55-43e2-b0f0-9f6c1ff06eee

The request was from an IPv4 IP mapped to IPv6. I do not know if that's the newtrackon IP.
There is only one ERROR record in the logs for the UDP tracker running on 6969.

In the past, I downloaded NewTrackOn to run it locally:

torrust/torrust-demo#26 (comment)

newtrackon reported a UDP timeout but I'm not sure if it was the new UDP tracker.

[josecelano]

It works when I run newtrackon locally:

josecelano@josecelano-desktop:~/Documents/git/committer/me/github/torrust/torrust-tracker-deployer-agent-01$  export PATH="$HOME/.local/bin:$PATH" && cd /home/josecelano/Documents/git/committer/me/github/CorralPeltzer/newTrackon && uv run python run.py --address=0.0.0.0 --ignore-ipv6 --no-import
2026-03-05 18:27:32,802 [INFO] [newtrackon] Server started
2026-03-05 18:27:38,834 [INFO] [tornado.access] 200 GET / (127.0.0.1) 7.54ms
2026-03-05 18:27:38,852 [INFO] [tornado.access] 304 GET /static/css/custom-v3.css (127.0.0.1) 2.19ms
2026-03-05 18:27:38,853 [INFO] [tornado.access] 304 GET /manifest.json (127.0.0.1) 0.46ms
2026-03-05 18:27:51,739 [INFO] [newtrackon] Tracker udp://udp1.torrust-tracker-demo.com:6969/announce submitted to the queue
2026-03-05 18:27:51,740 [INFO] [tornado.access] 200 POST / (127.0.0.1) 1.18ms
2026-03-05 18:27:51,740 [INFO] [newtrackon] Preprocessing udp://udp1.torrust-tracker-demo.com:6969/announce
2026-03-05 18:27:51,754 [INFO] [tornado.access] 304 GET /static/css/custom-v3.css (127.0.0.1) 0.62ms
2026-03-05 18:27:51,755 [INFO] [tornado.access] 304 GET /manifest.json (127.0.0.1) 0.43ms
2026-03-05 18:27:51,823 [INFO] [newtrackon] Tracker udp://udp1.torrust-tracker-demo.com:6969/announce added to the submitted queue
2026-03-05 18:27:51,823 [INFO] [newtrackon] Processing new tracker: udp://udp1.torrust-tracker-demo.com:6969/announce
2026-03-05 18:27:51,887 [INFO] [newtrackon] udp://udp1.torrust-tracker-demo.com:6969/announce Scraping UDP
2026-03-05 18:27:51,887 [INFO] [newtrackon] udp://udp1.torrust-tracker-demo.com:6969/announce UDP attempt 1
2026-03-05 18:27:52,028 [INFO] [newtrackon] udp://udp1.torrust-tracker-demo.com:6969/announce response: {'interval': 300, 'leechers': 0, 'seeds': 1, 'peers': []}
2026-03-05 18:27:55,063 [INFO] [newtrackon] New tracker udp://udp1.torrust-tracker-demo.com:6969/announce added to newTrackon
2026-03-05 18:28:08,330 [INFO] [tornado.access] 200 GET / (127.0.0.1) 0.70ms
2026-03-05 18:28:08,339 [INFO] [tornado.access] 304 GET /static/css/custom-v3.css (127.0.0.1) 0.52ms
2026-03-05 18:28:08,351 [INFO] [tornado.access] 304 GET /manifest.json (127.0.0.1) 0.56ms

[josecelano]

I have also executed this:

nc -vu udp1.torrust-tracker-demo.com 6969

Connection to udp1.torrust-tracker-demo.com (116.202.176.169) 6969 port [udp/*] succeeded!
error parsing request: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None }error parsing request: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None }error parsing request: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None }error parsing request: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None }error parsing request: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None }

And this was the log in the server:

tracker  | 2026-03-05T21:09:24.028154Z ERROR process_request:handle_packet{server_service_binding=ServiceBinding { protocol: UDP, bind_address: [::]:6969 } request_id="c2fc91f3-200d-4c58-aacd-8782b85d28ac"}:handle_error{req_kind=None client_socket_addr=[::ffff:2.137.92.24]:43688 server_service_binding=ServiceBinding { protocol: UDP, bind_address: [::]:6969 } request_id=c2fc91f3-200d-4c58-aacd-8782b85d28ac cookie_valid_range=1772744843.0281231..1772744965.0281231 error=InvalidRequest { request_parse_error: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None } } opt_transaction_id=None}: UDP TRACKER: response error error=error parsing request: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None } client_socket_addr=[::ffff:2.137.92.24]:43688 server_socket_addr=[::]:6969 request_id=c2fc91f3-200d-4c58-aacd-8782b85d28ac
tracker  | 2026-03-05T21:09:24.028266Z ERROR process_request:handle_packet{server_service_binding=ServiceBinding { protocol: UDP, bind_address: [::]:6969 } request_id="6d0cd6dc-e6d7-423b-b61f-be7e00e9afb0"}:handle_error{req_kind=None client_socket_addr=[::ffff:2.137.92.24]:43688 server_service_binding=ServiceBinding { protocol: UDP, bind_address: [::]:6969 } request_id=6d0cd6dc-e6d7-423b-b61f-be7e00e9afb0 cookie_valid_range=1772744843.028201..1772744965.028201 error=InvalidRequest { request_parse_error: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None } } opt_transaction_id=None}: UDP TRACKER: response error error=error parsing request: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None } client_socket_addr=[::ffff:2.137.92.24]:43688 server_socket_addr=[::]:6969 request_id=6d0cd6dc-e6d7-423b-b61f-be7e00e9afb0
tracker  | 2026-03-05T21:09:25.026489Z ERROR process_request:handle_packet{server_service_binding=ServiceBinding { protocol: UDP, bind_address: [::]:6969 } request_id="214f938a-44e7-4313-86d8-642722fb6028"}:handle_error{req_kind=None client_socket_addr=[::ffff:2.137.92.24]:43688 server_service_binding=ServiceBinding { protocol: UDP, bind_address: [::]:6969 } request_id=214f938a-44e7-4313-86d8-642722fb6028 cookie_valid_range=1772744844.0264533..1772744966.0264533 error=InvalidRequest { request_parse_error: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None } } opt_transaction_id=None}: UDP TRACKER: response error error=error parsing request: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None } client_socket_addr=[::ffff:2.137.92.24]:43688 server_socket_addr=[::]:6969 request_id=214f938a-44e7-4313-86d8-642722fb6028
tracker  | 2026-03-05T21:09:26.026620Z ERROR process_request:handle_packet{server_service_binding=ServiceBinding { protocol: UDP, bind_address: [::]:6969 } request_id="18260303-e349-4c72-a6d0-a9c1208ce350"}:handle_error{req_kind=None client_socket_addr=[::ffff:2.137.92.24]:43688 server_service_binding=ServiceBinding { protocol: UDP, bind_address: [::]:6969 } request_id=18260303-e349-4c72-a6d0-a9c1208ce350 cookie_valid_range=1772744845.0265775..1772744967.0265775 error=InvalidRequest { request_parse_error: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None } } opt_transaction_id=None}: UDP TRACKER: response error error=error parsing request: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None } client_socket_addr=[::ffff:2.137.92.24]:43688 server_socket_addr=[::]:6969 request_id=18260303-e349-4c72-a6d0-a9c1208ce350
tracker  | 2026-03-05T21:09:27.026579Z ERROR process_request:handle_packet{server_service_binding=ServiceBinding { protocol: UDP, bind_address: [::]:6969 } request_id="58d68ae0-e6a8-4c5a-98f5-3aa6d27976bd"}:handle_error{req_kind=None client_socket_addr=[::ffff:2.137.92.24]:43688 server_service_binding=ServiceBinding { protocol: UDP, bind_address: [::]:6969 } request_id=58d68ae0-e6a8-4c5a-98f5-3aa6d27976bd cookie_valid_range=1772744846.0265446..1772744968.0265446 error=InvalidRequest { request_parse_error: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None } } opt_transaction_id=None}: UDP TRACKER: response error error=error parsing request: SendableRequestParseError { message: "Couldn't parse action", opt_connection_id: None, opt_transaction_id: None } client_socket_addr=[::ffff:2.137.92.24]:43688 server_socket_addr=[::]:6969 request_id=58d68ae0-e6a8-4c5a-98f5-3aa6d27976bd

My ip: 2.137.92.24

[josecelano]

I forgot that there are a couple of restrictions when you submit a tracker to newtrackon. See https://newtrackon.com/faq

Especially the 1 and 3.

I think the problem is that I have already included the HTTP tracker, and newtrackon only allows one tracker per IP.

I have also forgotten to set up the DNS following BEP 34

I did it for the old demo tracker:

I was pointing in the wrong direction becuase at some point I saw a "UDP timeout" error. I guess newtrackon should improve the app to show an explicit error".

I will try with a new floating IP.

Relates to: CorralPeltzer/newTrackon#313