search

Roardom / UNIT3D-Announce

High-performance BitTorrent tracker compatible with UNIT3D tracker software
16 stars 3 forks source link

problem with seeding ip #8

Open oridark opened 2 weeks ago

oridark commented 2 weeks ago

There was a problem when obtaining the IP address of the user‘s seeding client I have used several clients to test, some in vps, some in my home computer, they all have public ip address, but the client ip shows on the website are wierd, like 162.158.19.72 which should be 185.150.18.57, it show right in other pt website, client is transmission 4.0.5 It seems to have something to do with Cloudflare's proxy feature

oridark commented 2 weeks ago

server ip is 152.53.109.235, nginx config add:

location ~ ^.(.(?:git|svn|htaccess|github))$ { return 403; } location /announce/ { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $host; proxy_pass http://127.0.0.1:6969$request_uri; real_ip_header X-Forwarded-For; real_ip_recursive on; set_real_ip_from 152.53.109.235; } listen 443 ssl; # managed by Certbot

and torrent tracker responce ok, seeding right, no error response, but on the website profile page, External Tracker info says: Tracker returned an error.

HDVinnie commented 1 week ago

This project is not officially released, unlicensed and not suited for production until then.

oridark commented 1 week ago

This project is not officially released, unlicensed and not suited for production until then.

what a pity and look forward to the official release, by the way, the seeding time might be wrong for that u3d system is using timezone time and announce always using utc time

Roardom commented 1 week ago

There is still lots to be changed before the first release. The code is still littered with println debug statements.

In addition to what HDVinnie said above, that error in UNIT3D is caused by Laravel's HTTP client throwing an exception or a non-200 HTTP response being returned.

Also, I would advise you to not change the default UTC timezone configured for UNIT3D. It's not meant to be changed. All timestamps for all running software should be UTC or things will break.

oridark commented 1 week ago

There is still lots to be changed before the first release. The code is still littered with println debug statements. In addition to what HDVinnie said above, that error in UNIT3D is caused by Laravel's HTTP client throwing an exception or a non-200 HTTP response being returned. Also, I would advise you to not change the default UTC timezone configured for UNIT3D. It's not meant to be changed. All timestamps for all running software should be UTC or things will break.

Thank you for your answer. Do you guys have a schedule on when the first release will be?

Roardom commented 1 week ago

I don't have an ETA, but most likely quite a far ways away, most likely not by the end of this calendar year. The current version is very rudimentary.