Jump to content

Moc

Member
  • Posts

    51
  • Joined

  • Last visited

About Moc

Moc's Achievements

Member

Member (2/3)

0

Reputation

  1. I agree with expecting a stable release, but does that mean that you don't even need to backup before upgrading? A simple quick-backup on the WHMCS installation would have saved a lot of this trouble. Yes one would maybe lose max. 24 hours of changes but those consequences shouldn't weigh up to the struggle people are dealing with now. Yes you are relying on WHMCS, but that is what you chose for. If you don't want to rely on others, build your own system. I know it isn't that simple, but if you look at it rationally, that's just the way it is.
  2. You've made your point, you've vented plenty, now sit back and wait till things get back in order. Obviously there is something going on but I'm sure you can spend your valuable time much better on getting things sorted within your hosting business rather than venting here. I agree, there is no excuse for the (huge) delay in support and the annoying and critical bugs in 5.1.2, though I believe that it should come from both ways. Testing, backing up, and again testing before upgrading. There are obvious problems in the management of the software and the support desk but posting like crazy here and 'attacking' other members is not going to solve that.
  3. 5.0.3 is working correctly here without any real bugs or issues. Not trying 5.1.2 until things get sorted out though
  4. Try and clear your cookies and log back in. Might want to test with another browser as well.
  5. Updating requests put you back in the queue. WHMCS support team works on last-reply basis, meaning the tickets that received a reply the longest time ago will be the first to get a reply back. There may be exceptions obviously but this is their regular process as far as I know.
  6. I agree on that last paragraph. As for the rest I'd like to refer to a reply made by 'Matt R' (not WHMCS matt related) on WHT.com: Anyhow, I'm awaiting more updates before posting more replies here
  7. Do you actually think it is as simple as restoring a backup? For all they know there is a rootkit installed which still controls the server. It first needs thorough checking, securing the box (possibly replacing the entire box to be sure), then loading up of the static files, etc etc. It is NEVER as simple to recover from a hack as just restoring a backup. I said it was physically impossible to send a mass mail right when they were hacked as the infrastructure wasn't recovered (yet).
  8. Probably because their initial priority was to get the boxes secure, then re-upload the website to be able to get some things functioning again which might include emailing. Don't underestimate the damage that has been done to both the physical and the online 'infrastructure'. At the time they are hacked, there is no way of retrieving the email addresses of all clients to send out an email, its physically impossible so to speak.
  9. Just look at the updates Matt is giving, it actually is quite frequent and informative. I've seen far worse.
  10. I find it highly unlikely that vbulletin lies at the root of the security breach, nonetheless it is one of the security measures. Note that the forum could have been patched with the latest fixes, just the version number that remains outdated. Give Matt and his team some time and resources (in terms of not whining at him) to get this sorted out. Obviously there is a risk that personal information has been compromised, act pro-actively and get yourself secured.
  11. Honestly, welcome to the internet. If security wasn't tough, why would it be called 'security' then? I understand the frustration but instead of whining here, get yourself secured in terms of passwords and any other information that might have been gathered by them.
  12. Regardless of the database being leaked or not, change all passwords that WHMCS may have or may have had. That includes securing credit card details, possibly contacting your bank and alerting them of possible fraud or just cancel and re-issue anyway. Be pro-active, not reactive.
  13. Waiting for what? If you had actually clicked on the link I posted above, you would have read this:
  14. This might help: http://docs.whmcs.com/Common_Troubleshooting_Tips#Down_for_Maintenance_-_An_upgrade_is_currently_in_progress
  15. Did you open a support ticket to get the fixed files?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated