400 Bad Request

Resolved Telx
(@sjswarts)

4 years, 9 months ago
Hi guys, I’ve followed all the other posts about this but to no avail.

WordFence refuses to scan. Fails immediately after manual run.

What I’ve tried:
– checked .htaccess for any offending code. None found.
– turned off all plugins
– running latest version of everything
– set remote scanning mode
– ensured that the A records point to the right location, no duplicates
– navigated to https://domain.com/wp-admin/admin-ajax.php
– checked hosting firewall for any WordFence IP’s
– We use CloudFlare – Use the Cloudflare “CF-Connecting-IP” HTTP header
–

I’m still getting this error:
https://techcareau.sharepoint.com/:i:/s/Clients/EaW8gDfAUUJGmn2JI2QIlxEBne_2k3nN8s4gjLnYnDNHpQ?e=Ahk0TN
```
HTTP/1.1 400 Bad Request
Date: Fri, 13 Aug 2021 02:18:47 GMT
Server: Apache
X-Powered-By: PHP/7.2.34
X-Robots-Tag: noindex
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
Referrer-Policy: strict-origin-when-cross-origin
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Upgrade: h2,h2c
Connection: Upgrade, close
Transfer-Encoding: chunked
Content-Type: text/html; charset=UTF-8
```

Viewing 5 replies - 1 through 5 (of 5 total)

Plugin Support wfpeter
(@wfpeter)

4 years, 9 months ago

Hi @sjswarts,

It certainly looks like you’ve tried a good number of possible solutions from previous similar issues. I think that it may be a good option to look at your site configuration myself so I don’t try to cover similar ground without knowing a bit more about your site. Can you please 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: For the fastest response time, please make sure and add any information or questions directly to this topic and not the email address above unless asked.

Thanks,

Peter.

Thread Starter Telx
(@sjswarts)

4 years, 8 months ago

G’day Peter,

Thanks for the response. I’ve sent the diagnostics to the email address mentioned.
Received “Diagnostic report has been sent successfully.” so I’m assuming it has been sent.

Thread Starter Telx
(@sjswarts)

4 years, 8 months ago

@wfpeter any update mate?

Plugin Support wfpeter
(@wfpeter)

4 years, 8 months ago

Hi @sjswarts,

I have been catching up with some annual leave and have had some feedback from our team regarding your diagnostic.

I am seeing the 400 error occur and the page received when running the “Connecting back to this site” test. However, if I try to make the same call myself in a browser, I get a 200 OK response so the endpoint is visible and your site is responding as normal to external requests.

When this check works from a browser, and not from the server itself, the server may be connecting to a different server. For example, if its IP was changed and it has an entry in /etc/hosts for its own domain, pointing to the old IP. This is a problem that cropped up recently and was solved by fixing the hosts file. It’s also possible a plugin is changing the wp-admin/ URL in a way that Wordfence can’t see, but usually we’d expect a 404 or 200 response instead. There could be other causes in plugins or themes too so disabling every plugin except for Wordfence and switching to a default theme such as Twenty Twenty-One could help. If the connection works under those conditions, re-enable your plugins one-by-one and finally your theme to see when the connection starts presenting the 400 error again.

Thanks again,

Peter.

Thread Starter Telx
(@sjswarts)

4 years, 8 months ago

@wfpeter – hope you had a relaxing time mate.
Thanks also for getting back to me.

I don’t know why but it is working now? I checked yesterday (haven’t checked since my previous response) and it is all good.

Don’t know what changed, but all is well now.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘400 Bad Request’ is closed to new replies.

Tags