Search results

I am not sure how aapanel's setup, if they can support SSL for the panel, then it should also work with the phpmyadmin. At least, I tried it on CyberPanel + OLS, and it works fine, it's not an OLS issue, but how they configure it.

Not as I know.

Good to know you have fixed the issue.

I see, that sounds like an HTML code issue. Is it possible to share that code here and maybe someone here can help you?

What if you create a static context like the attached file, and let us know if it works?

Hi, I don't think OLS supports AllowEncodedSlashes NoDecode feature.

ok. For Ubuntu 22.04, it should be xxx jammy main instead of xxx noble main.

Hi, I don't think the OLS app context supports ASGI, but you could set up a reverse proxy to the App in this case.

Hi, OpenliteSpeed supports phpmyadmin and SSL if you configure it in the right way, but the screenshot you shared is not OpenLiteSpeed.

1. no, it does not. You might need to restart the lsnode process after the code change by kill. 2. Use static context. 3. If you want to setup websocket proxy(which you should no need since you are using app ocntext), please check...

What's the output with the following command? cat /etc/apt/sources.list.d/lst_debian_repo.list Does it help if you install the LiteSpeed Repository again? https://docs.openlitespeed.org/installation/repo#install-the-litespeed-repository

You can create a conf file for it, and include it in the httpd_config.conf file. See https://openlitespeed.org/kb/ols-configuration-examples/#Include_Files

That's a known warning, please ignore it for now, it should not cause any issues.

Thanks, I will forward it to the package build master.

Please check lsrestat.log, to get some idea of what happened. A graceful restart must be completed before issuing another one. 1. Avoid using systemctl stop lsws or systemctl start lsws, use Always use "systemctl restart lsws" only, otherwise it may break the graceful restart. 2. Avoid...

My OLS WP docker test server works fine with QC. Maybe something blocked the API in your stack. For further help with the QUIC.cloud, please raise a ticket on https://quic.cloud/support

Thanks, I don't see any symbolic links(the ln command should generate a link for it). Like this cgi-bin -> /usr/lib/cgi-bin

What's the output with the following command, ls -al /home/example.com/public_html/

I think this part is purely a WordPress configuration issue, and not caused by OpenLiteSpeed. Here's another guide that you might want to take a look at and see if it's easier to config...

I am a little bit confused, you are using nginx to serve wordpress already, so why and how to use ols-docker-env solution with the existing stack? Have you checked the .htaccess file? What's the .htaccess content?