Rapid Hosting - Hosting Domains Reseller cPanel PHP and MySQL specialists

There have been a few reports from clients that when attempting to log into their client area an error message appears “License Validation Failed” which prevents users from logging in.

This issue is intermittent but WHMCS are aware of the issue and are releasing a patch to fix the issue (which is soon to be resolved in version V4.1.

At this stage, if you do receive the error when attempting to log in, please be patient and try again shortly after. As soon as the patch is available we will aply it to the system and ensure all our WHMCS clients with keys from us have access to this file.

From Matt of WHMCS:

The license validation errors that some people have been experiencing in V4 are down to 2 seperate issues which I’ll try to explain here.

Firstly, there’s the cron. Some users have been experiencing a “License Validation Failed” response from this. This happens only on some setups and where it does, it’s due to the $_SERVER php environment variables not making available the server IP when a file is being run as a cron and therefore it’s deemed to be an invalid location. The IP validation was introduced in V4 due to the number of people who migrate their sites to different servers and leave the old installation’s cron job running which results in duplicate emails to clients and them being issued invoices and reminders for things which don’t exist in the current install. But unfortunately it’s caused trouble for more people than it solved and so will be removed again in 4.1.

Then there’s the client login issue. This is caused either by the domain being used not being authorized in which case intentional, but can also be caused due to the local key expiring which is an error and not something that should be showing to clients. It’s not anything to do with not being able to contact our server as there’s no remote license checks client side and fail overs in place for should our server be unreachable.

In our next release we will be including modifications to avoid both of these situations occuring. However, if you are being affected by either now, then you should contact support. If you are not experiencing either problem then you do not need to apply for patches nor make any changes.

Matt