Search results

There are no entries in `/usr/local/lsws/log/error.log` about the 404?

The latest package should account for these issues. Please let us know if they do not.

libxml is included in the common package: lsphp72-common

How do you have OLS installed via apt? If so you can just run `apt-get install ols-modsecurity` to install mod_security instead of compiling it.

Yes, as long as those files are not handled by WordPress it should be fine.

Not for OLS it doesn't, just for Enterprise.

The crawler feature was added in V1.4.29 and should be enabled by default with you just needing to enable it in WordPress.

Hello, they have already been released and you can find out how to install them via this link here: https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:php:apt

Hi @TexasGreg, I am unsure how Webmin does upgrades for packages installed by APT but when you run `sudo apt-get upgrade openlitespeed` it will prompt you if you want to overwrite your `httpd_config.xml` and `.htpasswd` file. Like the following: root@deb9-rpm:~# apt-get upgrade Reading package...

Did you check stderr.log? What code are you trying to run? Can you try the following: def application(environ, start_response): start_response('200 OK', [('Content-Type', 'text/plain')]) return ['Hello World!\n'] Save it as hello.wsgi and try to visit it?

The biggest difference between OLS and LSWS is the Apache compatibility. About stability is that we usually put new features inside of OLS first before LSWS and this can cause some bugs here and there. OLS does support HTTP/2 and everything with SSL, the only thing it does not support is QUIC...

You will want to setup the per vhost/domain SSL certificates under the Virtual Host. There should be an SSL tab under each Virtual Host that you will want to configure. The main Listener SSL is for the main SSL cert of the server, it can be one of the domains or a self signed certificate it does...

Please try running php directly ie /usr/local/lsws/lsphp71/bin/php bin/magento setup:static-content:deploy.

Please try the following command: `yum install lsphp72-json` then do a graceful restart of OLS and it should be working.

How did you install lsphp72?

You can try adding Max Idle time of about 15 seconds. This will kill off idle PHP processes after 15 seconds.

You will want to setup the main SSL Cert on the listener, this can be a self signed or trusted certificate. Then under each VHOST, there is an SSL tab to specify the location for the domain/vhost specific SSL certificates. Then under the SSL Listener map the vhost and domain to that listener...

1.4.29 has been released. If you used an RPM you can update it via yum update or you can compile from source.

Is there any info in the Error Log?

For each OLS process you have it will spawn a main LSPHP process for each account. At which point it will spawn up-to how many children you specified.