Tracker ip changed to 185.30.164.12
-
First of all, sorry, :cry2: but this ip-changed was absolutely necessary for the futrue safeties of our Site. :hug:
If you still experience problems reaching our tracker from your client, your isp might have not updated the entries for both of our tracker domains…
tracker.gaytorrent.ru
tracker.gaytorrent.twthey should point to 185.30.164.12
use a command prompt on windows or terminal on osx:
start->run->cmd.exeand type
ping tracker.gaytorrent.twto check if the ip has already changed
if not, just reboot, which fix most cases and re-check. if this still not help and you don't like to wait up to 48 hours, you can just patch your
hosts file (%windir%\system32\drivers\etc\hosts) to reflect our new ip by just adding 2 lines:185.30.164.12 tracker.gaytorrent.ru 185.30.164.12 tracker.gaytorrent.twhere you can download a .bat file to automatically do this change:
https://www.gaytorrent.ru/hostfixwindowsgaytorrentru.bat run this with admin rights
finally reboot and enjoy
-
:afr2:
-
etc/hosts saves the day ;D
-
Dear Joker,
The batch file doesn't work in Windows 7 64 (at least not for me).
It might be worth adding a note that if users are running Avira or any other anti-virus programme, they made need to disable it before they can patch the hosts file.
Regards,
dances
-
What do I need to do for a Mac OSX? I'm running Mountain Lion and Transmission?
-
Am I correct in thinking that if I wait for 48 hours something will happen automatically which will correct the problem as Joker's message seems to state?
I have tried rebooting and no joy and I have no idea how to do any of the other suggestions. Perhaps someone could post a step by step guide for the computer illiterate. To be frank it lost me when it spoke of a coomand prompt.
-
ric58hard, you're probably best just waiting til your ISP catches up with the changes. Everything will still be here when it does and you may end up doing something useful while waiting for the pr0n to return
I spent hours the other day trying to change my system when the main address changed. I didn't know what was happening and I couldn't log on to find out. A friend who could log in was telling me to try all sorts of things. Nothing worked. Then I logged on a little later and everything was OK again.
The only hiccup I've had this time is that all the .tw tracker torrents (not files) needed to be downloaded again as the tracker seems to be .ru again.
See you on the 'other side'
-
The first thing to do, is to verify the IP your PC gets. For that, go to the "Start" menu, there select "Accessories" and then right mouse button click on the "Command Prompt" and select "Run as administrator".
Then in the window with black background which opens, type "ping tracker.gaytorrent**.ru**" without quotes and hit enter. Note the IP, timeout isn't of interest. Next type "ping tracker.gaytorrent**.tw**" and hit enter again. Note the IP.
If either of the two IPs is the old 85.159.237.127, type "ipconfig /flushdns" in that window. If it says sucess, type again the pings, which if your ISP DNS server got updated should show the new IP 185.30.164.12
If the new IP is shown with the ping's, reboot your PC.
In case only the .ru tracker ping shows the new IP, you could change in your torrent client's torrent properties the tracker from .tw into .ru
-
My dns ip has already been updated to 185.30.164.12 for tracker.gaytorrent.tw, starting torrents initially is fine (status code:working), but after a whilte changes to error code:
Tracker gave HTTP response code 503 (Service Unavailable)
This seems to be a problem with the tracker, not my computer. I started seeding 100 torrents. Is anyone else having this problem? pinging of 185.30.164.12 times out as well, although I do get a reponse from scraping the tracker.
-
icmp (ping) is disabled for our servers - so those timeouts are ok
503 means our DDOS network was not able to establish a connection to the backend (tracker)
so if you just wait and retry it gonna work. suchs timeouts aren't harmful for the tracking at all
-
Thanks for the info Joker. However, now I've noticed that twice when I started 113 torrents, I started having error 503, followed by timeouts on all 113 torrents. I stopped the torrents, and the timeouts continued for 6 hours; I also experience timeouts on the web site. After six hours, I started getting scrapes from the tracker again; it also took at least 6 hours to be able to access the website again. This happened twice. It's my impression that new settings on your DOS software bans me (my IP address) because it interprets starting so many seeding torrents as a DOS attack. I've been manually starting the torrents, but this is monotonous. Questions:
1. Does your DOS software ban IP addresses with the behaviour described above?
2. If it does, what are the settings ie 20 connections per second or what? If I know then I could start the torrents faster. I don't want to get banned
3. If it does ban as above, could the settings be made more similar to what they were before? I never had problems before -
thank you for reporting this
this problem is already under investigation…
it might have todo with the ddos protection system. dont worry, nobody gets banned forever. those ip ban's get released.hyperfilter is working on it. sorry for any problems due to this
-
Thank for looking into it. The torrents eventually scrape successfully, but it took a few hours. This might have something to do with my torrent client (transmission 2.75 (13675) taking a white to assemble the multiple scrapes into a single scrape
-
Our tracker has scrape deactivated. A torrent must be started to receive the peer list.
-
i'm on a mac, and suddenly the site wont work. it loads once in a while, but within minutes it stops loading. I dont know what's wrong. any ideas on how i can fix it?
-
Try to reboot your modem/router (the box from your ISP). If that doesn't help. Write to the Helpdesk and indicate your IP. You get your IP by typing "what is my IP" in Google search for example.
-
Thanks for the info Joker. However, now I've noticed that twice when I started 113 torrents, I started having error 503, followed by timeouts on all 113 torrents. I stopped the torrents, and the timeouts continued for 6 hours; I also experience timeouts on the web site. After six hours, I started getting scrapes from the tracker again; it also took at least 6 hours to be able to access the website again. This happened twice. It's my impression that new settings on your DOS software bans me (my IP address) because it interprets starting so many seeding torrents as a DOS attack. I've been manually starting the torrents, but this is monotonous. Questions:
1. Does your DOS software ban IP addresses with the behaviour described above?
2. If it does, what are the settings ie 20 connections per second or what? If I know then I could start the torrents faster. I don't want to get banned
3. If it does ban as above, could the settings be made more similar to what they were before? I never had problems beforeI am having very similar symptoms and I also have a large number of active seeding torrents (about 50+).
I also end up not being able to connect to the tracker or load the website, presumably because of my IP getting banned (using a different IP works).
-
Oh, is that why this site always seems down for me lately, giving my seeds 503s and nothing in my browser? I'm seeding too many torrents?
-
There were made some adjustments and torrents should no longer be the cause of the page not loading or of errors.
Personally I get often white screens or 502 errors, which disappear after refreshing the page. The Administrators still search for the cause of that to fix it.
-
It looks like you have changed the scraping internal for torrents to 90 minutes. Well, I tried it again. I stopped my torrents and restarted 100 of them; the same thing happened: error 503, followed by timeouts on the trackers and the website. So it's the same. Not a big problem for the torrents; if you leave them running then after several hours they will scrape again successfully. I still remember when gaytorrent.ru had a DOS attack, so I see why you guys are doing this. But I would hope that it is possible to change it so the timing out on the website does not occur.
