@Paul_M

[X-or]

Can you please make this product available again
https://vborg.vbsupport.ru/showthread.php?t=231873
Proxy to Real IP Conversion

This modification has been withdrawn.
vBulletin 4.0.x and 4.1.x are no longer supported.
For vBulletin 4.2.x please use the built in reverse proxy detection.

Problem the built in vbulletin reverse proxy detection is based on a list of IP to reverse
So if there are hundreds thousands IP to reverse the server will search for a match whenever any user does anything, and I'm afraid that's certain death for the server

So please make your product available again.

[Paul M]

Sorry, but thats not going to happen.

However, as of 4.2.3 a couple of new options were added to the core to help in this case.

/* Enter your known proxy servers here. You can list multiple trusted IPs separated by a comma.
You can also use the * wildcard (at the end of a definition only) or use the keyword 'all' to represent any ip address.*/
//$config['Misc']['proxyiplist'] = '127.0.0.1, 192.168.*, all';

Also, in 4.2.4 an extra fix was added due to PHP sometimes not passing the custom headers into the $_SERVER array (which stopped the system working).

[X-or]

wow, completely missed this as I took the bad habit of not updating the config file anymore :O

thank you, works fine

[TheLastSuperman]

Originally Posted by X-or

wow, completely missed this as I took the bad habit of not updating the config file anymore :O

thank you, works fine

Always update the config.php file using config.php.new, just copy/paste the values then save and overwrite . In some cases issues can arise form using an older config.php file.

[SuperTaz]

Originally Posted by Paul M

Sorry, but thats not going to happen.

However, as of 4.2.3 a couple of new options were added to the core to help in this case.

/* Enter your known proxy servers here. You can list multiple trusted IPs separated by a comma.
You can also use the * wildcard (at the end of a definition only) or use the keyword 'all' to represent any ip address.*/
//$config['Misc']['proxyiplist'] = '127.0.0.1, 192.168.*, all';

Also, in 4.2.4 an extra fix was added due to PHP sometimes not passing the custom headers into the $_SERVER array (which stopped the system working).

Cloudflare gave their IP ranges. Should we enter them as they are shown here even with the /## on the end?

103.21.244.0/22
103.22.200.0/22
103.31.4.0/22
104.16.0.0/12
108.162.192.0/18
131.0.72.0/22
141.101.64.0/18
162.158.0.0/15
172.64.0.0/13
173.245.48.0/20
188.114.96.0/20
190.93.240.0/20
197.234.240.0/22
198.41.128.0/17
199.27.128.0/21

[Paul M]

Nope, CIDR format wont work at all.

If you want to restrict it to ranges, you would have to figure out what ranges they represent, and add them.

[SuperTaz]

So will it work with this format?

$config['Misc']['proxyiplist'] = '131.0.72.0 - 131.0.75.255, 103.22.200.0 - 103.22.203.255, all';

[BirdOPrey5]

If using Apache web server use mod_cloudflare - https://support.cloudflare.com/hc/en...flare-Packages

[Paul M]

Originally Posted by SuperTaz

So will it work with this format?

$config['Misc']['proxyiplist'] = '131.0.72.0 - 131.0.75.255, 103.22.200.0 - 103.22.203.255, all';

The config file tells you what format will work, please read it.

[X-or]

Simply use this
$config['Misc']['proxyiplist'] = 'all';