Jili live casino login register download.REGISTER NOW GET FREE 888 PESOS REWARDS!

syedaliazlan
(@syedaliazlan)

1 year, 5 months ago

Hi,
I am having issues with initiating the scan through WordFence and I have already tried all debugging solutions provided. Just now, I was talking to my web host (SiteGround) about it and they revealed the actual reason behind it I am going to share it below:

“Hello, Syed,

The issue is because the WordFence API sends requests authenticating as a very old User Agent – “Chrome/33” according to the logs on the server. Here’s how the request made from WordFence

“GET /wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=standard&cronKey=f247a54996dbb2dd6b83d655cf582733&signature=7eef4e5209f9120fa1e482418887502a509f079195fddd08a0fb1d920d1ad19c&remote=1 “-” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.152 Safari/537.36″

This user agent is blacklisted by one of our security mechanisms. Our team regularly updates the firewall rules, which is why the issue started recently. For security reasons, such outdated user agents can no longer access our infrastructure.

As you know, security is our top priority, and we are improving it daily. The new implementations aim to strengthen your account’s overall security further, prevent malicious traffic and brute-force attacks, and improve the overall stability of the server.

Old User Agents are mainly used with malicious intent. Particularly the Chrome/33 User-Agent refers to a really old Chrome version, which is no longer officially supported and lacks the security of a modern browser. It is up to the software developer to regularly update their software to ensure it’s compliant with the latest security standards. It identifies with the correct User-Agent across the internet.

To resolve the issue, you should contact WordFence and ask them to update the User Agent to match the modern standard for a browser’s User Agent:

https://www.rfc-editor.org/rfc/rfc7231#section-5.5.3“

I have also shared the diagnostic report to your email with the forum username as requested. I am looking forward to find a resolution for this issue soon as it might impact all of the users who are using SiteGround hosting.

Thank you!

The page I need help with: [log in to see the link]

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

Plugin Support wfpeter
(@wfpeter)

1 year, 5 months ago
Hi @syedaliazlan, thanks for reaching out!

The Chrome/33.0.1750.152 user-agent shouldn’t be Wordfence as our requests should be seen as coming from WordPress/6.3 (or whichever version you currently have installed). I have seen a few older cases of the Chrome user-agent showing up when something is redirecting default HTTP error codes like 500 or 404, the site is having trouble connecting to itself (or our servers), or the default /wp-admin page is being redirected by a plugin.

Try enabling “Start all scans remotely” on the Wordfence > Tools > Diagnostics > Debugging Options section.

If it fails again with that turned on, the last 20 lines of the scan log would be helpful to us to determine what was happening immediately before:
- Stop the existing scan if it is still running (The “Start New Scan” button turns into a “Stop” button while the scan is running).
- Go to the Tools > Diagnostics page.
- In the “Debugging Options” section, if “Start scan remotely” is still checked, now uncheck this option.
- Click to “Save Changes”.
- Start a new scan on the Scan page.
- If the scan fails again, copy the last 20 lines or so from the Log (click the “Show Log” link) once the scan finishes and paste them in your next reply.
Thanks,
Peter.
Thread Starter syedaliazlan
(@syedaliazlan)

1 year, 5 months ago
Hi,
I have tried enabling and disabling the “Start scans remotely” option but it didn’t help. Also, the scan terminates as soon as I hit the “start scan” button.
Furthermore, I have also enabled WordPress troubleshooting mode to disable all other plugins to see if it’s the plugin conflict but had no look.

Lastly, I enabled debugging under WordFence and eventually got the logs you asked for and I am sharing them below:
- [Oct 12 11:38:51] Scan stop request received.
- [Oct 12 11:39:13] Scan stop request received.
- [Oct 12 11:41:23] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=55685c0ecc5f5bd48014166a4f9faf1649f097254fcf92539338746710d8f08dd6ec5acee92425ec1bb3b6e0986af97111e39e06b946b14899f4454f6cb6980e&s=eyJ3cCI6IjYuMy4xIiwid2YiOiI3LjEwLjQiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvcmFuZGN3aWxsaWFtcy5sdGQudWsiLCJzc2x2Ijo4MDUzMDY0OTYsInB2IjoiNy40LjMzIiwicHQiOiJhcGFjaGUyaGFuZGxlciIsImN2IjoiNy44NS4wIiwiY3MiOiJPcGVuU1NMXC8zLjAuOSIsInN2IjoiQXBhY2hlIiwiZHYiOiI1LjcuNDMtY2xsLWx2ZSIsImxhbmciOiIifQ&action=timestamp
- [Oct 12 11:41:26] Scan stop request received.
- [Oct 12 11:41:46] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=55685c0ecc5f5bd48014166a4f9faf1649f097254fcf92539338746710d8f08dd6ec5acee92425ec1bb3b6e0986af97111e39e06b946b14899f4454f6cb6980e&s=eyJ3cCI6IjYuMy4xIiwid2YiOiI3LjEwLjQiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvcmFuZGN3aWxsaWFtcy5sdGQudWsiLCJzc2x2Ijo4MDUzMDY0OTYsInB2IjoiNy40LjMzIiwicHQiOiJhcGFjaGUyaGFuZGxlciIsImN2IjoiNy44NS4wIiwiY3MiOiJPcGVuU1NMXC8zLjAuOSIsInN2IjoiQXBhY2hlIiwiZHYiOiI1LjcuNDMtY2xsLWx2ZSIsImxhbmciOiIifQ&action=plugin_vulnerability_check
- [Oct 12 11:43:12] Ajax request received to start scan.
- [Oct 12 11:43:12] Entering start scan routine
- [Oct 12 11:43:12] Got value from wf config maxExecutionTime: 0
- [Oct 12 11:43:12] Got max_execution_time value from ini: 120
- [Oct 12 11:43:12] ini value of 120 is higher than value for WORDFENCE_SCAN_MAX_INI_EXECUTION_TIME (90), reducing
- [Oct 12 11:43:12] getMaxExecutionTime() returning half ini value: 45
- [Oct 12 11:43:12] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/randcwilliams.ltd.uk/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=highsensitivity&cronKey=bc579774ebe41176dc9b821e29780be0&k=55685c0ecc5f5bd48014166a4f9faf1649f097254fcf92539338746710d8f08dd6ec5acee92425ec1bb3b6e0986af97111e39e06b946b14899f4454f6cb6980e&ssl=1&signature=459faee5e55a8b0c4757fdac127fed806ae04bdf7401da572e79a9ba0a12c4cc
- [Oct 12 11:43:13]?Scan process ended after forking.
  
  Thanks and I am looking forward to hearing back from you.
  These are the error screenshots:
  https://prnt.sc/XClw3pSFTzl6
  https://prnt.sc/UfZZ8CIzDRlN
Thread Starter syedaliazlan
(@syedaliazlan)

1 year, 4 months ago

Hi. I am still waiting for an update from you guys. Could you help please?

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

The topic ‘Scan Stage Failed’ is closed to new replies.