Title: Will's Replies | WordPress.org

---

# Will

  [  ](https://wordpress.org/support/users/willbeing/)

 *   [Profile](https://wordpress.org/support/users/willbeing/)
 *   [Topics Started](https://wordpress.org/support/users/willbeing/topics/)
 *   [Replies Created](https://wordpress.org/support/users/willbeing/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/willbeing/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/willbeing/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/willbeing/engagements/)
 *   [Favorites](https://wordpress.org/support/users/willbeing/favorites/)

 Search replies:

## Forum Replies Created

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

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Scan Stage Failed – Scan process ended after forking – AWS Bitnami Cloudflare](https://wordpress.org/support/topic/scan-stage-failed-scan-process-ended-after-forking-aws-bitnami-cloudflare/)
 *  Thread Starter [Will](https://wordpress.org/support/users/willbeing/)
 * (@willbeing)
 * [2 years, 8 months ago](https://wordpress.org/support/topic/scan-stage-failed-scan-process-ended-after-forking-aws-bitnami-cloudflare/#post-17136702)
 * Also, we’re using QueryMonitor plugin, and it shows the following PHP error when
   navigating the site or backend:
 *     ```wp-block-code
       chmod(): Operation not permitted	
       /bitnami/wordpress/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:442
       ```
   
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Scan Stage Failed – Scan process ended after forking – AWS Bitnami Cloudflare](https://wordpress.org/support/topic/scan-stage-failed-scan-process-ended-after-forking-aws-bitnami-cloudflare/)
 *  Thread Starter [Will](https://wordpress.org/support/users/willbeing/)
 * (@willbeing)
 * [2 years, 8 months ago](https://wordpress.org/support/topic/scan-stage-failed-scan-process-ended-after-forking-aws-bitnami-cloudflare/#post-17136617)
 * Hi [@wfpeter](https://wordpress.org/support/users/wfpeter/),
 * Thanks for the help. I re-whitelisted WF IPs (I can’t seem to find the link to
   current WF IPs, but it was from one of your responses here in the Forum)
 * I reset permissions according to [Bitnami’s recommendations](https://github.com/bitnami/vms/issues/22#issuecomment-1143906974).
   This fixed the `wp_remote_post()` issue.
 * Regarding my site IPs, the _IP(s) used by this server_ listed in **WF > Tools
   > Diagnostics **are different than our server’s static public IP. Seems strange.
   Regardless, we whitelisted those two IP addresses, too.
 * Changing _max\_execution\_time_ did not have any change.
 * Sort of related:
 * We have a duplicate WordPress instance on a subdomain. After performing the same
   permission changes, it still shows a Connectivity error below. Note: the Tools
   > Diagnostics page takes a long time to load.
 *     ```wp-block-code
       Connecting back to this site via IPv6 (not required; failure to connect may not be an issue on some sites) (opens in new tab)
       wp_remote_post() test back to this server failed! Response was: cURL error 28: Failed to connect to seo.oneoption.com port 443: Connection timed out
       ```
   
 * It cannot scan and has similar logs:
 *     ```wp-block-code
       [Oct 19 12:13:48:1697732028.589443:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=95c6edbe9ff64cf79a73a4078bb1b86d2b4c72f6315871ace35d7d880d6c19ec4167ce699252bd162802d39319f43bfec4a26ef13fb8ec1808ae20981a9deec9&s=eyJ3cCI6IjYuMy4yIiwid2YiOiI3LjEwLjQiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvc2VvLm9uZW9wdGlvbi5jb20iLCJzc2x2IjoyNjk0ODgzNjcsInB2IjoiOC4yLjEwIiwicHQiOiJmcG0tZmNnaSIsImN2IjoiNy43NC4wIiwiY3MiOiJPcGVuU1NMXC8xLjEuMW4iLCJzdiI6IkFwYWNoZSIsImR2IjoiMTAuMTEuNS1NYXJpYURCIiwibGFuZyI6IiJ9&action=timestamp
       [Oct 19 12:00:17:1697731217.503367:4:info] Calling Wordfence API v2.26:https://noc1.wordfence.com/v2.26/?k=95c6edbe9ff64cf79a73a4078bb1b86d2b4c72f6315871ace35d7d880d6c19ec4167ce699252bd162802d39319f43bfec4a26ef13fb8ec1808ae20981a9deec9&s=eyJ3cCI6IjYuMy4yIiwid2YiOiI3LjEwLjQiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvc2VvLm9uZW9wdGlvbi5jb20iLCJzc2x2IjoyNjk0ODgzNjcsInB2IjoiOC4yLjEwIiwicHQiOiJmcG0tZmNnaSIsImN2IjoiNy43NC4wIiwiY3MiOiJPcGVuU1NMXC8xLjEuMW4iLCJzdiI6IkFwYWNoZSIsImR2IjoiMTAuMTEuNS1NYXJpYURCIiwibGFuZyI6IiJ9&action=timestamp
       [Oct 19 11:52:12:1697730732.454230:4:info] Scan process ended after forking.
       [Oct 19 11:52:12:1697730732.446605:1:error] Scan Engine Error: The signature on the request to start a scan is invalid. Please try again.
       [Oct 19 11:52:12:1697730732.445532:4:info] Verifying start request signature.
       [Oct 19 11:52:12:1697730732.444315:4:info] Scan engine received request.
       [Oct 19 11:52:12:1697730732.259967:4:info] Starting cron with normal ajax at URL https://seo.oneoption.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&scanMode=standard&cronKey=5f3e04bf6b743b5469d6de96d22aace0&signature=2ddbe46a3ad9ce0adc4069e3ab4fb594c85742f6d8101f1316d26c9eb6cfda3a
       [Oct 19 11:52:12:1697730732.256772:4:info] Test result of scan start URL fetch: array ( 'headers' => \WpOrg\Requests\Utility\CaseInsensitiveDictionary::__set_state(array( 'data' => array ( 'date' => 'Thu, 19 Oct 2023 15:52:12 GMT', 'server' => 'Apache', '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', 'referrer-policy' => 'strict-origin-when-cross-origin', 'x-frame-options' => 'SAMEORIGIN', 'vary' => 'Accept-Encoding', 'content-encoding' => 'gzip', 'content-length' => '32', 'content-type' => 'text/html; charset=UTF-8', ), )), 'body' => 'WFSCANTESTOK', 'response' => array ( 'code' => 200, 'message' => 'OK', ), 'cookies' => array ( ), 'filename' => NULL, 'http_response' => \WP_HTTP_Requests_Response::__set_state(array( 'data' => NULL, 'headers' => NULL, 'status' => NULL,
       [Oct 19 11:52:11:1697730731.991837:4:info] getMaxExecutionTime() returning config value: 20
       [Oct 19 11:52:11:1697730731.990790:4:info] Got value from wf config maxExecutionTime: 20
       [Oct 19 11:52:11:1697730731.986275:4:info] Entering start scan routine
       [Oct 19 11:52:11:1697730731.980677:2:info] Attempting to resume scan stage (0 attempt(s) remaining)...
       [Oct 19 11:50:12:1697730612.010795:4:info] Scan process ended after forking.
       ```
   
 * I even disabled Proxied Status on CloudFlare to see if it was causing the issue.
   No change.
 * I went ahead and Emailed a Diagnostic Report from both the top level domain and
   the subdomain.
 * Thanks again for your help!
 * Will
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Wordfence Security - Firewall, Malware Scan, and Login Security] Scan Stage Failed – Scan process ended after forking – AWS Bitnami Cloudflare](https://wordpress.org/support/topic/scan-stage-failed-scan-process-ended-after-forking-aws-bitnami-cloudflare/)
 *  Thread Starter [Will](https://wordpress.org/support/users/willbeing/)
 * (@willbeing)
 * [2 years, 8 months ago](https://wordpress.org/support/topic/scan-stage-failed-scan-process-ended-after-forking-aws-bitnami-cloudflare/#post-17134480)
 * We also tried to _Start all scans remotely (Try this if your scans aren’t starting
   and your site is publicly accessible)  _without any luck[](https://www.wordfence.com/help/?query=diagnostics-option-remote-scans)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Total Upkeep – WordPress Backup Plugin plus Restore & Migrate by BoldGrid] Could not reach the URL address. HTTP error: 405 (Not Allowed)](https://wordpress.org/support/topic/could-not-reach-the-url-address-http-error-405-not-allowed/)
 *  Thread Starter [Will](https://wordpress.org/support/users/willbeing/)
 * (@willbeing)
 * [3 years, 1 month ago](https://wordpress.org/support/topic/could-not-reach-the-url-address-http-error-405-not-allowed/#post-16787036)
 * Thanks, Brandon!
 * This is the destination transfer-archive.log:
 * [https://codeshare.io/8pQWO4](https://codeshare.io/8pQWO4)
 * This is the source backup-download.log:
 * [https://codeshare.io/Od1x7r](https://codeshare.io/Od1x7r)
 * Thanks for your help!
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Custom Post Type Permalinks] Custom Post Permalink w/o ID](https://wordpress.org/support/topic/custom-post-permalink-w-o-id/)
 *  Thread Starter [Will](https://wordpress.org/support/users/willbeing/)
 * (@willbeing)
 * [4 years, 1 month ago](https://wordpress.org/support/topic/custom-post-permalink-w-o-id/#post-15662253)
 * Update: The permalink structure: example.com/slug/%year%/%monthnum%/%day%/ seems
   to always go to an Archive page with the custom post we want to view listed. 
   We can never view the actual pst, however.
 * Thanks for your help!

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