Update: It seems everytime the lsphp child process is terminated by OLS -
2023-07-16 21:24:57.082381 [NOTICE] [120009] [lsphp81] Send SIGTERM to process [139211].
I am getting a mariadb error. This started only on the newest version of lsws. It has nothing to do with timeouts.
2023-07-16...
I got it to work. You have to run an ipv4 listener and ipv6 listener both on OLS. Your cloudflare entries need an A entry and AAAA entry. Then cloudflare will prioritize ipv4 over ipv6.
I have the ipv6 listener on. I have cloudflare DNS AAAA entry pointing to my servers ipv6 address. However the site just won't load over ipv6 when behind cloudflare. I can access the site using the ipv6 address directly so i guess the listener is working.
After several months testing
I believe I found the error with the help of chatgpt – OLS has something wrong with the logic in managing lsphp connections (closing child lsphp connections to MariaDB). It’s trying to ‘kill” processes which are already closed. I believe this can cause MariaDB...
The listeners have a way to bind to a process, would that work? I see you can bind a listener to process 1 - 8
Binding: Specifies which lshttpd child process the listener is assigned to. Different child processes can be used to handle requests to different listeners by manually associating a...
I had someone from the litespeed team show me the ipv6 listener would work for both ipv6 and ipv4. But I setup a ipv6 listener and checked netstat and it does not seem to work for ipv4.
Am I supposed to run a 2 separate listeners for ipv6 and ipv4?
Cold-egg is correct. If client has both ipv4...
I had been speaking to someone on your team before getting ghosted. He had shown me that using the IPV6 Listener would support both ipv6 and ipv4. I found this to be untrue as I setup a fresh ipv6 listener on two servers and they according to netstat it was only listening to ipv6, which is...
I have a very strange problem with OLS. Everytime my wordpress site needs updates it says Files could not be installed due to likely permission errors.
Nothing fixes the problem unless I go ssh in and do the following command
sudo chown -R nobody:nogroup /usr/local/lsws/Example/html/wordpress...