You shouldn’t be getting a nothing found error just for a SSL problem. Security warnings, sure. But something should be found. If you removed the https redirect, do you get content with a basic http request?
Try placing a simple static index.html file in public_html. (you might need to rename index.php as well) It can just have minimal html tags and say “Hello world”. Be sure the file permissions are correct, typically 644. If requesting your domain name via http doesn’t return this page you should get help from your host. Your account is not setup right. If so, reinstalling WP will not help.
If there is no other content in public_html besides WP files and uploads (media files) you don’t need, you can delete everything and re-upload WP files or re-install from your hosting control panel. WP doesn’t normally use private_html but your host may have modified their version of WP. I cannot comment on removing files from there.
If you’re going to start over with WP, not only should you delete its files, but also drop its tables from its database. You use the phpMyAdmin app for that. Usually it’s accessed from your hosting control panel.
Thread Starter
forwp1
(@forwp1)
Thank you for the answer. I logged in to the control panel just to check something and apparently it got updated. What I first saw was some minor front-end changes – different login screen and copyright changes in the footer. With that update also my problem has somehow been fixed, so redirections work as intended and homepage is in it’s place. Site Health still reports issues about outdated PHP (found nothing on how to update) and REST API error.
That’s good news! To update PHP, there is usually some way through you hosting control panel to select the PHP version. Look for a link or icon titled “software” or “PHP” or the like.
If after updating PHP and any WP elements that might need it, if you still are getting REST API errors, it’s likely something about your server configuration that you’ll need your host to help you with. Before contacting them, try disabling all plugins and switching to the twentytwenty theme. If the problem goes away, restore your configuration one module at a time until the problem recurs. The last activated module is causing a problem.
If you still have the error with WP in its out of the box state, then there’s an issue with the server configuration.
Thread Starter
forwp1
(@forwp1)
So, I have updated PHP and now it seems everything is running fine apart from REST, but I will get into it later. Thank you for your help and I mark this thread as resolved.
