OpenLiteSpeed 1.7.19 on CentOS – Large Images Failing to Load

[MarcAtHemsol]

Hi community,

We're experiencing an issue with OpenLiteSpeed 1.7.19 on a CentOS-based environment where large images fail to load properly. The server sends only a few kilobytes before closing the connection. However, when accessing the application directly via IP (bypassing the proxy), large images load correctly.

Setup:
Our LSWS configuration proxies requests to a Docker container:

context / {
    type proxy
    handler Backend
    addDefaultCharset off
}

extprocessor Backend {
    type proxy
    address my_docker_ip:port
}

Troubleshooting Steps:

1. Configuration Check: We initially suspected a misconfiguration but found that replicating the same setup (with the same configuration) on a local machine (without CentOS) resulted in proper image loading.
2. Bandwidth Simulation: We applied request throttling to simulate low bandwidth, but images were still returned correctly.
3. Firewall & Logs: No anomalies found in firewall settings or logs.
4. Network Settings: We adjusted values like net.core.rmem_max, net.core.wmem_max, net.ipv4.tcp_window_scaling, and net.ipv4.tcp_mtu_probing, but the issue persists.
5. Hosting Provider: We’ve observed significant packet loss on this VPS, raising concerns about a potential network issue outside our control.

Before considering a hosting provider change, we’d appreciate any insights from those who have encountered similar issues. Could this be a bug in OpenLiteSpeed 1.7.19 on CentOS when running it as a proxy? Are there additional troubleshooting steps you’d recommend?

Thanks in advance for any advice!

 

[MarcAtHemsol]

It was the firewall, but it did not log any entries.. you can delete this post!

 

[Cold-Egg]

Glad to know you have found the issue. We can keep it, in case other users hit the same issue.

 

[MarcAtHemsol]

Ok! I can also add that it was not the firewall. After you change net.core.rmem_max, net.core.wmem_max, net.ipv4.tcp_window_scaling, and net.ipv4.tcp_mtu_probing you must also restart the container hehe