An illustrative and conceptual image showing an AI entity troubleshooting a WordPress PHP error

Troubleshooting WordPress session_start SiteHealth Critical Issue

()

Wonder what to do if you get the below message from your WordPress GoDaddy managed website:

A PHP session was created by a session_start() function call. This interferes with REST API and loopback requests. The session should be closed by session_write_close() before making any HTTP requests.

The first thing to do is to Open your GoDaddy hosting, then go to the WordPress File Manager and navigate to the plugin sections as per screenshot below:

godaddy wordpress file manager

The next step is to download the plugin folder using the menu.

Once that is done your browser will download a file named plugins.zip which can easily be decompressed using a tool like 7-zip.

Once this is done, if you are using windows, i recommend using grepWin to decompress the content.

Once done search in the content of all files for “session_start“, this is what I got:

grepwin search

In my case the issue was coming from row 403 in file class-ads-admin.php under the monetag-official folder:

 session_start() function call from a wordpress plugin

I then deactivated the plugin from WordPress plugin manager and the Critical alert disappeared from the dashboard!

I also notified the MoneTag support team via email about it, they resolved the issue in 24 hours releasing version 1.1.2, I was able to successfully reactivate the plugin and no more warning.

I hope this post can help others to debug similar issues.

No AI was needed in this case, however would be great to have something added to github Copilot.

How useful was this?

Click on a star to rate it!

Average rating / 5. Vote count:

No votes so far! Be the first to rate this post.