HeleneL

Hello again Emre,

I really need your help as I am dispaired to get my website working again with WP fastest Cache

Here is the answer from my host (Fastcomet)

“we started installing the so-called EngineTron which is one of the best solutions for server-side caching. In order for EngineTron to be installed NginX which is indeed a web server should be installed as a proxy server. This means that your server is still Apache, however, the HTTP/S requests are being proxied by NginX and cached by the Enginetron tool. This of course is a good thing, this makes your server way, way faster than a normal Apache would be able to perform. More about Engintron you can find here:

-> https://engintron.com/

However, this tool usually does NOT create any issues in regard to caching plugins and so on and so forth. It is used to cache server-side actions as well as help cache website files, HTML, CSS, JS and so on, however, it does NOT overwrite in any way any caching plugin functionalities.”
An then they stop at that saying they cannot replicate the error, and there is something wrong with my browser or IP address (?!!), but I am being logged out of admin whatever the browser, my IP address has not changed over the last 10 months, I am on Fiber with French main teleconm company… and all problems stop if I deactivated WP fastest Cache, but I don’t want to deactivate it.

What can I do?

Please help!

Helene

Follow up on cache problems… You were just so right (and the coincidence is quite amazing too). My host just changed the server-side caching (engintron proxying my apache server to Nginx… here I am way beyond my understanding, just parroting what they said), which created the pb with WP fastest cache and with AI engine when WP fastest cache is enabled… well, this is probably THE opportunity to test your advice to handle cache server-side…
In any case thank you for your help, even though it had nothing to do with AI engine.
And you are right again with the initial bad (and not that cheap) US host, we have moved to VPS and not that cheap either host… ??

• This reply was modified 1 year, 9 months ago by HeleneL.

Ok, Thank you Emre, my host must have set it up without telling me (that is helpful indeed!)… I’ll check with them right now.

As previously, TYSM for your speedy answer!

Hello Jordy, Thank you for your speedy answer as always. The problem must come from somewhere else, and as often it was just coincidental. (BTW, FYI I also noticed before to deactivate WP fastest cache that the chatbot answer was impacted, and could not be displayed without re-loading the page).
In any case, I’ll try to follow your advice and do without a cache plugin (my situation now)
My explanation for why we use it = when you have no real clue about webmastering, code etc, and you have to develop a website (no choice or you disappear), and learn (a bit) through trial and error and reading on the www, then you make plenty of mistakes and compensate your ignorance and errors with a cache… ? ??

Hello,
Sorry for the belated answer but I did not get your answer through my emails.
I’ll check.
For the mails sent for all new posts, the title as link link is checked.
In the settings, the Engagement analytics tracking is on full.
However, I don’t know if this pays or not we have the CAOS plugin plus all the stuff related to respect of GDPR “activated” (GDPR settings through jetpack notice).

Also one possible problem could be linked to translatepress, as this happened before.
Today (see crash when sending mailoet email a hour ago), I noticed a weird thing: all the links from mailpoet email are to the page in the French translation (which it should not do): https://redanalysis.org/fr/2022/06/02/the-red-team-analysis-weekly-2-june-2022/?utm_source=mailpoet&utm_medium=email&utm_campaign=the-red-team-analysis-society-newsletter-post-title_6

the link should be without the /fr/

Previously, we had excluded /?mailpoet_router*
/fr/?mailpoet_router*
from the strings to translate and the problem was solved.

I checked the post notifications settings and the post selection is simply tag:featured

The wp_mailpoet_statistics_opens database table appears all right (it was not in the rables idenified for repair.

As we just posted a new article today, the sending of the emails with mailpoet crashed the website with database has gone away (no need to suggest we checked the FAQ, we did that a couple of years ago and everything is in order with a lot of space and resources for mailpoet :)).
This time, i copied the message before repairing the database here they are copied below – also we have fatal errors recorded in our log starting on 31 May linked to mailpoet.

Addition/edit: I just checked the error log and we have fatal errors since 12 May 2022, always the same, taking place each time we send mailpoet emails for post notifications. I am afraid to copy the error log here as it could (?) create security breach issue? Each tme there are 3 errors for each “fatal error” recorded (the tool used is woocommerce log status debug), with things like /mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/EntityRepository.php(73): MailPoetVendor\Doctrine\ORM\Persisters\Entity\BasicEntityPersister-> in … /plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php à la ligne 91#!trpst#/trp-gettext#!trpen#

repairing database:
(I did not copy the wc etc tables that were ok):

The wp_users table is okay.

The wp_usermeta table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_usermeta table.

The wp_posts table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_posts table.

The wp_comments table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_comments table.

The wp_links table is okay.

The wp_options table is not okay. It is reporting the following error: 2 clients are using or haven't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_options table.

The wp_postmeta table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_postmeta table.

The wp_terms table is okay.

The wp_term_taxonomy table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_term_taxonomy table.

The wp_term_relationships table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_term_relationships table.

The wp_termmeta table is okay.

The wp_commentmeta table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_commentmeta table.

The wp_actionscheduler_actions table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_actionscheduler_actions table.

The wp_actionscheduler_claims table is not okay. It is reporting the following error: 2 clients are using or haven't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_actionscheduler_claims table.

The wp_actionscheduler_groups table is okay.

The wp_actionscheduler_logs table is not okay. It is reporting the following error: 1 client is using or hasn't closed the table properly. WordPress will attempt to repair this table…
    Successfully repaired the wp_actionscheduler_logs table.

The wp_wc_category_lookup table is okay.

Repairs complete. Please remove the following line from wp-config.php to prevent this page from being used by unauthorized users.

Looking forward to a solution and thanks for your help
Helene

• This reply was modified 2 years, 9 months ago by HeleneL.

Hello Ojoma,
Thank you for your answer.

Did you mean the title on your new post included in the post notification email had a hyperlink that redirect to the error message “Oops! That page can’t be found”

Yes exactly.

Actually, you asnwer is bizarre because we had another batch that left on last Thursday and again the title of the post was a hyperlink… but this time it appeared to lead to the post. You can check that here (hopefully) in the read in browser
https://redanalysis.org/?mailpoet_router&endpoint=view_in_browser&action=view&data=WzU1MTA2LCIzMmI5MjhkNjg1NGIiLDAsMCw1NjY0MCwxXQ

The problem just happened and we have been able to send post notifications with paper.li since 2011 if I remember well ??
For the previous non functioning email the link is
https://redanalysis.org/?mailpoet_router&endpoint=track&action=click&data=WyI1NyIsImFlMzVlNSIsIjU1ODkzIiwiOTI1Y2IzNTRkNTUwIixmYWxzZV0
to compare with another email of the batch
https://redanalysis.org/2022/05/24/information-warfare-and-the-war-in-ukraine/?utm_source=mailpoet&utm_medium=email&utm_campaign=the-red-team-analysis-society-newsletter-post-title_4
that worked.

Re database: no we did not, but we noticed that each time there was a problem with mailpoet, which happens unfortunately every two months or so, when there is an upgrade, most often with created a problme with the database that needed repairing. If we did not repair it promptly, then after a couple of hours the website crashed. Usually once the database is repaired we get many messages that read (approximately) like … error.. failed to close line whatever etc. this has been repaired
Sorry next time I’ll pay more attention.

Hopefully you can find out what went wrong, I know I don’t give you many strong elements
Best regards
Helene

Hello
Sorry for the belated answer, too much work!
After upgrade of the plugin and unchecking the template in redux, it appears that some traces remain as can be seen in the source code of a page e.g. https://redanalysis.org/2021/11/22/long-covid-and-the-fifth-wave-the-hidden-pandemic/

</style>
<meta name=”framework” content=”Redux 4.3.3″ /><link rel=”alternate” hreflang=”en-US” …etc.

I also tried to deactivate Redux, but that was impossible without losing WP Mail Logging.

Thanks for your efforts in solving the problem
Best regards
Helene

Hello,
The banner went away, however, the library remains installed and active in the post editor, with no means to remove it. We can refuse it but this won’t remove it, as it is now installed…
Any way forward ?
Thanks in advance
Helene

Hi Jesse,
Thanks for your quick reply. As we need WP mail logging for mails, we cannot do that ??
Likewise! As Wysija and Mailpoet are serious and Mailpoet is now part of woocommerce and wordpress, I would hope that the problem will be solved quickly?
Fingers crossed!

Hello,
I have exactly the same problem, and even though I declined, when I create a new post, Redux has been added to the editor, without my knowledge!
How to remove Redux completely now as Redux does not appear in the plugin listed but was installed by WP Mail Logging?
Thanks for a rapid answer,
Best regards

Hello again Emre,

Happy to report that all problems are now solved, thanks to your point on xvarnish and surveillance.
Our provider installed engintron instead, and this morning I could reactivate WP fastest cache and all is fine, no users logged out so far. I’ll monitor closely what happens in the coming day, but hopefully everything will be fine.
(We even got 99% for desktop on google speed insight for some posts – less good for mobile, 58, but nothing new for us and actually an improvement on usual)

So A billion thanks to you and your great plugin.
I’ll check I gave already a 5 start rating to it, and if not shall do it right away,
With my very best
Helene

Dear Emre,
Thank you SO much for identifying this… thanks to you I could go back to my provider and now xvarnish is removed and I’ll be able to try using WP fastest cache again. Once I have had time to test it again (tomorrow probably), I’ll drop you a line to tell you how it went.
A billion thanks for your support
Helene

Hello again Emre,
As my provider could not find either any cause for the problem, but could replicate the issue, and as I am repeatedly logged out even as admin, I have no other choice than to deactivate for now your plugin.
If you have any idea of what is wrong, I would greatly appreciate your help,
Unfortunately, I could not replicate the problem on our staging website, which would have allowed me testing which plugin could conflict with WP fastest cache.
Best regards
Helene

Continuing my investigation, always for logged in users (same problem in both safari and firefox)
The first time I try to access a post authorised by my membership, I can see it properly.
If I close the tab and then try to access it again, then I am blocked as if I were not logged in….
sigh

Finally I tried the following thing (I cannot let the problem last for too long considering users, so at one stage I need to “solve” it by clearing the cache, which I did a couple of minutes ago):
desactivate Async JavaScript (just to try)
clear the cache
and of course it worked… until it starts logging users out?

Interesting point re logged in users: we use wpcourseware for online courses, and these remain accessible, when pages under simple membership cannot be accessed by logged in users. Yet we use membership to manage access to both courses and simple posts and pages on the website.
It just does not make sense.