1

I have Ubuntu 14.04 and I have installed apache2, but the problem is when I visit my IP as site in order to view web files, it says unable to connect.

If I try to restart apache in SSH I get this error;

~# /etc/init.d/apache2 restart
 * Restarting web server apache2                                                               
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using (IP address of my server here). 
Set the 'ServerName' directive globally to suppress this message

EDIT: here is the error log as suggested by user

Pastebin to error log

Does someone know the solution?

Improve this question
9
  • The mentioned error is not the reason for the problem. Paste the contents (or at least the last 20-100 lines) of the error log here, so people trying to help will have a better idea of what might be causing this problem. The path to the log file is /var/log/apache2/error.log (if the location hasn't been changed in the config file).
    – Sledge Hammer
    Jul 17, 2015 at 10:10
  • Added error log; pastebin.com/qcjU1N2z
    – rosarika
    Jul 17, 2015 at 11:27
  • I can't see anything unusual in the log file... Are you sure you're accessing the site by the right combination of IP and port, and that there are no firewall rules blocking the access to the webserver?
    – Sledge Hammer
    Jul 17, 2015 at 12:03
  • Do a sudo netstat -tulpn the check if your defined port (e.g. 80/443) is opened and accessible from other hosts (must look like e.g. 0.0.0.0:80 or :::80 respectively with 443).
    – lumen
    Jul 17, 2015 at 12:16
  • Hello i am inexperienced with ubuntu. I have just received server and updated, then i typed apt-get install apache2 ...but it's not working for some reason, i don't know why, the ip combination is 100% correct.... Did sudo netstat -tulpn and that is the result gyazo.com/ba1f3660306883a58aa7e7c6efc03c06
    – rosarika
    Jul 17, 2015 at 12:44

1 Answer 1

Reset to default
1

There was nothing wrong with the webserver's configuration. Instead, it was user error -- I was trying to visit https:// instead of http://.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .