webserver is functioning normally

A7U

Verified User
Joined
Feb 14, 2023
Messages
11
Hi,

I was using OLS and LSPHP for some time now and decided to switch to nginx+apache. I did all steps correctly as shown in the docs, but now all my websites are down and all certificates are gone.

What do I do?
 
What steps have you done? You must recompile nginx+apache, remove OLS, recompile PHP as php-fpm, rewrite all confs.
 
Did all that.
I have reverted everything back to OLS and LSPHP with this:

Code:
cd /usr/local/directadmin/custombuild
./build update
./build set webserver openlitespeed
./build set mod_ruid2 no
./build set php1_mode lsphp
./build set php2_mode lsphp
./build set php3_mode lsphp
./build set php4_mode lsphp
./build openlitespeed
./build php n
./build rewrite_confs

But everything is still down and only displays"webserver is functioning normally"
 
Ok, I have fixed the issue.
I just ran
Code:
./build openlitespeed
./build rewrite_confs

again and everything is back up again.
 
"webserver is functioning normally" - means there is no virtualhost listening this port for this domain. Maybe something wrong with templates, maybe some custom templates etc.
 
Hello,
were you able to fix this? I started having the same problem and even though I restored from past backups, it doesn't fix it. I delete the user and create it again, but it doesn't work. I switched to Apache and it didn't fix it. I reinstalled openlitespeed and it didn't work.
thanks.
 
1751506357739.png

Hello, I'm having a similar issue with the websites https://dienlanh.edu.vn and https://forum.dienlanh.edu.vn. Can anyone help me with a solution? I'm not an expert, so I tried following step #4, but it still didn't work.
 
This worries me, do you have DA installed on the server ?
Seeing the terminal he shows i guess yes.
But it's a kinda strange way he connects (web) also not logged in as root / sudo so i guess thats why.

Option 1.
He is not an Admin

Option 2.
He doesnt know the basics(?) like sudo etc. because his commands fail due to not being sudo.
 
If that's Ubuntu he's using, $ prompt is normally a user, and # is root. I suspect it's option 1 @ericosman and he needs to enter:
Code:
$ sudo su
and then enter his root password and he'll be able to access all levels, and be able to issue commands without sudo.
 
I always use:
cd /usr/local/directadmin/custombuild
so without colon behind the cd, so not
cd: /usr/local/directadmin/custombuild

maybe in ubuntu this doens't matter, but in Alma I get an error doing it like this.
 
I always use:
cd /usr/local/directadmin/custombuild
so without colon behind the cd, so not
cd: /usr/local/directadmin/custombuild

maybe in ubuntu this doens't matter, but in Alma I get an error doing it like this.
You'll get this error Richard. Ubuntu doesn't like the colon after commands it seems :censored:
1751563487100.png


And i've gotten lazy these days. Since you can issue the 'da build' command, unless i'm running a script from the custombuild folder, i'll usually just use the 'da build ......' command from wherever I am 😁😁
 
the commands are entered without colon, the colon appears only in replies from bash. The /usr/local/directadmin/custombuild/ can not be accessed by a regular user, and CentOS will report:

Bash:
[user@server directadmin]$ cd  /usr/local/directadmin/custombuild
-bash: cd: /usr/local/directadmin/custombuild: Permission denied
[user@server directadmin]$

So, there is no issue with colon, but only with IPs.
 
Back
Top