Denis

Solved, it was caused by a bug in the theme.

Hi Peter,

Thank you. I asked my host again, here is his reply:

We were aware of an intermittent issue and assumed this was the same case.

But it was not. This time, their IPs were greylisted by our firewall, Imunify360. Imunify360 usually does not block WordFence IPs.

If you still have the ticket opened with them, ask them to contact Imunify360 and report the issue.

Meanwhile, we have removed the block from our server. You should now be able to install it.

Here is the cURL report:

# curl -v https://noc1.wordfence.com/

*   Trying 52.25.185.95...
* TCP_NODELAY set
* Connected to noc1.wordfence.com (52.25.185.95) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, [no content] (0):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=noc1.wordfence.com
*  start date: May 12 00:00:00 2024 GMT
*  expire date: Jun 11 23:59:59 2025 GMT
*  subjectAltName: host "noc1.wordfence.com" matched cert's "noc1.wordfence.com"
*  issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M02
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.3 (OUT), TLS app data, [no content] (0):
* TLSv1.3 (OUT), TLS app data, [no content] (0):
* TLSv1.3 (OUT), TLS app data, [no content] (0):
* Using Stream ID: 1 (easy handle 0x55d80a3016f0)
* TLSv1.3 (OUT), TLS app data, [no content] (0):
> GET / HTTP/2
> Host: noc1.wordfence.com
> User-Agent: curl/7.61.1
> Accept: */*
> 
* TLSv1.3 (IN), TLS handshake, [no content] (0):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS app data, [no content] (0):
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* TLSv1.3 (OUT), TLS app data, [no content] (0):
* TLSv1.3 (IN), TLS app data, [no content] (0):
< HTTP/2 200 
< date: Fri, 14 Mar 2025 15:06:29 GMT
< content-type: text/plain
< content-length: 108
< server: nginx
< x-frame-options: SAMEORIGIN
< x-xss-protection: 1; mode=block
< x-content-type-options: nosniff
< strict-transport-security: max-age=31536000; includeSubDomains
< 
* TLSv1.3 (IN), TLS app data, [no content] (0):
* Connection #0 to host noc1.wordfence.com left intact

As far as my case, I will mark this topic as closed. It was caused by my server, not WordFence.

Update. I was wrong about the x-litespeed-cache: bkd header coming from the cache warmer, it was ‘bkd’ since the visit-made cache was removed from the CDN PoP after 24 hours.

So in my case the cache crawler is unfortunately still not creating a cache copy on my Litespeed server. I’ve send all the website info to your e-mail @tmmtechnology. I would really appreciate if you could take a look!

Thank you for the replies!

>In Cache Warmer settings > Schedule, scrolling is disabled/not working (?)

I see, I didn’t know that the page length would impact the scrolling of the WP navigation menu.

What about the speed limit thing, it says “Max pages to visit per minute” but the warmer takes couple hour a ‘pause’ when it hits that limit?

As for the cache: miss, How do I check if I got served a cached page created by the Cache Warmer? There is no extra header added with this plugin, right? After the warmer is completed the pages don’t seem to load any faster.