IIS 10 – CloudFlare Proxy Reversing (mod_remoteip or mod_cloudflare)

cloudflarephpbb

I have a forum running on my website which is using phpBB, but all users on it have a CloudFlare IP. This is not ideal at all and I would like to fix it.

After running a Google search and spending about an hour trying to solve the problem, there seems to be no possible way to use 'mod_remoteip' for IIS. It is only for Apache server.

Moving on, I decided to try 'mod_cloudflare' (which CloudFlare says it is not recommended to use, but obviously I don't have any other options). However, I have no idea how to actually install this and use it. How do I get it added to phpBB? There seems to be a PHP script I need to add, but I honestly have no idea what file to add it to so it works on all of the phpBB forum.

Please don't also recommenced the phpBB plugin called 'Cloudflare unmasked IP'. It doesn't work at all. All IP's are still CloudFlare IP's.

Thanks.

Best Answer

You should be able to achieve this out of the box with IIS 10. Please refer to the following article https://support.cloudflare.com/hc/en-us/articles/200170786-How-do-I-correct-visitor-IP-with-Microsoft-IIS- (Webserver Instructions > Microsoft IIS section)

Related Solutions

Centos – apxs cannot install mod_cloudflare on centos

Fetch the RPM for your platform from https://www.cloudflare.com/resources-downloads: https://github.com/downloads/cloudflare/mod_cloudflare/mod_cloudflare-1.1.1-1.i586.rpm (32bit) and https://github.com/downloads/cloudflare/mod_cloudflare/mod_cloudflare-1.1.1-1.x86_64.rpm (64bit)

Install: rpm -ivh mod_cloudflare-1.1.1-1.*

Edit /etc/httpd/conf/httpd.conf

LoadModule cloudflare_module /usr/lib64/apache2/mod_cloudflare.so
<IfModule mod_cloudflare.c>
    CloudFlareRemoteIPHeader CF-Connecting-IP
    CloudFlareRemoteIPTrustedProxy 204.93.240.0/24 204.93.177.0/24 199.27.128.0/21 173.245.48.0/20 103.22.200.0/22 141.101.64.0/18 108.162.192.0/18
    #DenyAllButCloudFlare
</IfModule>

On 32bit change lib64 to lib

Nginx – Issue varnish purge through CloudFlare to Varnish

Your problem is that the purge request is being handled by ClodFlare instead of Varnish.

Keep in mind that:

In Varnish 3 you should be using purge; instead of set obj.ttl = 0s;
Varnish will resolve the object using vcl_hash. In Varnish 3 this means, by default [1], that the req.url will be used along with HTTP "Host" header or, if not present, the server IP:
```
sub vcl_hash {
  hash_data(req.url);
  if (req.http.host) {
    hash_data(req.http.host);
  } else {
    hash_data(server.ip);
  }
  return (hash);
}
```
You can override vcl_hash to match your needs

Please take a look at the documentation [2] and Varnish Book info [3] on Bans & Purges

In my opinion you have to options:

Issue the purges directly to Varnish circumventing CloudFlare, directly using curl -H "Host: _host_wich_has_the_url_to_purge" -X PURGE http://_varnish_ip_:_varnish_port/_url_to_purge_
Try to add the CloudFlare IP ranges to your acl purge (not recommended) and instruct CloudFlare to pass such requests to Varnish.

[1] https://www.varnish-cache.org/docs/3.0/reference/vcl.html#examples

[2] https://www.varnish-cache.org/docs/3.0/tutorial/purging.html

[3] https://www.varnish-software.com/static/book/Cache_invalidation.html#removing-a-single-object

Best Answer

Related Solutions

Centos – apxs cannot install mod_cloudflare on centos

Nginx – Issue varnish purge through CloudFlare to Varnish

Related Topic