I actually used to do the same, autocomplete just generated renderosity.com instead because that's what I used in the beginning. Looks like clearing the cache and then type www.renderosity.com it will just generate that instead in the future, so that's OK.

Maybe the change is intentional, it's said that it's bad for SEO to use both, but people usually expect URLs to work without www so it may be a bad idea in that respect. Looks though as if a redirect can solve the problem:

http://www.themezilla.com/should-you-use-www-in-your-url-or-not/

https://ithemes.com/2017/01/09/www-in-url-domain/

I used to type renderosity.com which is the simplest of all, but that doesn't work anymore.

Jules53757 posted at 11:38PM Wed, 30 May 2018 - #4330824

I'm sure this is not a problem of Renderosity, I usually start to Rendo from my list of most used sites (in Firefox) and that link is https://www.renderosity.com. I visit the site more than once a day and during the last weeks I had no problems to reach the site. So, just one question, what browser do you use? Did you try to delete the browser cache?

https://www.renderosity.com works yes, but not https://renderosity.com - both FireFox and Chrome times out: "This site can’t be reached renderosity.com took too long to respond."

This started a week ago or so (there was even a thread in the DAZ forum about it).

thaaksma posted at 10:06PM Thu, 17 May 2018 - #4330223

The promotions we run on the site, and their respective start and end times, correspond with the time that's expressed beneath the Renderosity logo at the top-left of every page of our site. If there is confusion as to when a promotion ends, I might suggest that you reference the respective end time with the current time on the site.

Hope this helps.

-Tim

Yes I understand that now but it took some research to figure out the confusing AM/PM time format. Today most of the world is using the much simpler 24 hour ISO 8601 format which is recommended by the International Organization for Standardization.

Mik239 posted at 9:21AM Thu, 17 May 2018 - #4330211

Because 'pm' starts with 12:00pm, 11:59am + 1 = 12:00pm, 11:59pm + 1 = 12:00am

https://en.wikipedia.org/wiki/12-hour_clock

Yes I understand that now, but it would be more logical and less confusing if it was expressed as 00:00am to 11:59am, and then 00:00pm to 11.59pm.

Well been looking into this and that 12 hours AM/PM format is illogical and very confusing. The 24 hour standard ISO format (2018-05-14 15:22:34) on the contrary is logical, simple to understand, cannot be misinterpreted and a 100 times easier to work with in programming.

https://www.reddit.com/r/AskReddit/comments/32bgkb/why_doesnt_the_civillian_world_use_24_hour_time/

thaaksma posted at 8:31AM Thu, 17 May 2018 - #4330166

This promotion expired at 12:00pm (cdt) on Monday, May 14th. That's 6 hours and 47 minutes prior to your referenced 6:47pm (cdt) time. You're correct that the promotion was no longer running at 6:47pm (cdt).

-Tim

How can 12:00pm come before 6:47pm?

thaaksma posted at 8:17PM Wed, 16 May 2018 - #4330157

I just double-checked the sales calendar and it does say 12pm (noon).

Yes, but the sale was already closed at May 14, 6:47pm CDT, according to the clock on top of this page.

I'm not complaining about the sale, but there's something here that doesn't make sense.

taoz posted at 6:45PM Tue, 15 May 2018 - #4330072

-renapd- posted at 11:54AM Tue, 15 May 2018 - #4330066

12:00pm (cdt) means noon Central Daytime - same as server time! In fact, Grab Bag stayed open for an hour and a half longer than it should! :)

Rena

Well the date on top of the page here said differently when I started the thread - it said something like Mon, May 14, 6:47 PM CDT which is several times before the Grab Bag expiration at 12:00 PM CDT. So something is out of sync here.

I meant hours, not times...

-renapd- posted at 11:54AM Tue, 15 May 2018 - #4330066

12:00pm (cdt) means noon Central Daytime - same as server time! In fact, Grab Bag stayed open for an hour and a half longer than it should! :)

Rena

Well the date on top of the page here said differently when I started the thread - it said something like Mon, May 14, 6:47 PM CDT which is several times before the Grab Bag expiration at 12:00 PM CDT. So something is out of sync here.

Jules53757 posted at 4:07PM Wed, 18 April 2018 - #4328514

taoz posted at 10:30AM Wed, 18 April 2018 - #4328475

Vendor search doesn't work, no matter what names I enter it either returns nothing or give a HTTP 500 error, and the old drop-down vendor list is gone, so currently no easy way to find a particular vendor's store.

No idea what you are doing, the vendor search works fine, I tested it with several vendor names, all works well.

Yes it's working now I can see, just couldn't find anything yesterday, trying several names. Maybe a temporary glitch?

Vendor search doesn't work, no matter what names I enter it either returns nothing or give a HTTP 500 error, and the old drop-down vendor list is gone, so currently no easy way to find a particular vendor's store.

jennblake posted at 8:27PM Wed, 14 February 2018 - #4323820

Our programmer has agreed to work directly with Taoz and will be contacting him. He is finished with his current project and has some time to address this issue.

Thank you! Look forward to hearing from him...

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.

jennblake posted at 6:59AM Fri, 15 December 2017 - #4318683

Can you send me a link to the app? Let me see what it does and that would give me more information for the programmers...and then we might get further with this. jennblake@renderosity.com

Like others say, I already gave you the link to the official release, plus at your request I sent you a special version which didn't encrypt the data, to make it easier for you to see which data it was collecting.