Hello, I'm new here and I'm trying to setup a web server for a web site that I'm creating. I have a few questions regarding Apache2 and FTP. 1st, I've been able to figure out, a little bit, on how to place html's into the /var/www/ directory although there may be a faster, more efficient way as I just copy and paste LOL. 2nd, I can view the web site on my LAN but internet users can't. I have a static IP with dyndns.org and finally, I would like to setup a directory so that gaming users who register with my web site, have the latest car skins. Kinda like Quake III Arena via FTP or, if it's more secure, via my web site.

Any ideas and/or suggestions?

Thanks.

Do you have a firewall (a separate device)? If you do, you need to configure it to allow incoming traffic on port 80.

If you are directly connected with no firewall, you may need to change an internal firewall rule with iptables. This command will list all your iptables rules: Finally, if you're stuck with an ISP that dictates how you may access the internet, they may permanently block incoming port 80 to prevent you from doing what you are doing. But not to worry, you can configure apache to listen to a different port (e.g. "Listen 0.0.0.0:8888") and then have dyndns redirect port 80 to the port you selected.

Thank Ken for your reply. I am behind a Linksys Router which I have forwarded port 80 to the computer that is, in testing right now, on my LAN. I have also looked at the iptables you mentioned and this is the response I got:

ri-simracing:/home/david# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Am I supposed to see any numeric information here?

Thanks again.

No, it looks like iptables is not blocking anything.

If your router is forwarding port 80, then either the server isn't listening or the ISP is blocking port 80.

You might do this on the server to verify apache is running: It should respond with "Apache is running" and some PIDs.

You can also do this to verify the server is actually listening You should see "tcp 0 *:http *.* LISTEN" in the output.

Hi Ken.
The above line didn't work. Replied with "no such file or directory" I replaced /httpd with /apache2 start and got a

bash: /etc/init.d/httpd: No such file or directory
ri-simracing:/home/david# /etc/init.d/apache2
Usage: /etc/init.d/apache2 start|stop|restart|reload|force-reload
ri-simracing:/home/david# /etc/init.d/apache2 start
Starting web server (apache2)...apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
httpd (pid 9979) already running


[/quote]You can also do this to verify the server is actually listening You should see "tcp 0 *:http *.* LISTEN" in the output.[/quote]

These are the results of my netstat query:

Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 *:nfs *:* LISTEN
tcp 0 0 *:51234 *:* LISTEN
tcp 0 0 *:afpovertcp *:* LISTEN
tcp 0 0 *:swat *:* LISTEN
tcp 0 0 *:14534 *:* LISTEN
tcp 0 0 *:713 *:* LISTEN
tcp 0 0 *:netbios-ssn *:* LISTEN
tcp 0 0 *:sunrpc *:* LISTEN
tcp 0 0 *:auth *:* LISTEN
tcp 0 0 localhost:ipp *:* LISTEN
tcp 0 0 *:1047 *:* LISTEN
tcp 0 0 localhost:smtp *:* LISTEN
tcp 0 0 localhost:4700 *:* LISTEN
tcp 0 0 *:2397 *:* LISTEN
tcp 0 0 *:microsoft-ds *:* LISTEN
tcp6 0 0 *:www *:* LISTEN

Unfortunately, no :http listed. I apologize if I'm a little clueless about this. It is definatly different than working with Windows XP.

Thanks Ken.