Cannot reach server?
I ran through everything at:
and found nothing that looked incorrect?
service apache2 status
apache2 is running
apache2ctl -t
Syntax OK
apache2ctl -S
VirtualHost configuration:
*:80 silsurf (/etc/apache2/sites-enabled/000-default.conf:1)
ServerRoot: "/etc/apache2"
Main DocumentRoot: "/var/www"
Main ErrorLog: "/var/log/apache2/error.log"
Mutex default: dir="/var/lock/apache2" mechanism=fcntl
Mutex watchdog-callback: using_defaults
PidFile: "/var/run/apache2/apache2.pid"
Define: DUMP_VHOSTS
Define: DUMPRUNCFG
User: name="www-data" id=33 not_used
Group: name="www-data" id=33 not_used
when I go to the URL it just says "Unable to connect Firefox can’t establish a connection to the server at xxx.xxx.xxx" I have tried multiple browsers and multiple computers
I would love any guidance on how best to proceed with trouble shooting
Thanks
Henry
4 Replies
root 19432 0.0 1.8 5440 2476 ? Ss 03:24 0:01 /usr/sbin/apache2 -k start
www-data 19435 0.0 2.1 284448 2784 ? Sl 03:24 0:08 /usr/sbin/apache2 -k start
luke 24470 0.0 0.5 2544 740 pts/6 S+ 10:55 0:00 grep –color=auto apache
the server uses to identify itself. This is used when creating
redirection URLs. In the context of virtual hosts, the ServerName
specifies what hostname must appear in the request's Host: header to
match this virtual host. For the default virtual host (this file) this
value is not decisive as it is used as a last resort host regardless.
However, you must set it for any further virtual host explicitly.
ServerName www.example.com
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
Available loglevels: trace8, …, trace1, debug, info, notice, warn,
error, crit, alert, emerg.
It is also possible to configure the loglevel for particular
modules, e.g.
LogLevel info ssl:warn
ErrorLog ${APACHELOGDIR}/error.log
CustomLog ${APACHELOGDIR}/access.log combined
For most configuration files from conf-available/, which are
enabled or disabled at a global level, it is possible to
include a line for only one particular virtual host. For example the
following line enables the CGI configuration for this host only
after it has been globally disabled with "a2disconf".
Include conf-available/serve-cgi-bin.conf
vim: syntax=apache ts=4 sw=4 sts=4 sr noet
netstat -lntp
This will tell you which ports and interfaces apache is listening on.
If it does listen on the public IP and HTTP, test whether you can reach the port from the outside with e.g. curl, telnet or nc. If that's not the case, your options are:
1. A WAN problem between you and Linode; try the same test from another location
2. Internal firewall on your Linode is blocking the traffic, iptables -L
3. Sanctions on your Linode account restrict traffic to it
Thanks very much for getting back to me.
H