randomcoder

Disabling ALL plugins still does not solve the loopback problem. For good measure, I also removed all the extra stuff from .htaccess, and that didn’t help either. No idea how I could troubleshoot it further, since it happens on a rented hosting and I don’t have direct access to the underlying OS (I do have SSH, but with very limited set of capabilities).

It’s quite obvious that users generally want to generate a static version of their site in order so that they could host that static version.

But yes, it would be cool if the plugin enabled you to automatically serve the static site without actually physically separating the WP source website and the static hosting.

That could be a problem as I can’t have a company’s site without plugins, it doesn’t work at all. But I get your point, I will make a copy on a test domain and will try there. Very odd that such info would be cached, if it really is – that’s a bug, in my opinion.

Thanks for the advice! I deactivated all the plugins, went back to “Site health” and the loopback error was still there. Do I need to also reset or restart something after deactivating the plugins?

The WP version is not too old – 6.4.1.

In the “site health” report: WordPress admin dashboard -> Tools -> Site Health.

Okay, thank you, I understand. How severe is this issue? What are the things that would commonly break if I ignore this?

Could you tell me what page or what request is used for testing loopback functionality so that I could execute it in a browser? Actually, is it even possible, I thought loopback always means “local”, as in 127.0.0.1?

And how can I trigger a re-check?

• This reply was modified 1 year, 3 months ago by randomcoder.
• This reply was modified 1 year, 3 months ago by randomcoder.

Well thank you for posting two ChatGPT replies, I can ask it myself if I want a bunch of useless answers.