Quote:
Originally Posted by k2k
hi, glen.barber . I am using fedora9. and error_log has this:
"error_log" 7L, 745C
[Fri Oct 24 13:24:51 2008] [notice] SELinux policy enabled; httpd running as context unconfined_u:system_r:httpd_t:s0
[Fri Oct 24 13:24:51 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Oct 24 13:24:51 2008] [notice] Digest: generating secret for digest authentication ...
[Fri Oct 24 13:24:51 2008] [notice] Digest: done
[Fri Oct 24 13:24:51 2008] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads.
[Fri Oct 24 13:24:51 2008] [notice] mod_python: using mutex_directory /tmp
[Fri Oct 24 13:24:51 2008] [notice] Apache/2.2.9 (Unix) DAV/2 PHP/5.2.6 mod_python/3.3.1 Python/2.5.1 mod_ssl/2.2.9 OpenSSL/0.9.8g mod_perl/2.0.3 Perl/v5.10.0 configured -- resuming normal operations |
If you're in front of the machine, open 127.0.0.1 in your browser. If apache is not running, you will get an error. If you're on the same LAN, open the host's IP in a local client's browser.
Quote:
|
should i disable seLinux??
|
This should not be necessary.
Quote:
this is the message generated from Open Port Check Tool
Error: I could not see your service on port (80)
Reason: Connection timed out
so that means port 80 is blocked by my ISP? ..... i'll look into noip.com
|
No-ip won't help you with port 80 being blocked. At best, you can have apache listen on an alternate port.
Regards.
