Re: 12 Hours downtime

One thing this revealed:
vBSEO down for 12 hours

Is that the activation/registration code in the code uses PHP to connect to the vbseo.com server and check registration status.

I'm sure it must cache this, but something very foul happened when the vbseo.com server was down... my site ground to a halt! Every request taking between 4 and 10 seconds to serve!

Frankly, this is absolutely unacceptable.

Sure you have a right to check for the registration status of your code, but you have written in a "feature" that means that the performance of our site is now bound to the availability and performance of your site.

Could you not have included the license check within the admin/configuration screens? That way the front end website doesn't suffer when your server, dns or site has problems. This is the way vBulletin does it... and it makes sense!

Even in the worst case scenario of your server being destroyed... all of the sites that have licensed your software should not suffer!

I am having terrible server issues these days which even forced me to purchase a dedicated server but vbseo's crash never effected my site. But in the other hand it happened to some clients. It doesn't look good and i know if it happened to me i would be pissed. Maybe we all need to find a better way for this.

There was another thread here which covered this, basically your site will only contact the vbseo servers if it's tagged as "Unregistered" (ie you see that in your Copyright footer).

As of 2.2.x we implemented the 'unregistered' notice (in the copyright text) to expressly show a user the fact that vBSEO is attempting to contact our server.

When I checked your instance this morning, it was displaying the 'unregistered' notice by the footer... This means that your datastore was cleared and hence your instance started attempting to get a license from our server while we were down.

This is a very important issue, something that I take very seriously. 2.3.3 is due out for release shortly - - we will look into a definitive solution to prevent this from happening again.

I will close this thread now and get back to everyone with an update either by re-opening it or via the release announcement for 2.3.3.

Juan