https becomes unresponsive

#1
hi guys,

i have an unusual problem where i am able to access the admin panel, then for some reason, it drops off and can no longer access it, when i run netstat i can still see its there waiting for connections, sometimes i even get the CloudFlare 524 Error because the pages takes too long to respond and cloudflare thinks the web server is offline, or admin 7080 page responds with
[ This site can’t be reached - server-ip took too long to respond ], the server is a fresh install, all pages work very fast, its a 2vcpu server with digitalocean, the only thing i still need to optimize is the child processes.

a similar thing happens with loading normal webpages where it sits in a loading loop and the server doesnt seem to respond like its busy but when you check htop there is low cpu usage

Code:
netstat -na | grep 7080
tcp        0      0 0.0.0.0:7080            0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:7080          127.0.0.1:58606         TIME_WAIT
udp        0      0 0.0.0.0:7080            0.0.0.0:*
and if you do a curl test, it redirects http to https which is correct

Code:
curl -i http://localhost:7080
HTTP/1.0 301 Moved Permanently
Location: https://localhost:7080/
Cache-Control: private, no-cache, max-age=0
Pragma: no-cache
Server:LiteSpeed
Content-Length: 0
Connection: Close
and the curl response for https is correct because it doesnt have an ssl certificate

Code:
curl -i https://localhost:7080
curl: (60) SSL certificate problem: self-signed certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
if i open a new browser, or if i go incognito, it doesnt make a difference, iptables is clear and server doesnt have any front facing firewalls enabled, and ufw firewall is also disabled

im stumped as to what is causing this
 
Last edited:
#3
cloudflare doesnt proxy the ip of the server.

see response below, maybe you've seen this before, i changed the port to 7081 to see if it helps, even if i do "systemctl restart lsws" it still doesnt come back but i know if i reboot the server it will

Code:
curl -IkL https://127.0.0.1:7081/
HTTP/2 302
x-powered-by: PHP/8.3.27
x-frame-options: SAMEORIGIN
content-security-policy: frame-ancestors 'self'
referrer-policy: same-origin
x-content-type-options: nosniff
set-cookie: LSUI37FE0C43B84483E0=37f5438c526fc2fcb31180142c0c311e; path=/; secure; HttpOnly
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
set-cookie: LSID37FE0C43B84483E0=deleted; expires=Thu, 01 Jan 1970 00:00:01 GMT; Max-Age=0; path=/
set-cookie: LSPA37FE0C43B84483E0=deleted; expires=Thu, 01 Jan 1970 00:00:01 GMT; Max-Age=0; path=/
set-cookie: LSUI37FE0C43B84483E0=deleted; expires=Thu, 01 Jan 1970 00:00:01 GMT; Max-Age=0; path=/
location: /login.php
content-type: text/html; charset=UTF-8
date: Tue, 04 Nov 2025 01:34:20 GMT
server: LiteSpeed
alt-svc: h3=":7081"; ma=2592000, h3-29=":7081"; ma=2592000, h3-Q050=":7081"; ma=2592000, h3-Q046=":7081"; ma=2592000, h3-Q043=":7081"; ma=2592000, quic=":7081"; ma=2592000; v="43,46"

HTTP/2 200
x-powered-by: PHP/8.3.27
x-frame-options: SAMEORIGIN
content-security-policy: frame-ancestors 'self'
referrer-policy: same-origin
x-content-type-options: nosniff
set-cookie: LSUI37FE0C43B84483E0=ce3cd5c00687a2bffb1a32633e19ffb9; path=/; secure; HttpOnly
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
set-cookie: litespeed_admin_lang=english; expires=Fri, 14 Nov 2025 01:34:20 GMT; Max-Age=864000; path=/; domain=127.0.0.1; secure; HttpOnly
content-type: text/html; charset=UTF-8
date: Tue, 04 Nov 2025 01:34:20 GMT
server: LiteSpeed
alt-svc: h3=":7081"; ma=2592000, h3-29=":7081"; ma=2592000, h3-Q050=":7081"; ma=2592000, h3-Q046=":7081"; ma=2592000, h3-Q043=":7081"; ma=2592000, quic=":7081"; ma=2592000; v="43,46"
 
#4
ive tried to change the version of php that admin panel uses to php84 but no change, curl says its on php84 but website is still not accessible so changed it back
 
#5
i noticed something important, when i remove this server from the load balancer, it receives no more traffic to http and https, and when this happens, im able to access the litespeed admin panel, what could it be?
 
#6
actually maybe not, traffic returned and admin is still up but when it goes down, usually the only way to bring it up is with a reboot, the issue remains, it just doesnt happen all the time
 
#7
curl looks fine. Changing port, webadmin php version, and a reboot are not required. If it failed to bring it up, please check if it's caused by another service listening on the same port with the netstat tool. You can also see the failed reason from the error log.
 
#9
An example command to check if any service is listening on port 7080.
Code:
netstat -antupl | grep 7080
You can check for other ports like 80 and 443 for sure.
 
Top