Make Quic Cloud block all IP addresses on development site

no , that won’t work , the QC IPs are auto-added in allow list

assuming you have correctly set up the use client ip in header

use rewrite rule to block all other IPs except yours , e.g.

RewriteCond %{REMOTE_ADDR} !123\.123\.123\.123
RewriteRule .* - [F,L]

so in above rule , assuming your IP is 123.123.123.123, then every other IP’s request will be denied

Hello and thank you for your response!

-How do I correctly set up the use client ip in header ?

-Should I put the rewrite rule at the top of the .htaccess file?

Thank you!

• This reply was modified 2 months, 3 weeks ago by hans410947.

this option: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:config:show-real-ip-behind-cloudflare , need to set to trusted ip only

and yes, put it at top of htaccess

Hello and thank you for your reply.

The link you posted takes me to LiteSpeed WebServer.

Maybe I misunderstand something, but I am using the LiteSpeed WordPress plugin together with Quic Cloud cloud services and CDN.

I have followed this doc to connect my staging site to Quic Cloud: https://docs.quic.cloud/cdn/devsite/ I added an A-record for the dev-site in the DNS zone at Quic Cloud.

I have also regenerated the Domain key in Litespeed plugin, and then connected to QC, so that I now have 2 domains in Quic Cloud: the main domain and the staging site.

But I can not find the table that is in your link anywhere, so I don′t know how to access “use client ip in header”

are you running on shared hosting or your own server ?

I am on shared hosting.

I have a WordPress Woocommerce site on a shared hosting, I am using the Litespeed cache plugin on the site, and I have connected the site to Quic Cloud using Domain key and CDN auto setup.

• This reply was modified 2 months, 3 weeks ago by hans410947.

then you probably not need to do that step that your provider should have already done it

You mean I dont need to do the step “correctly set up the?use client ip in header“?

So i I should just go ahead and add the rewrite rule in .htaccess?

yes, no need to that use client ip header thign , and place the rue in htaccess make sure you update the IP to your own IP instead of my example IP

Thank you very much, it is working now!

The Crawler can not find the sitemap after adding the rewrite rule. Does the crawler have it′s own IP address that I can add to the code to allowlist it?

yes, the crawler will probably use the server’s public IP , you may need to add that into the rule as well.

Perfect, that worked, thank you very much!