Server state yellow warning
-
I logged in to my website and had a notification from Wordfence. In my scan I have a warning in my server state (yellow triangle) I did a scan to see if it worked and the scan did go through and completed the task. However, the warning persisted. I went to options and the scan options seem OK.
Any help with this would be appreciated.
Many thanks
The page I need help with: [log in to see the link]
-
Hello @muhammadzak and thanks for reaching out to us!
Can you 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.
Thanks!
Hello, Done I have sent the email
Thanks for sending those reports @muhammadzak
Looks like you are using Cloudflare as your CDN.
If your site is protected by Cloudflare, you may need to update your Cloudflare settings to allow your site to connect back to itself. You should be able to do this by going to your Cloudflare control panel.
- Login to Cloudflare
- Go to “Firewall”
- Click the “Firewall Rules” tab
- Click “Create a Firewall rule”
- Name the rule under “Rule Name”
- Set the “Field” under “When incoming requests match…” to “IP Address”
- Enter your site’s IP address under “Value”
- At the bottom, under “Then…Choose an action” change “Block” to “Allow”
- Click “Deploy
Once you have added your site to the Cloudflare Whitelist, head back over to your site and attempt another scan.
Let me know if this helps and if you have any questions!
Thanks!
I followed your steps and still having the same yellow server alert
Try the following:
- Kill the existing scan if it is still running (The “Start New Scan” button turns in to a “Stop” button while the scan is running)
- Go to your Scan > Scan Options and Scheduling page and locate the “Performance Options”
Set “Maximum execution time for each scan stage” to 20 on the options page - Click to “Save Changes”
- Go to the Tools > Diagnostics page
- In the “Debugging Options” section check the circle “Enable debugging mode”
- Click to “Save Changes”.
- Start a new scan
- Copy the last 20 lines from the Log (click the “Show Log” link) or so of the activity log and paste them in the post.
On occasion, this fixes it straight away. That’s because adding 20 for the “Maximum execution time for each scan stage” tells the scan to pause every 20 seconds and start again where it left off. If this fixes the issue and scans run again, you can leave all the settings above except for “Enable Debugging Mode”.
Thanks!
Hello, it didn’t fix the issue and it also prevent wordfence from completing the scan
here are the 20 lines[Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ernubh-247x296.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ernubh-280x280.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ernubh-280x280.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ernubh-300x400.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ernubh-300x400.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ernubh-510x680.bk.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ernubh-510x680.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ernubh-510x680.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ernubh-600x800.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ernubh-600x800.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ernubh.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ernubh.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-100x100.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-100x100.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-247x247.bk.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-247x247.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-247x247.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-247x296.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-280x280.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-280x280.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-300x400.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-300x400.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-510x680.bk.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-510x680.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-510x680.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-600x800.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u-600x800.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-f5rs0u.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-fl4og8-100x100.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-fl4og8-100x100.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-fl4og8-247x247.bk.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-fl4og8-247x247.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-fl4og8-247x247.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-fl4og8-247x296.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-fl4og8-280x280.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-fl4og8-280x280.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-fl4og8-300x400.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-fl4og8-300x400.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-fl4og8.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-fl4og8.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ftf6in-100x100.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ftf6in-100x100.jpg.webp [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ftf6in-247x247.bk.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ftf6in-247x247.jpg [Oct 20 19:12:48] Skipping unneeded hash: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ftf6in-247x247.jpg.webp [Oct 20 19:12:49] 15433 files indexed [Oct 20 19:12:49] Forking during indexing: /home/u249594854/domains/jewelleryrack.com/public_html/wp-content/uploads/2019/08/10208-ftf6in-247x296.jpg [Oct 20 19:12:49] Entered fork() [Oct 20 19:12:49] Calling startScan(true) [Oct 20 19:12:49] Got value from wf config maxExecutionTime: 20 [Oct 20 19:12:49] getMaxExecutionTime() returning config value: 20 [Oct 20 19:12:51] Test result of scan start URL fetch: array ( 'headers' => Requests_Utility_CaseInsensitiveDictionary::__set_state(array( 'data' => array ( 'date' => 'Tue, 20 Oct 2020 17:12:51 GMT', 'content-type' => 'text/html; charset=UTF-8', 'set-cookie' => '__cfduid=d30c3705046a5533a4e4a6f52858b2b2f1603213969; expires=Thu, 19-Nov-20 17:12:49 GMT; path=/; domain=.jewelleryrack.com; HttpOnly; SameSite=Lax; Secure', 'x-powered-by' => 'PHP/7.4.11', 'x-robots-tag' => 'noindex', 'x-content-type-options' => 'nosniff', 'expires' => 'Wed, 11 Jan 1984 05:00:00 GMT', 'cache-control' => 'no-cache, must-revalidate, max-age=0', 'x-frame-options' => 'SAMEORIGIN', 'referrer-policy' => 'strict-origin-when-cross-origin', 'x-litespeed-cache-control' => 'no-cache', 'vary' => 'Accept-Encoding', 'strict-transport-security' => 'max-age=31536000; includeSubDomains; preload', 'content-security-policy' => 'upgrade-insecure-req [Oct 20 19:12:51] Starting cron with normal ajax at URL https://jewelleryrack.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&scanMode=standard&cronKey=ad0280ceeee241168392349af386a212&signature=f5149dd5afb4ae4eb92bfff7a1fdee987f5822e4ebb4a42b3560fc2c472c6d41 [Oct 20 19:12:52] Scan process ended after forking.
I copied the last 20 lines here but WordPress holding my reply for approving
Thanks for posting that. I went back over your diagnostics and realized you are also running Litespeed. Have you set up the following yet:
https://www.wordfence.com/help/advanced/system-requirements/litespeed/
It will require the addition of some code. Once you get this set up, attempt another scan and let me know how it goes!
Thanks!
Hello again, well my sever have been always litespeed and it was working fine with wordfence, Anyway, I tried to add the three codes you mentioned, non of them worked and all over them showed the yellow alert in server state
bestWhen did you notice that the scan had stopped working? Any updates that were applied? Added any new plugins?
I don’t know actually but even with all plugins disabled I still have the same problem, I’m using WordPress auto-update feature
Hello again @muhammadzak
It looks like scans are completing still but just the server state is yellow, correct?
Could you try changing your IP detection to test. Navigate to All Options > General Wordfence Options > How does Wordfence get IPs and select Use the Cloudflare “CF-Connecting-IP” HTTP header to get a visitor IP. Only use if you’re using Cloudflare.
Then head over to your Scan and Cancel the current scan and start a new one.
Let me know what you find!
Thanks!
Hello it didn’t work and still have yellow alert and the scan didn’t complete
It seems like you have everything set up correctly. It is possible that a table has corrupted after a possible update to something. The last resort is always a complete reinstall.
You can backup your Wordfence settings via the Export option. Navigate to Wordfence > Tools > Import/Export Options and click Export. You can also take note of the current Whitelisted URLs you have in Wordfence > Firewall > All Firewall Options > Whitelisted URLs as these are NOT included in the Import/Export, and will be lost during the re-install.
Here is what is exported: https://www.wordfence.com/help/tools/import-export/
During the export, you will be given a long string of text. Keep this safe, you’ll need it in a few minutes.After that, enable the option to Delete Wordfence tables and data on deactivation in All Options > General Wordfence Options. You will want to remember to disable this after you reinstall Wordfence again.
After you enable that option, you can deactivate Wordfence from the Plugins area of your site, then delete it. Next, from the plugins area, search for and re-install Wordfence like normal.
It will be like setting Wordfence up for the first time. You will need to enter an email address, and then go into Tools > Import/Export Options and paste that string of text into the Import Wordfence Options field and click the button there.
The firewall will be in Learning Mode by default for 7 days. I would recommend switching this to Enabled and Protected as soon as possible.
Let me know how this goes!
It didn’t work, I still get a yellow mark for server state ??
- The topic ‘Server state yellow warning’ is closed to new replies.