Your license successfully revalidated. Please log in.

[katycomputer]

Periodically, when I login to Blesta, it reports "Your license successfully revalidated. Please log in."

I then have to login again - is this really necessary?  It seems to be a needless aggravation. Additionally, I have a lifetime license, why is Blesta validating my license if it's perpetual?

[S.H.]

On 6/1/2019 at 4:03 PM, katycomputer said:

Periodically, when I login to Blesta, it reports "Your license successfully revalidated. Please log in."

I then have to login again - is this really necessary?  It seems to be a needless aggravation. Additionally, I have a lifetime license, why is Blesta validating my license if it's perpetual?

Yea this annoys me as well. Especially annoying to login a second time when using a phone.

[Tyson]

Do you have a cron job setup to run all tasks automatically? The system will attempt to revalidate the license by cron, but if it hasn't done so in a while it will also do it when you log in. It also checks other license information like companies and whether the license has changed, which needs to occur periodically regardless of license type.

[S.H.]

4 hours ago, Tyson said:

Do you have a cron job setup to run all tasks automatically? The system will attempt to revalidate the license by cron, but if it hasn't done so in a while it will also do it when you log in. It also checks other license information like companies and whether the license has changed, which needs to occur periodically regardless of license type.

Can you provide more details as to where and how to set this up? I do have a Blesta cron job scheduled to run every 5 mins but I have never seen an option for revalidating license in any of the automation settings within Blesta.

[Tyson]

The license check occurs automatically apart of cron without setup on your part. So long as you have the cron job setup to run all tasks (i.e. the command "/path/to/blesta/index.php cron"), the license check will run too. If you encounter a license check on log in, it's because the license data in your system is old. I'm not aware of an issue with this behavior, but I can take a look to see if the license check can fail to run automatically which may account for why it does it on log in for you.

[Amit Kumar Mishra]

or if you have got a ip dual stack then this may be a case

so you need to let blesta know your ipv6 in your blesta.com portal, and then things may be fine

actually you need to open a support ticket with blesta to add your ipv6 ahead of your ipv4

and the issue would be resolved

[katycomputer]

My dashboard says "The system is in good health and appears to be operating normally.", invoices are going out as expected

What else do I need to check to verify that cron is properly configured to run all tasks?

[katycomputer]

We are IP4 only.

[Paul]

2 hours ago, katycomputer said:

My dashboard says "The system is in good health and appears to be operating normally.", invoices are going out as expected

What else do I need to check to verify that cron is properly configured to run all tasks?

Settings > System > Automation. When is the date/time for the last cron run? What version of Blesta are you running? Do you have a cron job set up to run the command shown on that page every 5 minutes?

[katycomputer]

/admin/settings/system/automation lists cron job: */5 * * * * /usr/local/bin/php -q /home/katycomputer/public_html/billing/index.php cron > /dev/null 2>&1

It last ran at Jun 06, 2019 9:35:02 AM.

[Paul]

SELECT * FROM `log_cron` WHERE `output` LIKE '%validate%';

Can you run this query on your database? Any results? If yes, interested in the start and end dates. This is the cron log that contains license validations, which should occur automatically as part of your normal cron run.

[katycomputer]

run_id;"event";"group";"output";"start_date";"end_date"
17;"1";"1558927201.5381";"Attempting to validate the license.
The license validation task has completed.";"2019-05-27 03:20:01";"2019-05-27 03:20:05"
17;"1";"1559013601.6674";"Attempting to validate the license.
The license validation task has completed.";"2019-05-28 03:20:01";"2019-05-28 03:20:05"
17;"1";"1559100002.2224";"Attempting to validate the license.
The license validation task has completed.";"2019-05-29 03:20:02";"2019-05-29 03:20:06"
17;"1";"1559186401.7753";"Attempting to validate the license.
The license validation task has completed.";"2019-05-30 03:20:01";"2019-05-30 03:20:05"
17;"1";"1559272802.4212";"Attempting to validate the license.
The license validation task has completed.";"2019-05-31 03:20:02";"2019-05-31 03:20:06"
17;"1";"1559359201.6427";"Attempting to validate the license.
The license validation task has completed.";"2019-06-01 03:20:01";"2019-06-01 03:20:05"
17;"1";"1559445601.5029";"Attempting to validate the license.
The license validation task has completed.";"2019-06-02 03:20:01";"2019-06-02 03:20:05"
17;"1";"1559532001.7817";"Attempting to validate the license.
The license validation task has completed.";"2019-06-03 03:20:01";"2019-06-03 03:20:05"
17;"1";"1559618402.1411";"Attempting to validate the license.
The license validation task has completed.";"2019-06-04 03:20:02";"2019-06-04 03:20:06"
17;"1";"1559704801.5296";"Attempting to validate the license.
The license validation task has completed.";"2019-06-05 03:20:01";"2019-06-05 03:20:05"
17;"1";"1559791201.9135";"Attempting to validate the license.
The license validation task has completed.";"2019-06-06 03:20:01";"2019-06-06 03:20:05"
 

[Paul]

Thanks. I see no reason why you should be logged out unless the hostname in your browser changed, or your IP changed, or the server path to your installed changed. Tyson is looking into this in more detail to see if it may be a bug.

[katycomputer]

OK, thanks. We haven't changed anything since early in 2018 when we changed the domain.

[Tyson]

I think we'll just need to keep an eye on this one for now. From my testing, the license validates successfully and updates the license data as expected, so there are no required license validations when logging in for me. There could be another use case that triggers it though.

[katycomputer]

OK, thanks. It's not the end of the world, just aggravating...

There are higher priorities, for example allowing us to make "save payment details" a default setting.

[Gigaion]

Just chiming in that I have this similar issue (Since I'd prefer it gets fixed also).
Cron is setup properly, although once in awhile I end up getting logged out for revalidation.
The SQL statement run above shows its revalidating once per day, so I believe Tyson is correct that something else seems to trigger forcing a re-validation.

 

[katycomputer]

Adding another urggh....

I log in, get a "Your license successfully revalidated. Please log in.", then I have to log in again.

First world problem, aggravating issue.

My primary concern: I have a lift-time license, why does Blesta need to revalidate. What if the Phillips boys win the lottery, does Blesta quit working?

[Amit Kumar Mishra]

3 hours ago, katycomputer said:

Adding another urggh....

I log in, get a "Your license successfully revalidated. Please log in.", then I have to log in again.

First world problem, aggravating issue.

My primary concern: I have a lift-time license, why does Blesta need to revalidate. What if the Phillips boys win the lottery, does Blesta quit working?

if @Paul wins lottery, i am sure blesta will become more robust, and may be even free...

[Tyson]

Blesta always needs to check you have a valid license. If you decide to sell it to someone else later, why should your copy of it continue working?

I don't play the lottery, but if I did, it wouldn't change anything. There may be more money to spend making it better though.