Error Scan

Resolved alanaguiar
(@alanaguiar)

6 years, 11 months ago

error on my scanner

log:

[Sep 06 14:50:31] Forking during indexing: /var/www/excelcoaching.com.br/htdocs/wp-content/cache/object/4ed/4af/4ed4af0fee8ea7b70be55028103f1deb.php
[Sep 06 14:50:31] Entered fork()
[Sep 06 14:50:33] Calling startScan(true)
[Sep 06 14:50:33] Got value from wf config maxExecutionTime: 40
[Sep 06 14:50:33] getMaxExecutionTime() returning config value: 40
[Sep 06 14:50:43] Test result of scan start URL fetch: WP_Error::__set_state(array( ‘errors’ => array ( ‘http_request_failed’ => array ( 0 => ‘cURL error 28: Resolving timed out after 10514 milliseconds’, ), ), ‘error_data’ => array ( ), ))
[Sep 06 14:50:44] Starting cron via proxy at URL https://noc1.wordfence.com/scanp/excelcoaching.com.br/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&scanMode=custom&cronKey=0863f66ace0ff5b7cba4a52dceafcfb0
[Sep 06 14:50:45] Scan process ended after forking.
[Sep 06 14:58:49] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=39aa4c568e590239b346e986ebdd55a65c7fb0599f29a08dfd25cf8764bae30906be4d6951cd3ee5071820028a9d21fa4ddf74858882efad22a05451cd8ac258661517d0fff57aebbaeda87fb9430a03&s=eyJ3cCI6IjUuMS4xIiwid2YiOiI3LjQuMCIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC9leGNlbGNvYWNoaW5nLmNvbS5iciIsInNzbHYiOjI2OTQ4ODE5MSwicHYiOiI3LjAuMzMtMTErMH4yMDE5MDkwMi4xOStkZWJpYW44fjEuZ2JwZDA1YzdlIiwicHQiOiJmcG0tZmNnaSIsImN2IjoiNy4zOC4wIiwiY3MiOiJPcGVuU1NMXC8xLjAuMXQiLCJzdiI6Im5naW54XC8xLjEzLjgiLCJkdiI6IjEwLjEuMzgtTWFyaWFEQi0xfmplc3NpZSJ9&betaFeed=0&action=plugin_vulnerability_check
[Sep 06 14:58:56] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=39aa4c568e590239b346e986ebdd55a65c7fb0599f29a08dfd25cf8764bae30906be4d6951cd3ee5071820028a9d21fa4ddf74858882efad22a05451cd8ac258661517d0fff57aebbaeda87fb9430a03&s=eyJ3cCI6IjUuMS4xIiwid2YiOiI3LjQuMCIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC9leGNlbGNvYWNoaW5nLmNvbS5iciIsInNzbHYiOjI2OTQ4ODE5MSwicHYiOiI3LjAuMzMtMTErMH4yMDE5MDkwMi4xOStkZWJpYW44fjEuZ2JwZDA1YzdlIiwicHQiOiJmcG0tZmNnaSIsImN2IjoiNy4zOC4wIiwiY3MiOiJPcGVuU1NMXC8xLjAuMXQiLCJzdiI6Im5naW54XC8xLjEzLjgiLCJkdiI6IjEwLjEuMzgtTWFyaWFEQi0xfmplc3NpZSJ9&betaFeed=0&action=theme_vulnerability_check
[Sep 06 15:00:16] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=39aa4c568e590239b346e986ebdd55a65c7fb0599f29a08dfd25cf8764bae30906be4d6951cd3ee5071820028a9d21fa4ddf74858882efad22a05451cd8ac258661517d0fff57aebbaeda87fb9430a03&s=eyJ3cCI6IjUuMS4xIiwid2YiOiI3LjQuMCIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC9leGNlbGNvYWNoaW5nLmNvbS5iciIsInNzbHYiOjI2OTQ4ODE5MSwicHYiOiI3LjAuMzMtMTErMH4yMDE5MDkwMi4xOStkZWJpYW44fjEuZ2JwZDA1YzdlIiwicHQiOiJmcG0tZmNnaSIsImN2IjoiNy4zOC4wIiwiY3MiOiJPcGVuU1NMXC8xLjAuMXQiLCJzdiI6Im5naW54XC8xLjEzLjgiLCJkdiI6IjEwLjEuMzgtTWFyaWFEQi0xfmplc3NpZSJ9&betaFeed=0&action=resolve_ips
[Sep 06 15:00:16] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=39aa4c568e590239b346e986ebdd55a65c7fb0599f29a08dfd25cf8764bae30906be4d6951cd3ee5071820028a9d21fa4ddf74858882efad22a05451cd8ac258661517d0fff57aebbaeda87fb9430a03&s=eyJ3cCI6IjUuMS4xIiwid2YiOiI3LjQuMCIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC9leGNlbGNvYWNoaW5nLmNvbS5iciIsInNzbHYiOjI2OTQ4ODE5MSwicHYiOiI3LjAuMzMtMTErMH4yMDE5MDkwMi4xOStkZWJpYW44fjEuZ2JwZDA1YzdlIiwicHQiOiJmcG0tZmNnaSIsImN2IjoiNy4zOC4wIiwiY3MiOiJPcGVuU1NMXC8xLjAuMXQiLCJzdiI6Im5naW54XC8xLjEzLjgiLCJkdiI6IjEwLjEuMzgtTWFyaWFEQi0xfmplc3NpZSJ9&betaFeed=0&action=resolve_ips
[Sep 06 15:00:27] Call to Wordfence API to resolve IPs failed: There was an error connecting to the Wordfence scanning servers: cURL error 28: Resolving timed out after 10524 milliseconds
[Sep 06 15:04:03] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=39aa4c568e590239b346e986ebdd55a65c7fb0599f29a08dfd25cf8764bae30906be4d6951cd3ee5071820028a9d21fa4ddf74858882efad22a05451cd8ac258661517d0fff57aebbaeda87fb9430a03&s=eyJ3cCI6IjUuMS4xIiwid2YiOiI3LjQuMCIsIm1zIjpmYWxzZSwiaCI6Imh0dHBzOlwvXC9leGNlbGNvYWNoaW5nLmNvbS5iciIsInNzbHYiOjI2OTQ4ODE5MSwicHYiOiI3LjAuMzMtMTErMH4yMDE5MDkwMi4xOStkZWJpYW44fjEuZ2JwZDA1YzdlIiwicHQiOiJmcG0tZmNnaSIsImN2IjoiNy4zOC4wIiwiY3MiOiJPcGVuU1NMXC8xLjAuMXQiLCJzdiI6Im5naW54XC8xLjEzLjgiLCJkdiI6IjEwLjEuMzgtTWFyaWFEQi0xfmplc3NpZSJ9&betaFeed=0&action=plugin_vulnerability_check
[Sep 06 15:04:13] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=39aa4c568e590239b346e986ebdd55a65c7fb0599f29a08dfd25cf8764bae30906be4d6951cd3ee5071820028a9d21fa4ddf74858882efad22a05451cd8ac258661517d0fff57aebbaeda87fb9430a03

Viewing 1 replies (of 1 total)

WFGerroald
(@wfgerald)

6 years, 11 months ago

Hey @alanaguiar,

I can help debug the scan issue. But more importantly, it looks like the site has been compromised. I suggest changing all passwords including WordPress, sFTP, database, and hosting control panel.

The guide below may help you clean the site. If you’re not comfortable with this or the infection returns I’d suggest reaching out to a hack repair service to clean the site and patch the point of entry.

https://www.wordfence.com/docs/how-to-clean-a-hacked-wordpress-site-using-wordfence/

Regarding the scan issue, can you send me a Diagnostics report so I can get a better overview of your environment? Please navigate to Wordfence > Tools > Diagnostics. Here you can select SEND REPORT BY EMAIL. Please include your WordPress.org username and update this thread after you’ve sent it.

Thanks,

Gerroald

Viewing 1 replies (of 1 total)

The topic ‘Error Scan’ is closed to new replies.