Setting up Apache HTTP server

Micro420 · 02-25-2005, 02:27 PM

I think I'm almost there in terms of setting up a HTTPd server with Apache, but I don't know the details. Here is what I have done basically:

1) I got the Apache server running
2) I setup a hostname at www.dyndns.org (micro420.mine.nu)
3) I changed my router configuration to forward port 80 to my server, 192.168.2.2

Now what do I do? Going to http://micro420.mine.nu doesn't do anything. I can, however, access http://192.168.2.2 internally.

I tried reading the official documentation for the Apache HTTPd server, but it's confusing! It's more like "Good luck finding what you need in this massive documentation" rather than "Okay, here's what you do step-by-step".

david_ross · 02-25-2005, 03:04 PM

Your router probably doesn't support natting back to the lan. Try from a web proxy like:
http://www,proxify.com

You will also need to wait a few minutes for the dns address to become active.

mikeheggy · 02-25-2005, 09:17 PM

I know for sure my router doesn't support "natting back to the lan" (I'm pretty sure it's called loopback?)

Anyway, ask a friend to visit the website. If not, try something like Webscale. That would connect to your server and give you details about your website.

Micro420 · 02-25-2005, 10:37 PM

I went to www.proxify.com and entered my website, but nothing came up. That's because I can't connect to micro420.mine.nu, yet.

I also checked out the webscale website, and again, it could not find the website. That's because my website isn't out on the internet yet. So that is my problem: how do I get my website exposed out on the internet???? It can ONLY be access internally.

mikeheggy · 02-25-2005, 10:55 PM

maybe your ISP blocks port 80?

Micro420 · 02-26-2005, 12:32 AM

Quote:

Originally posted by mikeheggy
maybe your ISP blocks port 80?

is there a way I can find out if this port 80 is blocked? Is there a way around this?

mikeheggy · 02-26-2005, 10:05 AM

What ISP do you have? If your ISP does block port 80, it probably says somewhere in their TOS that running a server is not allowed.

You can check it by changing the port that apache listens on from 80 to 81 or 88 - something that's not already in use. Don't forget to change the configuration in your router to foward to the new port.

Afterwards, do a portscan at www.grc.com, and that will tell you whether the new port is open or not. If it is, then it's likely that your ISP is blocking port 80.

david_ross · 02-26-2005, 01:56 PM

If you gave your true domain name above then it isn't set up right. I can't resolve an IP for it:
rossy - trigger - Sat Feb 26 19:59:18
~> dig +short micro420.mine.nu
rossy - trigger - Sat Feb 26 19:59:56
~>

Micro420 · 02-26-2005, 04:17 PM

Quote:

Originally posted by david_ross
If you gave your true domain name above then it isn't set up right. I can't resolve an IP for it:
rossy - trigger - Sat Feb 26 19:59:18
~> dig +short micro420.mine.nu
rossy - trigger - Sat Feb 26 19:59:56
~>

Yes, it is a false address because the REAL website is actually myrealname.mine.nu and I didn't want to post it.

Micro420 · 02-26-2005, 04:20 PM

Quote:

Originally posted by mikeheggy
What ISP do you have? If your ISP does block port 80, it probably says somewhere in their TOS that running a server is not allowed.

You can check it by changing the port that apache listens on from 80 to 81 or 88 - something that's not already in use. Don't forget to change the configuration in your router to foward to the new port.

Afterwards, do a portscan at www.grc.com, and that will tell you whether the new port is open or not. If it is, then it's likely that your ISP is blocking port 80.

Good news is that port 80 is OPEN, however GRC detects that as a security threat, but that's okay with me.

I'm thinking it's either now a www.dyndns.org configuration problem or an Apache configuration problem.

sarin · 02-26-2005, 05:07 PM

Do an nslookup/dig on your hostname and that should tell you if the dyndns is fine or not. I have worked with httpd long back.

(Edited)Sorry, I had mentioned about acl. But ACL comes in Squid and not in httpd. So removing it.

--Sarin

Micro420 · 02-26-2005, 05:44 PM

Quote:

Originally posted by sarin
Do an nslookup/dig on your hostname and that should tell you if the dyndns is fine or not. I have worked with httpd long back.

(Edited)Sorry, I had mentioned about acl. But ACL comes in Squid and not in httpd. So removing it.

--Sarin

nslookup myrealname.mine.nu

Server: DHC1TF31
Address: 192.168.2.1 <--- This is my second router gateway address, which the server is NOT connected to. Very weird

Name: myrealname.mine.nu
Address: 67.180.140.102 <--- this is my correct Comcast IP address.

lennysokol · 02-26-2005, 06:36 PM

Is this running on Linux? If so, did you start the service?

go to the terminal and type in:

service httpd start

then go to http://localhost in firefox. If you receive a page, your in the right direction!

lennysokol · 02-26-2005, 06:38 PM

BTW:

did you enable chkconfig for Apache for bootup?

you said you can get to internally, but not externally?

Try to go to websitepulse and enter your URL and see if it hits a response.

Also -

what's your public IP? it should be on the router somewhere. try to enter that...?

that limits down whether it's dyndns...

Micro420 · 02-26-2005, 08:00 PM

Quote:

Originally posted by lennysokol
Is this running on Linux? If so, did you start the service?

go to the terminal and type in:

service httpd start

then go to http://localhost in firefox. If you receive a page, your in the right direction!

No, I am running Apache in Windows 2000. The Service is running as I see it in the tray. When I do http://127.0.0.1, or 192.168.2.2, I can see the webpage. But, when I do http://myrealname.mine.nu, it says the connection was refused.

As for the websitepulse, it would not matter since people outside my network cannot see my server or webpage. It would just think that I typed in some non-existent website.