Page isn't working - 500 error - swapping to LS from Apache

P

Providence

New Member
#1
#1
Evening all,

I'm somewhat perplexed by this.

I'm running on Plesk Obsidian, and LS was installed (5.4.3) through their extension store.

Everytime I swap over to Litespeed, I get the 500 error and this is on every single page I try to visit.

Swapping back to Apache and the site suddenly works and I cannot work out what the issue is.

It's not a broken .htaccess either, as I have re-moved and then re-uploaded it to double check it.

I've been into the logs for Apache and this is the information I see:

2019-12-29 22:49:23.746301 [NOTICE] [19716] Litespeed is ready to serve...
2019-12-29 22:49:23.747784 [NOTICE] [19716] [AutoRestarter] new child process with pid=19719 is forked!
2019-12-29 22:49:23.748349 [NOTICE] [19716] [AutoRestarter] new child process with pid=19720 is forked!
2019-12-29 22:49:23.749150 [NOTICE] [19720] [*:443] Activates #2->1 SO_REUSEPORT socket: 30
2019-12-29 22:49:23.749211 [NOTICE] [19720] [UDP *:443] Activates #2->1 SO_REUSEPORT socket: 34
2019-12-29 22:49:23.749314 [INFO] [19720] registered RT signal 38
2019-12-29 22:49:23.749355 [INFO] [19720] [UDP 0.0.0.0:443] initPacketsIn: allocated 100 packets
2019-12-29 22:49:23.749405 [NOTICE] [19720] [*:80] Activates #2->1 SO_REUSEPORT socket: 25
2019-12-29 22:49:23.749446 [NOTICE] [19720] [[::]:443] Activates #2->1 SO_REUSEPORT socket: 32
2019-12-29 22:49:23.749464 [NOTICE] [19720] [UDP [::]:443] Activates #2->1 SO_REUSEPORT socket: 36
2019-12-29 22:49:23.749493 [INFO] [19720] [UDP [::]:443] initPacketsIn: allocated 100 packets
2019-12-29 22:49:23.749506 [NOTICE] [19720] [[::]:80] Activates #2->1 SO_REUSEPORT socket: 27
2019-12-29 22:49:23.749520 [INFO] [19720] [*:7088] Stop listener.
2019-12-29 22:49:23.750805 [NOTICE] [19719] [*:443] Activates #1->0 SO_REUSEPORT socket: 29
2019-12-29 22:49:23.750856 [NOTICE] [19719] [UDP *:443] Activates #1->0 SO_REUSEPORT socket: 33
2019-12-29 22:49:23.750950 [INFO] [19719] registered RT signal 38
2019-12-29 22:49:23.750987 [INFO] [19719] [UDP 0.0.0.0:443] initPacketsIn: allocated 100 packets
2019-12-29 22:49:23.751036 [NOTICE] [19719] [*:80] Activates #1->0 SO_REUSEPORT socket: 24
2019-12-29 22:49:23.751076 [NOTICE] [19719] [[::]:443] Activates #1->0 SO_REUSEPORT socket: 31
2019-12-29 22:49:23.751094 [NOTICE] [19719] [UDP [::]:443] Activates #1->0 SO_REUSEPORT socket: 35
2019-12-29 22:49:23.751121 [INFO] [19719] [UDP [::]:443] initPacketsIn: allocated 100 packets
2019-12-29 22:49:23.751134 [NOTICE] [19719] [[::]:80] Activates #1->0 SO_REUSEPORT socket: 26
2019-12-29 22:49:23.803754 [NOTICE] [19716] Memory size is: 1882188KB.
2019-12-29 22:49:23.858970 [INFO] [19716] [LICENSE] License is OK.
2019-12-29 22:49:23.749953 [NOTICE] [19720] [Child: 19720] Setup swapping space...
2019-12-29 22:49:23.750005 [NOTICE] [19720] Successfully change current user to apache
2019-12-29 22:49:23.750015 [NOTICE] [19720] Core dump is enabled.
2019-12-29 22:49:23.750258 [INFO] [19720] [SSL_APK] created offloader with 2 workers.
2019-12-29 22:49:23.750262 [ALERT] [19720] LiteSpeed/5.4.3 Enterprise starts successfully!
2019-12-29 22:49:23.751523 [NOTICE] [19719] [Child: 19719] Setup swapping space...
2019-12-29 22:49:23.751557 [NOTICE] [19719] Successfully change current user to apache
2019-12-29 22:49:23.751565 [NOTICE] [19719] Core dump is enabled.
2019-12-29 22:49:23.751777 [INFO] [19719] [SSL_APK] created offloader with 2 workers.
2019-12-29 22:49:23.751781 [ALERT] [19719] LiteSpeed/5.4.3 Enterprise starts successfully!


The actual error_log for the site doesn't give me any indicators either.

Anyone have any ideas what might be causing this?

Many thanks,

J.
 
T

TommyTran732

New Member
#2
#2
Providence said:
Evening all,

I'm somewhat perplexed by this.

I'm running on Plesk Obsidian, and LS was installed (5.4.3) through their extension store.

Everytime I swap over to Litespeed, I get the 500 error and this is on every single page I try to visit.

Swapping back to Apache and the site suddenly works and I cannot work out what the issue is.

It's not a broken .htaccess either, as I have re-moved and then re-uploaded it to double check it.

I've been into the logs for Apache and this is the information I see:

2019-12-29 22:49:23.746301 [NOTICE] [19716] Litespeed is ready to serve...
2019-12-29 22:49:23.747784 [NOTICE] [19716] [AutoRestarter] new child process with pid=19719 is forked!
2019-12-29 22:49:23.748349 [NOTICE] [19716] [AutoRestarter] new child process with pid=19720 is forked!
2019-12-29 22:49:23.749150 [NOTICE] [19720] [*:443] Activates #2->1 SO_REUSEPORT socket: 30
2019-12-29 22:49:23.749211 [NOTICE] [19720] [UDP *:443] Activates #2->1 SO_REUSEPORT socket: 34
2019-12-29 22:49:23.749314 [INFO] [19720] registered RT signal 38
2019-12-29 22:49:23.749355 [INFO] [19720] [UDP 0.0.0.0:443] initPacketsIn: allocated 100 packets
2019-12-29 22:49:23.749405 [NOTICE] [19720] [*:80] Activates #2->1 SO_REUSEPORT socket: 25
2019-12-29 22:49:23.749446 [NOTICE] [19720] [[::]:443] Activates #2->1 SO_REUSEPORT socket: 32
2019-12-29 22:49:23.749464 [NOTICE] [19720] [UDP [::]:443] Activates #2->1 SO_REUSEPORT socket: 36
2019-12-29 22:49:23.749493 [INFO] [19720] [UDP [::]:443] initPacketsIn: allocated 100 packets
2019-12-29 22:49:23.749506 [NOTICE] [19720] [[::]:80] Activates #2->1 SO_REUSEPORT socket: 27
2019-12-29 22:49:23.749520 [INFO] [19720] [*:7088] Stop listener.
2019-12-29 22:49:23.750805 [NOTICE] [19719] [*:443] Activates #1->0 SO_REUSEPORT socket: 29
2019-12-29 22:49:23.750856 [NOTICE] [19719] [UDP *:443] Activates #1->0 SO_REUSEPORT socket: 33
2019-12-29 22:49:23.750950 [INFO] [19719] registered RT signal 38
2019-12-29 22:49:23.750987 [INFO] [19719] [UDP 0.0.0.0:443] initPacketsIn: allocated 100 packets
2019-12-29 22:49:23.751036 [NOTICE] [19719] [*:80] Activates #1->0 SO_REUSEPORT socket: 24
2019-12-29 22:49:23.751076 [NOTICE] [19719] [[::]:443] Activates #1->0 SO_REUSEPORT socket: 31
2019-12-29 22:49:23.751094 [NOTICE] [19719] [UDP [::]:443] Activates #1->0 SO_REUSEPORT socket: 35
2019-12-29 22:49:23.751121 [INFO] [19719] [UDP [::]:443] initPacketsIn: allocated 100 packets
2019-12-29 22:49:23.751134 [NOTICE] [19719] [[::]:80] Activates #1->0 SO_REUSEPORT socket: 26
2019-12-29 22:49:23.803754 [NOTICE] [19716] Memory size is: 1882188KB.
2019-12-29 22:49:23.858970 [INFO] [19716] [LICENSE] License is OK.
2019-12-29 22:49:23.749953 [NOTICE] [19720] [Child: 19720] Setup swapping space...
2019-12-29 22:49:23.750005 [NOTICE] [19720] Successfully change current user to apache
2019-12-29 22:49:23.750015 [NOTICE] [19720] Core dump is enabled.
2019-12-29 22:49:23.750258 [INFO] [19720] [SSL_APK] created offloader with 2 workers.
2019-12-29 22:49:23.750262 [ALERT] [19720] LiteSpeed/5.4.3 Enterprise starts successfully!
2019-12-29 22:49:23.751523 [NOTICE] [19719] [Child: 19719] Setup swapping space...
2019-12-29 22:49:23.751557 [NOTICE] [19719] Successfully change current user to apache
2019-12-29 22:49:23.751565 [NOTICE] [19719] Core dump is enabled.
2019-12-29 22:49:23.751777 [INFO] [19719] [SSL_APK] created offloader with 2 workers.
2019-12-29 22:49:23.751781 [ALERT] [19719] LiteSpeed/5.4.3 Enterprise starts successfully!


The actual error_log for the site doesn't give me any indicators either.

Anyone have any ideas what might be causing this?

Many thanks,

J.
Click to expand...
Are you using php-fpm or fastcgi?
 
P

Providence

New Member
#3
#3
Hi Tommy,

The default was set to Fast CGI, however using either or doesn't make it work.

For a little more clarity, I use a Digital Ocean droplet.

Litespeed was working perfectly fine on a previous droplet that I had (only 2 weeks ago or so), with the same settings, php version (7.2.26), short tags are on, SSL certs are fine but I destroyed it and created a new one the other day and I've had issues since.
 
You must log in or register to reply here.
Top