Posts made by MrMazda

There's not really much we can do about it unfortunately.

@tempdownload:

Any update on the status of the SSL certificate fix on your end?

Turning off SSL tracker doesn't always work.

Actually, I just noticed you are using Transmission 3.0…. THAT is your problem in your case. You will find that if you roll it back to the previous version (2.94), you should have no issue anymore.

@SimonSaid:

@MrMazda:

This error message means that your torrent client is choking on the SSL certificate. In order to get around this, you need to disable the SSL tracker in your profile. You may also need to change the announce URL in your torrent client. Specifically, change the beginning from

https://tracker.gaytorrent.ru/

to

http://tracker.gaytorrent.tw:2710/

Do you know what's the root issue though?
For one I'd rather keep using the SSL tracker. Also I don't really feel like modifying the 150+ torrent files I'm seeding or having to re-download and re-hash them…  :-[
[/quote]

Some torrent clients do not want to play well with our SSL CA certificate issuer for some reason.

If you've changed from the SSL to the non-SSL tracker and are still having issues, you may need to use a VPN to connect to our services.

Also, it should be noted that for some reason, Transmission 3.0 will not work with our tracker any longer for some reason. Instead, if you're using Transmission, roll back to the previous version (2.94) and you should have no issues.

This limit was first put into place due to users who we had who were mass spamming literally EVERYONE. Unfortunately, no system is perfect and some messages that should be getting through cannot due to this security upgrade.

From the looks of it, you may need to use a VPN to connect through to our system.

This topic has been moved to Requests - Porn.

https://forum.gaytorrent.ru/index.php?topic=66730.0

@tempdownload:

I'm using Transmission 3.0 and all torrents still say cannot connect to tracker

You may find you have no end of difficulty with Transmission 3.0. You may need to roll back to version 2.94

@yalenxxx:

@MrMazda:

This will connect to the regular tracker, rather than the SSL tracker.

IT WORKED!!! sorry for my english.. so everytime i download a torrent I have to change the tracker?

You can make this change permanent by clicking the "Profile" tab at the top of the page, then disabling the SSL tracker, and saving the changes at the bottom of the page.

This topic has been moved to Requests - Porn.

https://forum.gaytorrent.ru/index.php?topic=66727.0

For users who are having a problem with the SSL certificate, you may need to use the non-SSL tracker. To do this, change the beginning of the announce URL from:

https://tracker.gaytorrent.ru/

to

http://tracker.gaytorrent.tw:2710/

You can also make this change permanent in your profile using the "Profile" tab at the top of the page, and disabling the SSL tracker.

Your history in qBitTorrent will show you all the data that has been transferred since the torrent was added to your client. The stats on the site on the other hand will only show you the status for the current session. If for any reason the session is stopped, such as you reboot your computer or you close your torrent client, the stats on the site will reset to zero. That being said, all totals ARE counted towards your overall totals, which affect your ratio.

This error message means that your torrent client is choking on the SSL certificate. In order to get around this, you need to disable the SSL tracker in your profile. You may also need to change the announce URL in your torrent client. Specifically, change the beginning from

https://tracker.gaytorrent.ru/

to

http://tracker.gaytorrent.tw:2710/

@yalenxxx:

@MrMazda:

We were having problems with our tracker earlier, which was causing a lot of stuff to not work. The issue should now be resolved.

no it's not

Is there a particular error messag that you're getting from the tracker?

As far as I am aware, there is no way in which to do this.

It should also be noted that users who are using Transmission 3.0 have experienced no end of trouble trying to reach the tracker, and rolling back to version 2.94 seems to resolve the issue.

Based on a number of user reports, users who are running Transmission 3.0 are having no end of difficulty with the tracker. As well, users who are using NordVPN have also reported that they are unable to connect to the tracker as well.

When you do try to connect and seed or leech a torrent, is there an error message that you're getting from the tracker, and if so, what is the error message?

Unfortunately, there is no way for us to do this as far as I am aware. What torrent client are you using? Some issues are the result of the torrent client as I've come to recently discover.

More specifically, if you're using Transmission 3.0, we have received a plethora of complaints that it is not working. If you are using Transmission, try rolling back to v2.94. I don't know why this makes a difference, but it apparently does.

Another thing that should be noted is that some users (especially ones who use NordVPN) need to use Google DNS to make things work. If you're using NordVPN, enable the custom DNS setting and use 8.8.8.8 and 8.8.4.4 as your DNS servers.

There are a lot of things that can cause this. Click on a torrent that is not working, then click on the "Trackers" tab. There should be an error message next to the tracker. It should give us more information about what the problem is.

Two things to note…. For users who are having issues with the CA Certificate for our SSL tracker, you can manually change the beginning of the announce URL in your torrent client. Change the beginning from:

https://tracker.gaytorrent.ru/

to

http://tracker.gaytorrent.tw:2710/

If you want to make this change permanent on all torrents moving forward, click the "Profile" tab at the top of the page, then disable the SSL tracker, and save the changes at the bottom of the page.
For users who are using NordVPN, it has come to my attention that it will only work consistently if you enable the Custom DNS setting and use the servers 8.8.8.8 and 8.8.4.4

These solutions should get you around most issues. If you are not using a VPN and the tracker change does not work, you may need to use a VPN to bypass the issue routing through to our tracker. I use PrivateVPN, as do a number of other staff, and it works GREAT with our system.