Error on AMP sites only

Yeah, that surely wouldn’t cause a fatal error but it would result in AMP detection not being reliable. Any call to the mentioned functions should only happen at wp or later as indicated.

Nevertheless, I’m surprised that it says Jetpack is responsible. Can you share a list of the Jetpack modules you have active? That information isn’t present in the Site Health information.

I’m on Jetpack Premium, and I have most of their features on.

I have received a reply from my hosting provider:
“Thank you for writing back to us. First of all, we would like to take this opportunity to apologize for the inconvenience you have experienced thus far throughout this process.

I completely understand your concern regarding the Amp plugin compatibility. I have reviewed the case history and understand that website links ending with /?amp link is not working and showing Internal Server Error. I have reviewed the screenshots provided by you are those were very helpful. I have reviewed the Amp Validator and it is showing a script error.

It looks like a configuration issue with the Amp plugin and not from the server end.

Also, I have reviewed the error_log file and it is showing the following error:

PHP Warning: PHP Startup: Unable to load dynamic library ‘ixed.7.4.lin’ (tried: /opt/cpanel/ea-php73/root/usr/lib64/php/modules/ixed.7.4.lin (/opt/cpanel/ea-php73/root/usr/lib64/php/modules/ixed.7.4.lin: cannot open shared object file: No such file or directory), /opt/cpanel/ea-php73/root/usr/lib64/php/modules/ixed.7.4.lin.so (/opt/cpanel/ea-php73/root/usr/lib64/php/modules/ixed.7.4.lin.so: cannot open shared object file: No such file or directory)) in Unknown on line 0

It looks like the Amp plugin is not compatible with the higher PHP version. Also, I have referred below help articles:
https://www.ads-software.com/support/topic/cant-get-amp-pages-to-work/

https://www.ads-software.com/support/topic/doesnt-works-with-pages-and-custom-post-types/

I have flushed the permalinks via WordPress Dashboard >> Settings > Permalinks and re-save. However, the issue was not resolved. Also, checked the .htaccess file located in domain directory /public_html/lifeofaworkingadult/ and there is no issues with that file.

It does look like there are multiple reasons for this issue to occur with the Amp plugin. We did try some of the fixes that do not require code changes. To prevent any further issues involving the site, we strongly recommend reaching out to Amp plugin support for more information on how to address this:
https://www.ads-software.com/support/plugin/amp/

The issue you are seeing on your website is not caused by any wrong server configurations. It seems like a website plugin/design/coding issue. It is advisable to contact the web developer to get this checked.

As scripting/coding is something beyond scope of our support, we would request you to contact the plugin provider or developer to check on this and let us know if they would need us to make any changes from our end towards resolution, we’ll be more than happy to check it for you.”

Humm. That PHP warning doesn’t seem related to the AMP plugin. It seems like a server misconfiguration issue to me, but nevertheless it is a warning and not a fatal error so I don’t see why it would the Internal Server Error.

We test the AMP plugin on PHP versions from 5.6 all the way up to 8.0.

Thanks for nothing that you’re using Jetpack Premium. We’ll try to reproduce the issue with Premium.

Thanks. Just to let you know, each time I disable JetPack, all the Internal Server Error issue will be solved, and whenever I enable JetPack again, the Internal Server Error comes back, even for new posts that I just posted today (https://lifeofaworkingadult.com/2021/05/15/raya-2021-with-covid-19/?amp)

And oh, I installed the newer version that has yet to be released via www.ads-software.com, but it doesn’t fix my problem either.

Which BlueHost plan are you using?

Right now I’m on Shared Choice Plus plan.

We’re currently replicating your site setup so we can attempt to reproduce the issue.

Just to let you know we’ve been unable to replicate the same issue you’re encountering. I don’t see AMP active on the URLs I checked on your site at present, can you share you’re experience the same issue with the latest version of the plugin?

I have temporarily disabled the AMP plugin, as I’ve decided to switch from Divi builder to Elementor builder. I will update here once I’ve performed the necessary changes.

Sorry for the inconvenience.

No problem at all. I’ll close this support topic for the moment given we’re unable to reproduce, although if you do happen to encounter this once more let us know and we can once again review.

Hello, I am receiving the same error message – how was this resolved with DIVI?

Hello @adelevarris

Please create a new support topic so we can check your issue in a specific topic.