>>A problem can only exist if you use whatever function to limit the access by checking the IP address or to a specific source. The function to limit the access is often provided by hosting providers, so it is always recommended to check if IPs are whitelisted if any errors occures to receive the domain key.
I just use quic.cloud for compressing images and converting them to webp. It works AOK on staging and production. If I run into any troubles in the future, I'll look into whitelisting - thanks.
>>If you use www.a.example.com for production domain and www.b.example.com for staging domain then you can't expect that the key is a universal domain key, so you caused the issue by yourself by misunderstanding. A key implies that it is unique for each domain.[/QUOTE]
I make lots of mistakes - I even started by pointing out that I made a mistake. That's not the issue for me. What is is being able to use quic.cloud for my purpose - compressing and optimizing images. It does this, and I can see that it does so in my media library. So, as I said before - for my purposes, whitelisting was not required. Other cases may differ.
But, I do like to use best practices - and you seem pretty concerned about whitelisting. In that case, how would you suggest I do it? I have runcloud.io and the 8G firewall from Perishable press - there's an area for IP whitelisting in Runcloud. But then I also have access to the litespeed config file. Which places would you suggest I do it?
Thanks.
