Dear all,

I recently became in charge of a Linux server, and my website is having difficulty working and fails to load up properly. The Linode's name is carolina-review, and the website is http://www.carolinareview.org. The IP is 173.255.230.146 The version of Ubuntu is 14.04.1.

Currently the message showing at that domain is:

Index of /
Name Last modified Size Description
Apache/2.4.7 (Ubuntu) Server at carolinareview.org Port 80

Everything started successfully upon rebooting except for two things. I get one message from apache2 stating:

AH00548: apache2: Could not reliably determine the server's fully qualified domain name using 173.255.230.6. Set the 'Server Name' directive globally to suppress this message.

In addition, lighttpd "can't bind to port: 80 Address already in use"

The person formerly in charge said to stop apache2 and restart lighttpd, which allowed lighttpd to run, but resulted in putting a 404 message displayed on our site instead.

We recently transferred the site to a new Namecheap account as well. The former person in charge failed to state if there was anything to be done in dealing with that.

There are no written messages to be found by the former person in charge. I believe all they did was install apache2 and lighttpd and did nothing else, as I have searched high and low for something.

What steps should I take in order to get the website back working? Any help would be appreciative. Thank you in advance!

Only one web server can bind to port 80. Pick one and go with it. Having Apache and lighttpd fighting over who gets to serve your web traffic is not going to work.

_________________
/ Peter

Peter,

Thank you for that part! I have done that and it has made the start-up much more fluent! However, I'm still getting this as my main page:

Index of /
Name Last modified Size Description
Apache/2.4.7 (Ubuntu) Server at carolinareview.org Port 80

I am also still getting the message from apache2 (now with an update to the IP that I conducted) stating:

AH00548: apache2: Could not reliably determine the server's fully qualified domain name using 173.255.230.146. Set the 'Server Name' directive globally to suppress this message.

How on earth do I set the Server Name and get this problem solved?

_________________
Either provide enough details for people to help, or sit back and listen to the crickets chirp.
Security thru obscurity is a myth - and really really annoying.