Posts made by MrMazda

Invites are reserved for power users only.

To become a power user you need:

• A ratio of at LEAST 1.04
• An upload total of at LEAST 40 GB
• To be a member for at LEAST 4 weeks

This is because you have a TERRIBLE upload speed and are only seeding ONE of your several uploads.

My two personal favourites….

https://www.gaytorrent.ru/details.php?id=2c2a8d46b7697991fe9be73a4968c887f02fa0f25ea8a6a2

https://www.gaytorrent.ru/details.php?id=6413fca4c8eb6bbcaab3af0fad85f63e24932bc27b886cf2

This topic has been moved to Requests - Porn.

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

Not that I'm aware of. I can save you half the work. Your torrent client reports that it is using port 11773

You need to make sure this port is forwarded from your router to your computer. The only resource I can think of for help would be www.portforward.com

This is what I get on a Samsung Galaxy A50 running Google Chrome and Android 10.

It does the same thing on my Alcatel tablet, but interestingly, on my tablet, when I rotate the screen 90° then rotate it back, the pictures don't overlap anymore.

It sounds like you do not have the correct port forwarding settings in place. You need to be sure that the port that your torrent client uses is forwarded through your home router or VPN to your computer, both in TCP and in UDP. This is a critical, yet often overlooked step needed to be able to get proper upload traffic.

@jacrobat:

I read the comment about NordVPN. I am a Nord user and cannot upload. Are the admins saying that Nord is specifically an issue for their DDOS counter measures and so people should move to another provider or that this is a temporary issue? Also, does this affect other VPN providers or just Nord?

More or less. There are some users who say they have had intermittent success with different workarounds for NordVPN, but the general consensus is that NordVPN will not work.

This topic has been moved to Requests - Porn.

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

On the most part, you can use most any VPN with our site. Some VPN's however such as NorVPN and PIA seem to have issues connecting to our site. I personally recommend using PrivateVPN, as that's what a number of our staff use, however the key to whatever VPN that you use is that it needs to support port forwarding for ALL ports. This is critical for getting proper upload traffic.

Scrape has never been supported by our tracker. It only affects your ability to see the peers pool if you are not actively downloading or seeding the torrent, and as such, is not necessary to be able to download or seed torrents.

Do you by any chance have other torrents seeding? If so, you may have torrent queuing enabled. Go to your settings, then go to Queuing and either uncheck the box to disable it, or change the maximum number of active torrents and the maximum number of active uploads to 999. This should resolve your issue.

This is something that can only be done by staff usually. If you have a link to the torrent and a specific reason for deleting the torrent, it may be possible to arrange this for you.

@libertyx:

Still the SSL Tracker isn't working for me.

In your case, I see that you are using Transmission 3.0… This may be where your problem lies. For some reason version 3.0 is very temperamental with our tracker for some reason. If you roll back to the previous version (2.94), you should have no issue with our tracker anymore.

@Douseikekkon:

I'd like to revert to SSL in my profile, to see if things get better with SSL checked, but I can't access this setting anymore due to the new interface :cry2:

Click your username in the top right corner, then click "Profile".

There are a few things to try to see where the issue may lie….

1. Try disabling the SSL tracker. You can do this permanently in your profile settings, or you can do it manually on any given torrent. To do this manually, change the beginning of the announce URL on the torrent. Specifically, change the following:

https://tracker.gaytorrent.ru/

to

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

2. Try using a VPN such as PrivateVPN to route around possible blocks that may be preventing you from connecting directly to the site through your home network.

3. Try making use of Google's DNS servers by changing your DNS settings to use 8.8.8.8 and 8.8.4.4

If this does not work, there may be other avenues to explore.

@Gincio:

Not sure if I have ever posted here before.

I've been a member for years.

In the last few months I have started seeing key loggers/malware in the m4m porn.

How do we get these trackers pulled and who ever is uploading these banned before anyone loses their life savings?

Thanks,

Usually by users clicking the "Report" button on these torrents. As regular users, you are not able to see much information with respect to user accounts, however staff can see a lot more. When we see this, we immediately pull those torrents from the site, and at the very least send the uploader a PM. For repeat offenders, we do things like remove their upload rights so that we have to review their uploads before they can go live, and in some cases, we have even banned users for this kind of thing.

It all gets managed on a case by case basis with each user respectively.

1. No… You should resume the download or seeding from where you left off. This will prevent you from getting charged double the download.

2. Yes... This is usually a sign that the file has been damaged.

3. Once the file goes to "Seeding", it is 100% complete, without flaw.

@srblock:

It is clean. I think I Like it, I'll give it a go. One thing is bothersome: in Browse view, when I mouseover "i" to see info, the popup box sometimes is very wide and goes off the left side of the page. This is only happening in Safari (which I prefer to use). It looks fine in Chrome. Also, under my profile I do not see an option to choose the old layout, although like I said I think I'll get used to the new layout. Nice work

This issue should now be fixed.

UPDATE: Apparently, there was an underlying issue with the SSL certificate for which we were not aware, which has been fixed. This should mean that Transmission 3.0 among a number of other clients should now work again.