Search results

Check if your OLS HTTP listener has mapped the virtual host and domain. See https://docs.openlitespeed.org/config/#map-virtual-hosts for more information.

Not as I know since PHP83 has been released and is quite popular now. If you think it's a bug, please submit the issue to bug@litespeedtech.com with the details, so the dev team can help to take a look at the issue.

Should be in this month if there are no further issues.

The next release should be 1.8.x instead of 1.7. If there's a new update available, and you run the yum update, then it should revert back to v1.7.x Thanks, we just have it updated.

Good to know it works. Context with regular expression has higher priority.

Please try to disable the "context exp:^.*" and see if it helps. Since OLS has browser cache enabled by default, you don't need to add that context.

Hi, Is it possible to share the vh config here, you can PM me if you want to keep it private.

Thanks @airween, I will share the info with the team.

Nice. The new v1.8.2 package should be published in the following few days.

For the current instance, simply run an apt update, and an apt upgrade should be sufficient. Upgrading the OS might lead to some unexpected issues that you'll need to address." If you want to use the new instance, you can launch it, and then migrate the sites from the old server.

I've tested it and it works. :)

No problem.

@gamingtips Could you try the latest build and let us know if it works? /usr/local/lsws/admin/misc/lsup.sh -b -v 1.8.2

Hi, The Deployment Manager feature is deprecated and no longer supported by GCP, so we have to use Terraform as the only deployment method for GCP. See https://cloud.google.com/marketplace/docs/partners/vm/configure-dm-deployment for more information By the way, the new image was built with...

Based on the OLS developers' review, it appears that the issue is related to the new ModSecurity library. As a result, we will be releasing a new v1.8.2 OLS package that includes the previous ModSecurity library.

Then I guess you are using the DA control panel? When the config file identifies an include, the web admin will switch to read-only mode, which is intentional.

Do you use any "include" in the config file?

Happy to help. (y)

To make ftpuser to have permission access the document root. You could add the ftpuser to the www-data group. If you really want to implement umask globally, please check this post.

Hi, I've checked the report, but it won't include any debug log. Could you submit the issue to support@litespeedtech.com, we might ask you for temporary wp-admin access from there?