Thank you for the expeditious response. This has consumed so much time in the past two months. We love the MailPoet plugin.
BlueHost did not provide the information we requested — a listing of every instigator of the 500 errors that began in early August.
We have site logs that are visible to us as a customer through cPanel and a Lin, and one of our project volunteers has been running Site Monitor for a few weeks.
Without warning or consultation, BlueHost began editing our .htaccess file because they said it did not contain “standard WordPress commands.” That made the problem worse. With BlueHost’s technician describing on the phone what our most-knowledgeable project volunteer needed to edit, he did so. For some reason, BlueHost’s technicians replaced that .htaccess file with their “standard” one.
The server error log we could see on our cPanel showed numerous errors generated by the .htaccess file BlueHost configured with all the “standard” WordPress lines that had not existed in our .htaccess file for the approximately 10 years our domain has been running just fine at BlueHost.
Our project volunteer uploaded a stripped-down .htaccess file that contained only redirects we need to keep our URL’s working properly as we make changes and updates from static HTML to WordPress. To my knowledge, BlueHost has not made additional changes to the .htaccess file.
The 500 errors have continued. Site Monitor logged 30 errors in 24 hours about a week ago, and it recorded a site failure that lasted at least 3.5 hours on September 21st.
BlueHost will not communicate except by e-mail. They are NOW blaming MailPoet.
For about two years, MailPoet has been running on a few WordPress sites on our domain with no problems. Beginning in March, 2023, we started adding MailPoet to approximately 50 WordPress installations on our domain, and things worked as expected until the beginning of August.
BlueHost shows 6821 calls in a 6 hours time frame from just two IP’s. Approximately 1500 calls were from wp-cron, and approximately 5300 calls from mailpoet_router.
MailPoet documentation says wp-cron is used to have the email queue continuously running. Since we send fewer than 300 Post Notification e-mails from any single MailPoet installation, the documentation suggests using server cron as also described in the reply above.
However, that does not explain why two of our MailPoet installations that are configured exactly like the others are creating 3000 calls in a six-hour window — at least that is what BlueHost is reporting.
I don’t want to share complete logs in this forum for account privacy and to avoid kludging the thread. However, if someone from MailPoet would message me separately, I can provide a lot more detail from logs, .htaccess files, and e-mail threads with BlueHost.
