Passing real IP to chat application on cpanel server with Litespeed + Cloudflare
Budget: $10 – $30 USD
Hello,
We have a cPanel server running litespeed webserver and also uses Cloudflare for DDoS protection. When litespeed is enabled our chat application does not work. When we switch to apache it works fine.
We've already enabled Use Client IP in Header in the Litespeed settings. We've also added all the Cloudflare IP tanges to the trusted IP list.
We need someone that can locate the issue and either make adjustments on the server without disabling litespeed or editing the chat application code to read the IP forwarded from Cloudflare.
I found this additional information which might be helpful:
It occurs when the user's IP cannot be verified.
When creating a user code, IP information of the user identified by the web server where the mini-talk client is installed is included.
This occurs when the IP information is different from the IP of the user accessing the mini-talk server.
The mini-talk server supports IPv4 only, and if the web server supports IPv6, the IP included in the user code may be recorded as IPv6.
If IPv6 is not essential, it can be solved by turning off IPv6 support on the web server and enabling IPv4 support only.
Alternatively, it can also occur if the cloud flare IP or the IP of the L4 equipment is recorded in the user code, not the user's actual IP, on a web server with a mini-talk client installed, such as cloud flare or L4 equipment.
The GetClientIp() function exists in the /classes/functions.php file of the mini-talk client, and please check whether the return value of this function is the user's actual IP.
If an IP other than the user's actual IP is printed, please modify it so that the user's actual IP can be recorded in the user code using a variable that can check the user's actual IP on the web server you use ($_SERVER[HTTP_X_FORWARDED_FOR, etc.).
We have a cPanel server running litespeed webserver and also uses Cloudflare for DDoS protection. When litespeed is enabled our chat application does not work. When we switch to apache it works fine.
We've already enabled Use Client IP in Header in the Litespeed settings. We've also added all the Cloudflare IP tanges to the trusted IP list.
We need someone that can locate the issue and either make adjustments on the server without disabling litespeed or editing the chat application code to read the IP forwarded from Cloudflare.
I found this additional information which might be helpful:
It occurs when the user's IP cannot be verified.
When creating a user code, IP information of the user identified by the web server where the mini-talk client is installed is included.
This occurs when the IP information is different from the IP of the user accessing the mini-talk server.
The mini-talk server supports IPv4 only, and if the web server supports IPv6, the IP included in the user code may be recorded as IPv6.
If IPv6 is not essential, it can be solved by turning off IPv6 support on the web server and enabling IPv4 support only.
Alternatively, it can also occur if the cloud flare IP or the IP of the L4 equipment is recorded in the user code, not the user's actual IP, on a web server with a mini-talk client installed, such as cloud flare or L4 equipment.
The GetClientIp() function exists in the /classes/functions.php file of the mini-talk client, and please check whether the return value of this function is the user's actual IP.
If an IP other than the user's actual IP is printed, please modify it so that the user's actual IP can be recorded in the user code using a variable that can check the user's actual IP on the web server you use ($_SERVER[HTTP_X_FORWARDED_FOR, etc.).