Search results

Hi Pete, Protect the CyberPanel should be good enough since you access the phpmyadmin via the Cyberpanel. Here are the steps: 1. Remove the CyberPanel port, follow https://community.cyberpanel.net/t/how-to-remove-port-8090-from-cyberpanel/30648 2. Create realm protection, follow...

@azlitesp Just published, please confirm if it works.

Ubuntu 9? Anyway, I have forwarded your request and hope we can restore the old image in the next few days.

Could you share some example rules?

No need to delete it, probably a firewall somewhere that you need to allow port 7080. It could be on the network level or system level. Form my point of view, no difference to the web server.

Glad to know it works now.

OpenLiteSpeed process runs as nobody(in nogroup group) user, so we usually set 750 to the document root folder and owned by the [virtual host user]:[nogroup], so the web server has permission to access it.

Is it a WSL system? To fix that error message, you can try following this post, https://superuser.com/questions/1539972/wget-error-bash-windows-subsystem-for-linux

If you can curl it via localhost or 127.0.0.1 from the same server, then it means a firewall issue somewhere.

Correct, for CyberPanel server, you need to control the PHP via the control panel, not updating the config manually through the console. For the IncScheduler issue, please upgrade the Cyberpanel to fix it. Similar issue can be found here...

--update can not be used with other parameters. Please try this, bash <( curl -k https://raw.githubusercontent.com/litespeedtech/ols1clk/master/ols1clk.sh ) --update bash <( curl -k https://raw.githubusercontent.com/litespeedtech/ols1clk/master/ols1clk.sh ) -w --wordpressplus wp.local --lsphp 82

What's your document root's permission? e.g. 755, 750?

Hi @azlitesp The OpenLiteSpeed WordPress image is still on the Azure Marketplace, see https://azuremarketplace.microsoft.com/en-us/marketplace/apps/litespeedtechnologies.openlitespeed-wordpress The image built with Ubuntu 20.04 (with gen1)has been outdated and may have some security concerns...

No problem.

Create an access control config file, and include it in any virtual host you want. Or set it on the server level, web admin > Security > Access Control, this will apply to all the websites.

The OLS v1.8.0 package will be ready and pushed to the LiteSpeed repo in the following days.

Hi, Thanks for the report, it's a known issue and will be addressed in the next build release.

No problem.

There's an Access Control feature under virtual host level, you can add the IP from there. If you want the config, here's an example, accessControl { deny 1.2.3.4 }

Please wait for a few days and try it again, the OLS v1.8.0 package isn't ready on the LS repo yet. :)