ironsoul posted at 2:46PM Sat, 23 December 2017 - #4320803

torqy posted at 5:14AM Fri, 22 December 2017 - #4316735

I would like to add my own additional plea to get this problem fixed. Tao's software fills a very important need for those of us who purchase a large number of Renderosity products. Downloading individual product .zip files may not be so onerous for those who only purchase a handful of items here or there, but my Renderosity account's Purchases page shows 328 orders that I would need to slog through to download my purchased items. Tao's software helps buyers like me keep coming back to buy more, which should be important enough to Renderosity management to free up a bit of debug time in the development team.

I can provide some additional details that may help the developers narrow this down. The change to the web site occurred on or around August 30, so they should be able to check their change logs to determine what relevant changes were made at that time. Tao's program throws the following error message:

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream. at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocoIRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocoIRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocoIRequest asyncRequest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResuIt) at System.Threading.ExecutionContext.run TryCode(Object userData) at System.Runtime.CompiIerServices.RuntimeHeIpers.ExecuteCodeWithGuaranteed Cleanup(TryCode code, CleanupCode backoutCode, Object userData) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCaIIback callback, Object state) at System.Net.TIsStream.ProcessAuthentication(LazyAsyncResuIt result) at System.Net.TIsStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.ConnectStream.WriteHeaders(Boolean async) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.GetResponse() at ?.?(String pageUrI)

Does your system support TLS 1.2?

I've been looking into this, and though the app is written in NET 3.5 for backward compatibility and therefore currently does not support TLS 1.2 (I's possible to make a workaround for that if necessary), this does not seem to be the problem. I've tried to upgrade it to NET 4.6.1 which does support TLS 1.2 but it's still being denied access.

My impression from what Renderosity have said here is that they have blocked it intentionally. The fact that it was working perfectly all the time during the 2 years of development and testing and then suddenly was denied access 2 days after it became publicly available also points in that direction.