WHMCS Statement for db error?

[Bubka3]

Will WHMCS be releasing a statement on why your database was down? My license was only invalid during that period...

 

Happened around 12:20AM today, EST.

Edited October 18, 2012 by Bubka3

[disgruntled]

if your installation was not accessible then this suggests a licensing issue with your local key, the way the system works is that your license is verified at set intervals, if the licensing server is down at this check then your installation stays alive because your local key allows this, if your system went down because the license server was down then your local key has been broken some how or the license server was down for an extended period of time, in which case everybody would have had problems and as i myself didnt notice anything i can only suspect this want the case.

[Sue611]

I have the same problem right now never had it before and the key hasn't expired. When I go to my login page I get the following message: License Noconnection - WHMCS has not been able to verify your license for the last few days.

 

It hasn't been a few days it has been the last 12 hours.

 

Maybe some people haven't yet realised there system isn't down I don't know.

[Bubka3]

....

I know how licensing works, the local key hasn't updated in a few days, and it just so happened that when it wanted to update, WHMCS databases were down. Still no confirmation from WHMCS. Just sweeping it under the rug, again...

[bear]

I've yet to see my owned installs go down because of anything here on WHMCS being down. Either I'm just lucky, or my local key works as expected.

 

As for them owing anyone an explanation, I'm not so sure that's exactly mandatory unless it was something serious affecting data integrity or security. Sure, information would be appreciated (mainly to rule out the above considerations), but I'm not sure disclosure of every burp in a system is warranted.

Just me, maybe.

 

Just sweeping it under the rug

To do that would require deleting all mentions, I'd suggest. Haven't seen that.

[disgruntled]

I think in the case of a licensing server issue it is better to forewarn, but to be fair i would only warn myself if say more than 1 - 2% of the clients are going to be affected by an issue that is ongoing, if i was expecting to resolve the issue before more clients were affected i wouldnt feel the need to do so.

 

That said, a notice section on the forum and in the client area might be useful, post up a notice while the problem is ongoing, remove it once its resolved, it might at least put some minds at rest with an acknowledgement from the staff at whmcs there is an issue and its being worked on.

 

Far better than wondering and thinking the worst i would say.

 

 

From my business point of view personally, if i have to do any form of maintainance i inform all clients whether i think there will be any problem for the client or not. thats just me covering my own backside obviously. forewarned leads to less complaints.

[disgruntled]

I know how licensing works

 

I wasnt suggesting otherwise just clarifying in case you didnt, besides anybody reading this who didnt know, now does. We cant begin to presume everybody knows everything its thinking like that which causes people to get in a mess because it was presumed they knew what they were doing, never presume. i dont, i always assume they dont.