Search results

Okay last question, how can I display the log from the end instead of the beginning?

Apparently, it's this line in /usr/local/lsws/admin/html.open/view/logviewer.php: $("#dash_logtbl").dataTable( {"ordering": false, // <-- CHANGE to true...

Oh I figured out I have to increase the length parameter. Now if there was a way to change the time display ordering to descending...

Turns out it works if I use Safari instead of Chrome. On a different note, the server error log webadmin console interface seems broken (in both browsers). On the dashboard page, nothing is displayed. And on the server log viewer page, nothing is displayed unless I select DEBUG and it keeps...

That is definitely not happening for me. Now to figure out why. Here are some unusual messages I see in my server log: ... 2020-09-10 02:08:12.525802 [NOTICE] chroot is disabled. ... 020-09-10 02:49:00.060799 [NOTICE] sendKillCmdToWatchdog: 'extappkill:1867:-3:0'. 2020-09-10 02:49:00.060874...

Thank you for the reply. Is there a log I can look at (or turn on) to figure out what's wrong in my installation?

My (development) openlitespeed server was recently infected with the kinsing malware. My production server is on Cloudways. Don't underestimate security issues. I use the openlitespeed server to run xdebug when I need to debug something. Cloudways does not allow xdebug anymore. I haven't been...

I was trying to suspend/resume a virtual host from the webadmin console and it was not taking. The toggle only took after I did 'sudo service lsws restart' from the terminal. I am running lsws 1.7.4. Let me know if this is a known problem or maybe there is an issue with my installation...

Apparently I had to do: sudo service lsws restart after enabling Referrer/User Agent/Host in the log headers and setting the log format to: "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\" to make it all work. Doing a restart from the webadmin console was not sufficient.

I am running lsws 1.7.4 and the logs/access.log now looks like this: <ip_address> - - [09/Sep/2020:09:20:27 +0000] "" 400 B1209 <ip_address> - - [09/Sep/2020:09:34:41 +0000] "" 400 B1209 <ip_address> - - [09/Sep/2020:21:04:58 +0000] "" 200 O- <ip_address> - - [09/Sep/2020:21:05:06 +0000] "" 200...

I am having the same issue. Would love to know why the log comes out with numbers instead of strings.

The litespeedtech.com website advertises the LiteSpeed Web Server has the only solution to have QUIC and ESI support. I saw QUIC support announced in OpenLiteSpeed 1.6.* and possible ESI support coming too. Am I reading this right?