FastCGI Errors with Latest Official X and Pro Themes and WP 6.2

Support
#1

Hi there,

One by one, my sites have been going offline. All of them with a suspicious, generic 500 error produced by the server and NOT by WordPress.

While wp_debug doesn’t seem to help, the server error logs usually reveal errors such as this:

[Wed Mar 29 18:41:48 2023] [warn] [client 208.115.199.24] mod_fcgid: error reading data from FastCGI server, referer: https://www.example.com/
[Wed Mar 29 18:41:48 2023] [error] [client 208.115.199.24] Premature end of script headers: index.php, referer: https://www.example.com/

All of the sites are using either:

Pro 5.1.5
X 9.1.4

And upon further inspection, they are all using WordPress 6.2.

Now, I noticed your forum post here: Important WP 6.2 Issue — Please Read Before Updating

Can you confirm that it is, indeed, the problem being referenced? I hadn’t seen that post, but I did figure out on my own to install that newest beta version and it has solved the problems so far.

However - here is the issue. I have in the ballpark of maybe 60 websites using Pro or X. I’d really rather not be putting out fires for the next week as they auto-update and go offline.

What exactly can I do? It’s going to be a huge pain in the butt to go through and FTP an updated theme version to every single one of them proactively.

When will a new version be available via the WordPress dashboard? Is there anything else I can do?

Thank you!

#2

There is already a new update out for this issue. If you’re on Pro 5 / X 9 you can follow this guide to check if it’s actually the same issue. It probably is as that file has been unchanged since 2016. So I’d do that if you’re trying to stick on Pro5. Or just turn off auto-updates for WordPress core. It’s a little annoying to me auto-updates are now the default for core as it’s something I would never turn on if given the choice.

To check if it’s the same issue
if you wish to manually fix the issue you can add return; to line 194 of framework/legacy/functions/plugins/cornerstone.php

#3

Hi Charlie,

Thanks for confirming it is that issue. There weren’t really any details in the announcement post so it was hard to say.

When will Pro 6.x be available via the WordPress backend for updates? Once that is out, I can update my sites to use it before they auto-update to WP 6.2. I’m hoping you’ll be able to do that very soon, otherwise I’m going to have to deal with a lot of headaches.

#4

6.1.10 has the fix for WordPress 6.2. It’s already out so go ahead and start updating, before WordPress core updtaes.

#5

I know that, but as mentioned: I have something like 60+ websites to update. I’m not going to take the time to upload a new theme via FTP for each of them, that will take forever.

I’m wondering when we’ll be able to update directly through the backend. When will I be able to click “update” on the theme and have it go to 6.1.10? It seems like the stable release is still 5.x.

#6

Actually, I do see that it’s available now. Yesterday I didn’t think it was. I don’t know if you just updated or not, but that’s all I needed.

Thank you!

#7

Yes sometimes it takes a little bit for it to show up. /wp-admin/update-core.php this path on your domain will always show the latest update regardless of the wp-cron status.

Happy to help have a great day!

#8

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.