Hi @akwasid,
Thanks for reaching out and starting a new thread. We’d like to get some additional information from you, please:
- Do you see a generic server 503 error or are there any details on the 503 page?
- Does StableHost use cPanel as the control panel for their hosting?
- Do you know if the server runs Apache, LiteSpeed, Nginx, or something else?
- Are you using the latest version of Wordfence (8.0.5), before and after reinstalling?
If possible, can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so at the top of the Wordfence > Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.
NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email
If you can’t access Wordfence at all, please email an export of your Site Health to wftest @ wordfence . com. In the WordPress dashboard, under Tools > Site Health > Info, click Copy site info to clipboard. Paste this information into the email and use your forum username as the subject. Respond here after you’ve sent it.
If you’re on an older version of WordPress where Site Health isn’t available, please send a list of your plugins, themes, current WordPress version, and current PHP version to wftest @ wordfence . com. Use your forum username as the subject of the email and respond here after you’ve sent it.
Thanks,
Margaret
Hi @akwasid,
Thanks for sending that over. While Wordfence is compatible with PHP 7.4, we believe something has changed at multiple hosting providers at the same time, whether it’s a PHP update, a cPanel update, a change in a cPanel extension they’re using, an operating system update, etc.
We’ve had users with those hosting providers report that updating to PHP 8.1 or 8.4 resolves the 503 error on their site. If your site is compatible, please try updating the version of PHP used on the site and test again.
Please let me know how it goes!
Thanks,
Margaret
@wfmargaret thanks. switching to PHP version 8.0 solved my issue. 8.1 for some reason didnt work
Hi @akwasid,
I’m glad to hear it! Thank you for letting me know.
I’m going to resolve this thread, but if you notice any issues over the next few days, please feel free to follow up with me here, and I’ll be happy to help.
Thanks,
Margaret