Search results

Hi @Naveen Dsouza, I can see the issue, you must hit the context level external redirect error. As you can see there's an extra / in the end of the url which is not right. This issue should has been fixed on 1.5.9, https://openlitespeed.org/release-log/version-1-5-x/ `apt-get upgrade...

Glad to help, we should put a shorten keep log days by default next time.

Hi @ftsor , Please check this post https://www.digitalocean.com/community/questions/openlitespeed-log-rolling-size Let us know if this is the same case.

Hi @oxcid , Please try to increase the HTTP/HTTPS connections as well if it's a small number, e.g. set to 10000 or more. May I ask the server spec and what's your current PHP parameters on web admin settings. Also what's the crawler settings on lscache plugin now, a screenshot or config...

Yes, thanks for the update

If you finish all the steps, script will be removed automatically. To remove it manually is easy, vi /etc/profile and remove the "sudo /opt/domainsetup.sh" entry.

That explains. You can try https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:cache:litemage:troubleshooting:handle-cookie-vary to separate views by cookie.

HI, So if you have lscache setup correctly (see a cache hit from response header), then it general should be able to handle >1000 connections. So "15/30" is really way too low. I may guess cache not working in your production site, could you share the test link here so we can verify? If you...

[Resolved] To anyone who may be interested. Issue was due to invalid cert path, so port 443 listener failed to start.

Hi, May I ask limited number means how many connections to SSL and PHP? Any cache solution on it? I am more curious about how's the site went down. Auto-scaling now may not ideal for cache solution since the cache file may not be valid. To make cache solution work in this case, may need to...

That's normal, default web admin come with self-signed certificate for secure reason. To avoid the warning, you may want to set a valid SSL cert/key on path on web admin SSL tab.

Once you setup the virtual host and add the sub domain to the existing 80/443 listener, also web admin port set to e.g. 8443, then you should be able to visit web admin through https://subdomain:8443.

Hi @kifurax , I just installed on DigitalOcean Ubuntu 18.04 and it went well. Please share the output with command apt list --installed | grep lsphp May I also ask which cloud platform you tested on? Best, Eric

Send your issue/question to `support@litespeedtech.com`

Hi, I think you can create a new virtual host with the sub domain. Follow wikis to set valid SSL on web admin: https://forums.cyberpanel.net/discussion/1259/tutorial-how-to-secure-ols-lsws-webadmin-console-with-valid-ssl-certficate...

Hi @Webshaped.Biz , Could you run this command from ssh console and share the output here? grep certbot /etc/cron.d/certbot | grep -v '#' It will be better if you can also provide ols restart log from `/usr/local/lsws/logs/lsrestart.log` Best, Eric

Hi @Real_Time , Check https://www.litespeedtech.com/support/wiki/doku.php/litespeed_wiki:lsmcd:install-memcached#for_ubuntu_debian . Did you install memcached yet? Please check if service is running. Then go to lscache plugin to enable object cache...

You can add certificate to virtual host level. Visit web admin -> Virtual Hossts -> SSL tab, specify your cert then do a graceful restart Best, Eric

If you were installed from LiteSpeed repository. You can try 1. edit user & group from `/usr/local/lsws/conf/httpd_config.conf` 2. Remove rtreport, `rm -rf /tmp/lshttpd/.rtreport*` 3. then reinstall it by command `apt-get -y install --reinstall openlitespeed `

No cache/cache hit on the page so not cache related. Will check if it's rewrite rule related.