2 weeks of trying to get this to work

[skyfolly]

---

u can't see anything when u type localhost in yr browser? aiya, I dun think i can help you here since I am not able set up my own server as well! crying here.......................

[andutt]

Check if the processes are up and running with..

ps -efl | grep http

Regards

[skyfolly]

5 S root 3135 1 0 75 0 - 4726 schedu 21:22 ? 00:00:00 /usr/sbin/httpd
5 S apache 3164 3135 0 84 0 - 4732 schedu 21:22 ? 00:00:00 [httpd]
5 S apache 3165 3135 0 84 0 - 4732 semop 21:22 ? 00:00:00 [httpd]
5 S apache 3166 3135 0 84 0 - 4732 semop 21:22 ? 00:00:00 [httpd]
5 S apache 3167 3135 0 84 0 - 4732 semop 21:22 ? 00:00:00 [httpd]
5 S apache 3168 3135 0 84 0 - 4732 semop 21:22 ? 00:00:00 [httpd]
5 S apache 3169 3135 0 84 0 - 4732 semop 21:22 ? 00:00:00 [httpd]
5 S apache 3170 3135 0 84 0 - 4732 semop 21:22 ? 00:00:00 [httpd]
5 S apache 3171 3135 0 84 0 - 4732 semop 21:22 ? 00:00:00 [httpd]
4 S root 3571 3546 0 80 0 - 1204 pipe_w 21:37 pts/0 00:00:00 grep http

[Dolda2000]

Check what address apache has bound to with this:

netstat -antp | grep 80

Also, regarding the security question bpark asked:
Of course port 80 is still open; if it weren't nothing would be able to connect to apache, and then you could just not have apache running, right? The thing is that it automatically blocks all ports that you haven't explicitly forwarded, and therefore you can't have accidental security holes because of eg. instant messenger programs listening to ports that you don't know about. And IM programs do have security holes from time to time.
As for forwarding ports to apache, you have to do it if you want people to be able to use your apache server, right? You can't just "half" block them in order to improve security but still letting requests through. If anything, you can block requests form specific IP addresses that you know are malicious.
Therefore, you can block ports that you don't want to be explicitly opened up, and for the ports that you have opened, you have to configure security options in the programs that are dealing with them.

[nikhil]

ok Cyberfed,

so is apachectl start workin? and apachectl extendedstatus not working?
what is the status right now? can you go to http://localhost:80 on your machine?

[skyfolly]

tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
-
tcp 0 0 192.168.2.103:35049 205.188.248.56:80 ESTABLISHED
5669/opera
tcp 1 0 192.168.2.103:33304 218.30.13.130:80 CLOSE_WAIT
-
tcp 1 0 192.168.2.103:33305 218.30.13.130:80 CLOSE_WAIT
-
tcp 1 0 192.168.2.103:35044 64.177.242.188:80 CLOSE_WAIT
5669/opera
tcp 1 1 192.168.2.103:34982 64.177.242.188:80 LAST_ACK
-
tcp 1 0 192.168.2.103:33301 202.106.185.228:80 CLOSE_WAIT

[Dolda2000]

I didn't know you had a problem, skyfolly? I thought is was Cyberfed we were trying to help here, but I just joined this thread recently.

[andutt]

Id it doesnt work now, check if your Documentroot are correct in your httpd.conf...it should point to the directory where you have you webpages..

Regards

[Cyberfed]

status is it will not come up if i do a localhost in my browser. however it WAS viewable (only local though no web traffic could see it...my orginal problem) till i did something now its not even visible on my computer. apache will not start
if i type apachectl start it'll go to the next prompt
i check processes and its not running anywhere
i do extendedstatus and it says that its not running with the error i posted

so i went from being able to see my server locally only to now not even being able to do that...so upset...

[skyfolly]

I didn't know you had a problem, skyfolly? I thought is was Cyberfed we were trying to help here, but I just joined this thread recently.

Guy I need help too!!! sorry! So Is mine working?