Closed mylesagnew closed 5 years ago
Thanks @mylesagnew,
I use CloudFlare primarily for caching performance when I use it.
I turn off/lower their firewall rules like this:
For me, this wasn't out of compatibility with crawling with WP2Static, but that when I travel especially, I get CloudFlare security warning pages. For me, it's not worth it to have false-positives showing users a scary error page.
I cannot really advise you what settings to choose, but just providing my own reasoning. I prefer to use http basic auth for WordPress sites when they're being used for static publishing. I'd put some IP whitelisting on if it were only myself or a corporate office accessing the dev site.
I'll close this and reference it / add to the documentation and troubleshooting sections (already should be a note on CloudFlare)
ifconfig
on the server? Server IP's are whitelist both IPV4 and V6 I will double check in the configuration rules on Cloudflare.
it would be nice if the plugin could alternately crawl on an internal address. for UI based crawls, it could work, ie where wp-config.php sets the Site URL and Home via $_SERVER['HTTP_HOST']
, but not for WP-CLI, where this isn't available... Bypassing CloudFlare or even just https could speed up the crawls quite a bit...
I'll make a new task to attempt a solution to this, but not likely to have it ready in the next month
When converting a site from WP to Static HTML the conversion process appears to use external IP or resource to do the scan.
https://www.dropbox.com/s/whfxnngyo5fhlyb/2019-01-29_17-24-57.png?dl=0