I ran across this issue today, and you may run across it yourself over time. Disabling two factor authentication in WHMCS can be tricky if you don’t actually have access to the account, device, or admin side to take care of this. Personally, I feel WHMCS should handle this better, but that’s just my own opinion. Each is very well welcome to their own.
WHMCS has made the decision to force users to update to php 5.6 in order to receive updates in the future. While good, there are indeed WHMCS mail problems in php 5.6.
To be fair, the problems aren’t WHMCS problems directly, but they COULD be avoided by not forcing users to update to a version of php which is riddled with a pretty major hole.
At one time, WHMCS and SSL played nice. All you had to do was add your ‘WHMCS system URL’ (in admin -> settings) to https://yourdomain.com. Unfortunately, somewhere along the line in v6, WHMCS and SSL stopped playing nice. Here’s a guide serving WHMCS 100% over SSL in v6, with no errors or redirect issues.
So, you’ve managed to get WHMCS installed and updated. You’ve been working with it for a while, but you decided hey, you don’t like the URL it’s at. Here’s how to go about changing the WHMCS URL (ie: where your clients go to your WHMCS). Some of this is basic, some, not so much
So, we covered the upgrade yesterday. Yet, far too often, we run into WHMCS upgrades gone wrong. Something is messy, or something just doesn’t work as expected, or, well, it just doesn’t work like you need. How to fix it? How to revert things? There’s a few things that can be done for WHMCS upgrades gone wrong. If all else fails, hey, please do contact us, and we’ll work with you and see what we can do to help you get straightened out!
Upgrading WHMCS can be kind of tricky, especially when you’re going from major release to major release (ie: 5 to 6). There’s a pretty good chance that something’s gone missing, or something’s going to break. Even worse, it’s entirely possible that there’s bugs that the WHMCS team, and their testing didn’t catch. So, what to do? How to ensure a somewhat trouble free upgrade?
If you’ve been around the Windows world long enough, you know what the BSOD is. It’s nasty, it’s ugly, and even though Microsoft claims to have gotten rid of it, it still exists in a very different way. I bet you didn’t know, however, that there is such a thing as the WSOD (white screen of death) that is referred to by php developers and users alike. How can one figure out these errors? With WHMCS, this can be kind of complicated, but that’s what the point of this is, helping you get past these issues.
WHMCS, being the complicated beast that it is can be somewhat tricky to work with. Some tips and tricks to at least try to identify and mitigate the problem in here. If you’re still seeing issues after trying these, or your problem isn’t covered here, please do contact us! We’re absolutely here to help you work through the problem you’re having.