Search results

Please try to increase procSoftLimit and procHardLimit to e.g. 2000 And memory_limit from the php.ini file to 1 GB see if it helps.

Thanks for the report, I will forward it to the build master. You could try to install it manually during the time, https://docs.litespeedtech.com/lsws/extapp/php/extensions/#manual

Glad to know it works

Edit /usr/local/lsws/lsphp81/etc/php/8.1/litespeed/php.ini file from the SSH console, update the memory size, then run `killall -9 lsphp` to make settings take effect. More https://docs.litespeedtech.com/cloud/images/wordpress/#how-do-i-change-php-parameters

It's Linux package related. You might want to share the whole output or follow https://stackoverflow.com/questions/30677470/apt-get-error-sub-process-usr-bin-dpkg-returned-an-error-code-1 to fix it.

Please submit a ticket so we can check on it directly.

Write http://127.0.0.1:2002is fine. If you visit WWW.EXAMPLE.COM/webmail, does that work for you?

Have you create the CGI context yet? https://forum.openlitespeed.org/threads/how-to-run-perl-cgi.5335/

it is still on our build mater to-do list. ~

@vrojas1015 I couldn't recall the issue, does the site has a loading issue now? or does only the web admin has an issue to access? If this is critical, please sent the issue to support@litespeedtech.com and we can help you more quickly from there.

Sure, please try RewriteCond %{REQUEST_URI} ^/webmail$ REWRITERULE ^(.*)$ HTTP://webmail/$1 [P,L,E=PROXY-HOST:WWW.EXAMPLE.COM]

First, you need to make sure curl http://127.0.0.1:2002/abc works locally. Then you can add the rewrite inside of the rewrite tab. REWRITERULE ^(.*)$ HTTP://webmail /$1 [P,L,E=PROXY-HOST:WWW.EXAMPLE.COM] If it works, then you can add a rewritecond for the "webmail". Note, please...

OLS does not support ProxyPass, but you could use the external app + rewrite method, check https://docs.openlitespeed.org/docs/advanced/proxy#method-1-proxying-with-rewrite-rules

Could you send the issue to support@litespeedtech.com with this foru link appended and I will help you further from there?

Looks alright to me, what's the error log say for the reason of the 403?

Checked one site, https://gtmetrix.com/reports/prosalsk.ru/zfLo13Lh/ The TTFB is 226ms which is short. Do you have any screenshot or report link so we can check it further?

ok. It should be a quick check for me if you still have the server on.

The swap file full probably when you have a lot of accounts with a lot of static files, gzip compression may take up space. I'd recommend you to try Method 1 - make /tmp larger enough to hold necessary swap files and gzip compression cache for static files Method 2 - relocate the folder with...

Glad to know it works.

Have you reserved a static IP for the load balancer and pointed a valid domain to it? If your WordPress' site URL is server IP, then it will redirect from the load balancer to the server IP. Note, if you have LSCache, a GCP load balancer is not recommended since it won't recognize the purge...