@MrMazda:

Two things to note…. For users who are having issues with the CA Certificate ... <snip>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.</snip>

Thanks MrMazda, I appreciate your help!

While I use NetShade, and not NordVPN, I will try those specific DNS values to see if they help.

Since Transmission hasn't specifically given any errors about the CA Certificate and I agree with @pjh1122 about staying as secure as possible, I'll try that first. I will inform of my results up here.

Some  additional updates:

1. Previously-downloaded .torrent files are no longer working. I believe they were only working before because the same members were in the swarm as when the last successful announce occurred. Simplified - the previous IPs are now gone and I can't connect to the Tracker to find out the new ones.
2. I have raised this issue with the site Helpdesk and also pointed them to this thread. I am hopeful that the Admins will provide some answers.
3. Can anyone tell me what VPNs are still working as of now? While I'm not thrilled with the idea, I might consider using a different VPN on another computer. Though I realize that is not an option for most people. (Didn't gt.ru have a VPN of their own at some point? I cannot seem to find anything about it now.)

Any and all help is  appreciated!!

A little more information:

1. To see if the issue was IP-specific, I tried a NetShade server in the UK. No change in the issue. (And that's a completely different IP!)
2. Other torrent trackers are working fine and have no new issues; so I don't think it's a problem with the Transmission update.
3. .torrent files previously downloaded (before today) appear to be functioning okay. I see data being up- and down-loaded, even though Transmission reports it cannot connect to the Tracker. This applies to both seeding and leeching torrents.

Any help is appreciated!!

Just since around Noon today (May 30) Eastern Daylight Time, I am having an issue connecting to the Tracker. My current IP through my VPN is 64.62.244.51.

Is this IP now being blocked by the DDOS protection? It is one of the servers used by Netshade, which is a widely-used Macintosh VPN.

They have several servers but this particular one seems to normally work best for me. I have tried one of their others (with a similar IP, only the last node changed). But I am still having the same issue: Transmission 3.00 (f4489c982e) reports:
Announce error: Could not connect to tracker - Today at 6:48 PM

I've used NetShade for several years now. And since I have already paid for a full year's subscription, it would be very inconvenient to switch VPN providers.

I'd appreciate any help or suggestions. Thanks!!

One other question…

I noticed that the minimum freeleech period (when it appears) has been changed from 3 hours to 24 hours. I guess the idea is to reduce the 'hit-n-run' effect. Is there some chance of putting in a shorter minimum? Perhaps 12 hours would be a good medium?

Thanks!

I have a question about making torrents freeleech by 'spending' my points: I understand there is a 48-hour delay on new torrents before they can be made freeleech but I'm seeing torrents that are well older (four days or more) than that without the option appearing. Are there other criteria that control this? If so, what are they?

I'd just like to understand how the process works. Thanks!