Scanner problem with vpn

Hi @drorefraim

I would like to have a look at your Wordfence diagnostics report. Please go to the top of the “Diagnostics” tab on the Wordfence “Tools” page. There will be a “SEND REPORT BY EMAIL” button to send the diagnostics report. Enter wftest [at] wordfence [dot] com as the email and drorefraim as the forum username please.

Once you have emailed me the diagnostics report can you reply here to let me know that it has been sent. This is important in the unlikely event that your installation of WordPress is having an issue with sending mail.

Hi,
Tanks for fast replay!
I sent you the diagnostics report.

Hi @drorefraim

Thank you for the report.

The error isn’t caused by Wordfence. The Wordfence scanner needs to be able to send requests back to the website. The error is for a test using WordPress’s own function wp_remote_post:

https://developer.www.ads-software.com/reference/functions/wp_remote_post/

The test checks that WordPress is able to send a request back to itself but that is failing.

This is why your scans are failing.

The cURL 28 error is common and usually temporary. If you see it persistently then your hosting provider is going to have to investigate and fix the fault on the server causing the error.

You may be able to get the scanner to work use the option Start all scans remotely (Try this if your scans aren’t starting and your site is publicly accessible). This is found in the Debugging Options section on the Tools >> Diagnostics page.

Hi,
I just sent you the new diagnostics report that shows curl without errors.
However, the scan still faild and the scan log not showing errors.
Also checked console log and server errors but it’s clean.
What can it be?

Hi @drorefraim

Please check our troubleshooting page here first:

https://www.wordfence.com/help/scan/troubleshooting/

If that doesn’t help, can you do the following so I can get the information I need to help you:

– Kill the existing scan if one is still running by pressing the STOP SCAN button.

– Click on the Scan Options and Scheduling link.

– In the Performance Options section set Maximum execution time for each scan stage to 20.

– Hit the SAVE CHANGES button.

– Go to the bottom of the Diagnostics tab on the Tools page and expand the Debugging Options section.

– Enable the option below:

Enable debugging mode (increases database load).

– Disable the option below if it is enabled:

Start all scans remotely (Try this if your scans aren’t starting and your site is publicly accessible).

– Hit the SAVE CHANGES button.

– Start a new scan.

– When the scan has definitely failed, or definitely appeared to have got stuck, click on the EMAIL ACTIVITY LOG link to email the scan activity log and send it to wftest [at] wordfence [dot] com.

Once you have emailed me log can you reply here to let me know here that it has been sent. This is important in the unlikely event that your installation of WordPress is having an issue with sending mail.

– Remember to disable Enable debugging mode (increases database load) after you have finished.

Hi,
Troubleshooting page didn’t help.
I followed the settings you mention and sent you the new report after the scan failed

Hi @drorefraim

I am taking a look at the scan activity log now for you and will reply shortly.

Hi @drorefraim

The scan is failing without any useful diagnostics information. You will need to ask your hosting provider to look at the last timestamp below of when the scan failed and then they can look at all of the log files on the server for that time to see if they can find out what caused the scan to fail.

Sun, 19 Sep 21 06:24:33 +0000::1632032673.2610:4:info::getMaxExecutionTime() returning config value: 20