mss.ERROR: key-validation.failed

Hi there @everade,

Thanks for reaching out!

It’s expected to see errors related to Premium check when using a free plan. Do you see any other issues with how the MailPoet plugin works on your site?

Cheers!

Hey Elvira.

The definition of an error is that something went wrong.
I don’t understand why it would generate an error just because i’m using the free version.

This shouldn’t generate an error. It just bloats my error logs with a behavior you claim to be normal. If it’s normal, then it should not generate an error.

But yes, i have issues that consecutive mails aren’t sent, but i’ve opened another support topic for that but i’ve not recieved proper support in 6 months.

Still getting hundreds of errors per week filling up my logs for no apparent reason.

Hi there!

Thank you for your answer

When accessing the MailPoet “Home” menu section in WordPress, it generates the following error:

I don’t see any logs section on the Mailpoet Home page on my website. Can you please tell me where you see this logs page? Can you please send us a screenshot of the entire page?

But yes, i have issues that consecutive mails aren’t sent, but i’ve opened another support topic for that but i’ve not recieved proper support in 6 months.

Can you please add the link to the support topic where you haven’t received an answer for 6 months?

First and foremost. No…
I’m not re-posting a screenshot i’ve already posted.
And secondly, no i’m also not going to tell the MailPoet support where the MailPoet Logs are. I said the errors are generated when visiting the MailPoet Home section. Not that the MailPoet Logs are to be found there.

And third, no, i’m for sure not showing you the link to the other support case if you’re not even capable of this.

What a waste of time.

Hey @everade,

Apologies for the misunderstanding above. Let’s try to figure out what is going on with the generated error logs, and thanks for giving clues on what is going on.

I see from the screenshot you shared in your first message that the “key_type” is checking if you have MailPoet Premium.

The Starter plan doesn’t give you access to the Premium features of the MailPoet plugin, including access to the Premium plugin.
?
But you should still send out your emails, create newsletters, etc. successfully. It seems like this is your case.

We have seen situations where modifying the wp-config.php file fixed the error. But again, if sending emails is working, you can just ignore the logs.

In case it’s working, but you still want to get rid of the logs, you can work on the wp-config.php file with your hosting provider to ensure the URLs for the site and the ones triggering the cron tasks are all returning the same one that the MailPoet license key is activated on.

Alternatively, you could set up a Linux Cron job and switch MailPoet to use the Linux Cron option for the task scheduler as described in our guide below, which we’ve seen solves this issue with the license check task:
https://kb.mailpoet.com/article/257-setting-the-server-side-cron-linux-cron.

Thanks again for using MailPoet & let us know if you have any further questions!

Just seems weird to me that instead of MailPoet devs actually going ahead and removing or fixing that error condition, now me the user is supposed to do a workaround just so my logs don’t fill up with an unnecessary error message which supposedly isn’t even an error.

I’m already running a linux cron, yet the errors are still being generated. Keep in mind that this is a MailPoet error, generated by MailPoet, logged into the MailPoet logs.
Please also note that these errors are generated when navigating throughout the MailPoet plugin. Validate your Activation Key? Error logged (despite displaying YOUR KEY IS VALID). Do nothing? Error logged. So basically all the time. Just every time MailPoet checks the activation key for whatever reason, it logs an error, despite having a valid Key entered. This doesn’t seem to be related to the Cron at all.
It’s just MailPoet which runs a key-validation all the time when using MailPoet, then triggering an error for no apparent reason. So i’m not sure how editing the wp-config file is supposed to remove an error condition that’s been coded into the plugin source code. Doesn’t make any sense to me at least.

The home-url in that error looks correct to me by the way (it’s simply my base URL such as https://redacted.sdf ) So i’m not sure why the key-validation is failing when in my Key Activation settings the Key is valid. I don’t have premium, never used premium, i use the free version, so the key entered is a free key, and i use free features only.

Any explanation or hopefully a fix?

• This reply was modified 11 months, 1 week ago by everade.
• This reply was modified 11 months, 1 week ago by everade.
• This reply was modified 11 months, 1 week ago by everade.
• This reply was modified 11 months, 1 week ago by everade.
• This reply was modified 11 months, 1 week ago by everade.

Hi there @everade,

Thanks for continuing to reach out on this issue.

I have run some tests on my test site with a Starter (i.e. free) license code, and I’m not seeing the same behaviour. I see the same error message about the key failing validation *only* when I actually validate the license – that is, under the Settings > Key Activation tab, when I click “Verify”. This re-runs the verification and adds that failure message to my logs.

I tested re-loading the MailPoet home page multiple times, and I also sent out some sample newsletters and none of that basic functionality triggered the addition of the error message to the logs. I was testing with the latest MailPoet which is 4.40.0.

So, if you are seeing that error message added to your logs hundreds of times a day, it would seem that something unusual is going on and that is not typical MailPoet behaviour.

Is this a recent change in your log file activity? Can you look back in your logs to see if the flood of error messages started happening on a specific date, and if so, were there any major changes to the site at that time?

Also, can you explain a bit more about what you are doing to trigger the error – does it happen when you send out an email? If so, how big is your distribution list? Or does it happen just when working within the plugin in any way?

Lastly, can you confirm which free plan you are using at MailPoet – is it our Starter plan, or do you have a legacy plan that you use?

Thanks!

Still get the error at least once daily.
Could this please finally be forwarded to the plugin dev team so they can fix it? You even confirmed the error yourself so i don’t understand why we need to pull this any further.

It doesn’t matter which plan i have, i have a valid plan, so an ERROR should not be triggered. https://dictionary.cambridge.org/dictionary/learner-english/error

Thank your for your understanding.

Hi there!

Still get?the error?at least once daily.
Could this please finally be?forwarded to the plugin dev team?so they can?fix it?

We’re happy to investigate further and report to the developers if required, but we will need the details we requested.

For further troubleshooting, please get back to us with:

1. Screenshot of the error (the original image you shared is no longer accessible)
2. Is this a recent change in your log file activity? Can you look back in your logs to see if the flood of error messages started happening on a specific date, and if so, were there any major changes to the site at that time?
3. Also, can you explain a bit more about what you are doing to trigger the error – does it happen when you send out an email? If so, how big is your distribution list? Or does it happen just when working within the plugin in any way?
4. Can you confirm which free plan you are using at MailPoet – is it our Starter plan, or do you have a legacy plan that you use?
5. Finally, share MailPoet System information:
   • A screenshot of the MailPoet > Help > System Status page. Please ensure to capture the whole page or make several screenshots.
   • Copy and paste the information from MailPoet > Help > System Info.

Looking forward to hearing from you.

1.) You’ve confirmed it.
2.) You’ve confirmed it.
3.) You’ve confirmed it
4.) You’ve confirmed it
5.) You’ve confirmed it

How to reproduce:
Get a free MailPoet license. Install MailPoet. Your log gets at least 1 error per day.

How is this error generated?
Every time MailPoet runs a license validation check. This happens when you click the verification button. And also automatically DAILY. Most likely also during other occasions. I haven’t looked into the source code of MailPoet just yet, but it’s most likely a single function which is called during multiple occasions.

Why does this happen?
Because inside the MailPoet Source Code (most likely a function), there’s a case in which it generates an Error even when having a valid free license, as it only checks for a paid subscription plan. This function must be fixed.

How to fix it?
The MailPoet support team must forward error reports to their MailPoet dev team. So the MailPoet dev team can fix their function.

Has it been confirmed?
YES. One MailPoet supporter has confirmed the error to be in their logs.

Has it been forwarded to the dev team?
For some unknown reason, NO. The MailPoet support team are still asking the same questions, and stealing everyones precious time.

Hi there @everade,

I have forwarded your issue to our development team to take a look. We will update you with their feedback.

Hi again @everade,

Just wanted to confirm here that our development team acknowledges that this is a message that should not be reported as an error in the logs.

They have raised a bug report to remove this message. At the moment there is no fixed ETA for this change and it has a medium priority level.

Please continue to watch the release notes for upcoming releases of MailPoet for the fix.

Thanks for bringing this to our attention!

Thank you very much @lynnjat7 for forwarding it.
Much appreciated.
Have a nice day.

Happy we were (finally) able to help! I’ll go ahead and mark this thread as resolved for now as our policy is not to keep threads open when there is an open bug report instead. I’d recommend keeping an eye on future release notes to note when this issue is resolved.

In the meantime, happy mailing!