Revocation server issues Windows 11 / 2022.33910

Not sure if this is a bug, but posting it for search engines and future users.

Until recently, I’ve never been able to activate using the login and had sporadic issues deactivating my license to move between computers.

The error I was getting was:

Error fetching data. Check network connection

I checked the Windows firewall and used Window’s TCPView64 to validate that TouchDesigner could talk to the Derivative servers. In TCPView64, I could see a long running HTTP port connection and very brief HTTPs connections to the same remote IP when I tried to login or deactivate.

I double checked firewall logs by enabling auditing of failed connections:

auditpol /set /subcategory:"Filtering Platform Connection"  /success:disable /failure:enable

(don’t forget to turn off the above as it can generate a lot of logs)

Running eventvwr.msc I didn’t see any outbound disabled firewall logs in the security log, but I did find this in the system log:

Searching for Event 36876, Schannel didn’t return any thing useful. Searching online for error code 0x80092013 I found the error was related to the certificate revocation function. So, I converted the derivative.ca server cert attached in the log from hex to binary .der file and inspected it. This was a whole ordeal involving some command line ASCII hex to binary conversion. I installed the certificate and the rest of the chain which involved going to Amazon. Within the original cert, I found the CRL distribution point.

(Can’t post the image due to new user image restrictions)

Using the Amazon CRL Distribution Point address, I found the .crl file and imported it. That ultimately fixed the issue. In hindsight, I’m not sure if I really needed to import the Derivative and two Amazon certs, but I had already installed them once I got to this step. So, you may be able to fix this issue simply by downloading and importing the CRL file.

Cheers, and I hope this helps anyone with the same issue. On the Derivative side, a more descriptive error message would be helpful.

Thanks for your report. We haven’t heard of any issues like this before so its curious you have having these problems to begin with. I’ll send your notes to our web team for review.

Thank you, Ben. Issue was encountered on two different machines both Windows 11. One is a laptop from Asus and the other home built. I normally run the Windows firewall with a default block. I did debug with the firewall completely off which made no difference. But, maybe it’s possible that on a fresh install it’s an issue related to trying to use Touch Designer with a firewall on initially and attempting to contact the TD license servers prior to adding TD to the firewall putting TD or Windows into some weird state.