Sounds like a server-side problem. I would recommend contacting your host’s support team.
I have contacted them, and they think it is a problem with my installation. But I can’t figure out how that could be given that we didn’t make any updates.
If You use the optimization plugin, clear the cache, deactivate it temporarily, and then try again. Try with a different browser. And take a look this publication; there has some advices to solve error 400 – https://www.novatel.bg/http-400-what-does-it-mean-and-how-to-fix-it/
I have already deactivated it, and tried with a different browser.
I can’t clear the cache from within the w3 cache plugin, as I also get the error then.
Any other advice?
Sounds like a server-side error. The reason for the error should be visible in the error log. You can find it in your hosting area. If necessary, the support of your hosting can help you.
Alternatively, you could also enable debugging in WordPress. How to do this is described here: https://wordpress.org/support/article/debugging-in-wordpress/ – also here the support of your hosting can help you if necessary to edit the file accordingly.
In both cases you should be able to see what the cause is in the logfile.
I have already tried most of the things in that article as well, I will go through and see if there are any I have not.
In debugging, I get this message: Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the salient domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home3/8/investhub/www/wp-includes/functions.php on line 6121
My hosting provider has been pretty insistent that it is not them, but I will try again. Unfortuantely, the host does not have a client-side server area
The message is a note, not an error. It is definitely not the cause of your problem. Is there really nothing else? Which log does it come from exactly? Such server-related errors are more likely to appear in the hosting error log than in the WordPress debug.log, but it also depends on the hosting configuration.
If you can’t find it yourself and the hosting support is uncooperative, you have two options:
- Move the project to another host. You don’t even have to change the domain to do this, just install WordPress somewhere else with a different domain (or subdomain, or even in a local installation) and see if it works better there. If so, then the problem really is with your current hosting provider.
- You can also find someone who can provide you with personal support. You can find someone like this here, for example: https://jobs.wordpress.net
Yes, it’s annoying that such an error cannot be found and fixed in other, simpler ways. Here in the forum, we can only give you tips for self-help, but sometimes you are dependent on your host for something like this.
