Mailpoet tells me my key is invalid even though it isn’t

I have the same problem! It is so frustrating! It would be nice if MailPoet actually responded to these. I posted about this same thing a few weeks ago and never heard anything.

Yes this is the second time I have posted. It’s more than frustrating. If I am unable to check the site every day there is a chance automatic posts will not be sent.

That’s exactly what’s happened to me. I find it annoying that I have to login every day to make sure my emails go out. Are you a paying or free user? I’m on the free plan, and the lack of support is very discouraging. I’m about to use a different service even if I have to pay for it.

I am on the free service. We are a not for profit organisation with only 35 members, we cannot justify a paid plan.

I know what you mean. I looked into other services, but the cost didn’t seem worth it. But I’m getting to the point where paying for reliability and convenience might be worth it.

??

Just got this from MailPoet, so I thought I would share it:

MailPoet from time to time rechecks your license. I think what’s happening is that when this action happens, your website can’t successfully connect to MailPoet’s website (bridge.mailpoet.com) to verify your license, so the plugin checks it invalid.

Try to contact your host support to look for any sort of connection issues between your website and MailPoet’s website (bridge.mailpoet.com).

Additionally, try to check your MailPoet’s Help page for any connection issues.

Thanks for the information Mark.

Does it use the same process when the key is verified using the link on the settings, key activation page? If so, I do not understand why that always works, no exception.

I’ll contact my host about the possible connection issue.

Thanks again.

Ian

Yeah, I’m not sure about that either. I also assume that other plugins do something similar, and I don’t have problems with any of my other plugins.

I just got done chatting with my host, and they said there’s no problem. I wrote MailPoet back and told them it wasn’t a connection issue, so we’ll see what they say.

Thanks.

Not sure if your issue has been resolved yet (mine hasn’t). Support said, “I believe the issue could be happening because you have both www and non www version of your website active. But for the key check, we allow only one domain.” They told me to check that I had a redirect in place pointing to the domain registered with the MailPoet key. The redirect was in place, and it worked with no problems. So, they’ve sent my problem off to their dev team.

Thanks.

I’ve checked my site (again) and all routes redirect to wayfarerschorus.com, so it looks like it is the same problem as you are having.

Look forward to some news.

Ian

This is the response I got from the dev support. I set up the server side cron job a few minutes ago, so only time will tell if this works.

Thank you for the issue report. I definitely understand how frustrating it must be having to revalidate the API keys multiple times every week.

I’ve taken a look at your site and I think I see the issue.

Even though your domain normally is https://www.markthegreenvan.com, and it’s known that way to you and your visitors,
your hosting company has also assigned a different site URL to the site as well: https://markthegreenvan.com.dream.website/
They use it to make sure any scheduled tasks are successfully run (e.g. thumbnail generation).

However, MailPoet uses the current site URL to check whether it is still associated with your API key.
So if the check happens when https://www.markthegreenvan.com is the site URL – the API key is considered valid.
However, if the check occurs while the site URL is changed to markthegreenvan.com.dream.website/ – MailPoet will not consider the API key as valid.

Could you please switch to the Server side cron option in MailPoet?
This article describes the necessary steps to take: https://kb.mailpoet.com/article/257-setting-the-server-side-cron-linux-cron
We believe doing so should help avoid API key invalidation.

This is the response I got from the dev support. I set up the server-side cron a few minutes ago, so only time will tell if works.

Thank you for the issue report. I definitely understand how frustrating it must be having to revalidate the API keys multiple times every week.

I’ve taken a look at your site and I think I see the issue.

Even though your domain normally is https://www.markthegreenvan.com, and it’s known that way to you and your visitors,
your hosting company has also assigned a different site URL to the site as well: https://markthegreenvan.com.dream.website/
They use it to make sure any scheduled tasks are successfully run (e.g. thumbnail generation).

However, MailPoet uses the current site URL to check whether it is still associated with your API key.
So if the check happens when https://www.markthegreenvan.com is the site URL – the API key is considered valid.
However, if the check occurs while the site URL is changed to markthegreenvan.com.dream.website/ – MailPoet will not consider the API key as valid.

Could you please switch to the Server side cron option in MailPoet?
This article describes the necessary steps to take: https://kb.mailpoet.com/article/257-setting-the-server-side-cron-linux-cron
We believe doing so should help avoid API key invalidation.

Thanks Mark, I will try that. It is happening almost every day, so shouldn’t take long to work out whether the change fixes it.

Ian