Apache & no-ip

mtrivs · 2006-01-12 07:04:10

OK, so i want to set up a small http server to start out...Nothing big, just simple HTML and maybe some PHP. I have installed apache and have signed up at no-ip.com for the free service. I chose the website URL to be mtrivs.servehttp.com . so now i am able to see the page if i type in my DHCP assigned IP of 192.168.1.44 . However when i go to mitch.servehttp.com i get "Problem loading page". I haven't touched any of the configurations in apache and have tried to edit the /etc/hosts file to the following:

#
# /etc/hosts: static lookup table for host names
#

#<ip-address>    <hostname.domain.org>    <hostname>
127.0.0.1    localhost.localdomain    localhost
71.XXX.XXX.XXX     mitch.servehttp.com    Laptop
192.168.1.44    mitch.servehttp.com     Laptpop

# End of file

However this still doesnt make my website appear. I have run the tool provided by no-ip several times, but it still doesnt help.....What should my next course of action be?

I searched the forums and found someone else with the same problem as me and he was asked to do a dig, so i will do one to save a post.

; <<>> DiG 9.3.1 <<>> mitch.servehttp.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4657
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3

;; QUESTION SECTION:
;mitch.servehttp.com.           IN      A

;; ANSWER SECTION:
mitch.servehttp.com.    60      IN      A       71.XXX.XXX.XXX

;; AUTHORITY SECTION:
servehttp.com.          10925   IN      NS      nf2.no-ip.com.
servehttp.com.          10925   IN      NS      nf3.no-ip.com.
servehttp.com.          10925   IN      NS      nf1.no-ip.com.

;; ADDITIONAL SECTION:
nf1.no-ip.com.          28428   IN      A       204.16.252.8
nf2.no-ip.com.          13286   IN      A       216.66.37.12
nf3.no-ip.com.          13286   IN      A       70.86.196.66

;; Query time: 3 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Jan 12 02:02:31 2006
;; MSG SIZE  rcvd: 161

Thanks in advance! [/b]

tomk · 2006-01-12 10:06:54

dig would be useful if your URL wasn't resolving, but it is - I can ping it (your public IP address is 71.240.250.180 at the moment).

Here's what nmap tells us:

Interesting ports on pool-71-240-250-180.syr.east.verizon.net (71.240.250.180):
(The 1665 ports scanned but not shown below are in state: filtered)
PORT     STATE  SERVICE
22/tcp   open   ssh
80/tcp   open   http
1503/tcp closed imtc-mcs
Device type: broadband router
Running: Panasonic embedded
OS details: Panasonic IP Technology Broadband Networking Gateway, KX-HGW200

So port 80 on your router is open - that's good. However, Firefox gives me a server timeout message, which means no http is being served. The obvious question is - have you forwarded port 80 to your apache box?

mtrivs · 2006-01-12 19:29:18

Thats the right IP your right. I dont know what you mean by forwarding port 80 to my apache box? If you mean through my router, then i have already opened the port. Other than that i am lost.

tomk · 2006-01-12 20:24:27

I don't think this is an Arch question anymore, but let's do it anyway.

According to me, or anyone else on the internet, your web server is (or should be) at 71.240.250.180. Only you, me, and anyone else reading this thread knows that the server's real, and private, address is 192.168.1.44. Your router is meant to take care of directing http traffic from the public to the private address. Briefly, this is called port forwarding, and how it's done varies from router to router. I don't use any of the commercial models myself, so I'd suggest you have a look for your particular model here, and see if that helps.

Let me know how you get on.

mtrivs · 2006-01-13 01:48:27

Oh, thats what i thought u meant, but wasnt sure. To answer the question, yes, port 80 is forwarded.

iphitus · 2006-01-13 01:55:08

Fix up /etc/hosts.allow

Add:

http : ALL : allow

mtrivs · 2006-01-13 02:15:37

Added that line, but still hasn't solved the problem.

rdoggsv · 2006-01-19 02:04:11

are u using a router to connect to the internet ??. I just finished installing today for example my apache on arch (been using apache long time ago but never on arch). And i have a no-ip.com.

Just that i did my nat rule on the router , then u have to put your no-ip.com on your httpd.conf file on the server name

# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If this is not set to valid DNS name for your host, server-generated
# redirections will not work.  See also the UseCanonicalName directive.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address anyway, and this will make 
# redirections work in a sensible way.
#
ServerName rdogg.no-ip.com:80

now everyone from the outside can access my site, but if i want to access to my site locally using rdogg.no-ip.com , i also have to put the public ip on the eth0:0 like this

ifconfig eth0:0 201.247.24.xx netmask 255.255.254.0

and thats it i can access using rdogg.no-ip.com hope this gives some ideas to you.

For example if i dont do the ifconfig thing , i get a "problem loading page", but it is because it is trying to access the router, after the ifconfig thing i have no more problems.

//sorry for my english.

Bzillins8906 · 2006-01-31 17:17:47

Are we sure he started the apache daemon?

cactus · 2006-01-31 17:42:45

omg. the information in this thread is so wrong it is going to make my head explode.

Do not make a virtual nic and give it your external ip address. It is not needed, and wholly undesirable.

Similarly, there is no need for apache to listen on your external ip. It will not even work, as apache cannot see that ip (it is not bound to any interfaces). Specifying ServerName is ok, but generally not needed either.

Just have apache listen on port 80. That is all you need for a simple site (if you want namebased virtual hosting, or ip based virtual hosting, that is entirely different).

rdoggsv · 2006-01-31 19:47:37

cactus wrote:

omg. the information in this thread is so wrong it is going to make my head explode.
Do not make a virtual nic and give it your external ip address. It is not needed, and wholly undesirable.
Similarly, there is no need for apache to listen on your external ip. It will not even work, as apache cannot see that ip (it is not bound to any interfaces). Specifying ServerName is ok, but generally not needed either.
Just have apache listen on port 80. That is all you need for a simple site (if you want namebased virtual hosting, or ip based virtual hosting, that is entirely different).

you just make me fell of doing a video of me changing the settings and showing you that if i dont do the eth0:0 it doesnt work. That is something to do with my router config , i dont know how to configure it to redirect my connections to the port 80 to the machine of the nat rule.

Im telling u for real , if i dont do my eth0:0 my pc tries to connect to the modem and then the message of problem loading page. Rite after i do my eth0:0 , the server works ok.

that its only needed for me to connect with no-ip.com name , but other people can connect to it even if i dont have my eth0:0 configured.

cactus · 2006-01-31 22:04:14

because your local box looks up the ip, then knows it id itself. if you were on a routed subnet, it could cause issues.....and..it is wonky!

ie.
you request rdogg.no-ip.com. You box does a dns lookup on that name.
the public dns returns your external ip of your router.
so.. your browser does an http get against that ip. Your machine has no route for that, and it is not on the local attached segment, so it sends it to its default gateway. The gateway, the router, doesn't handle this very well, since it is addressed to its outside interface, and is coming from the inside interface, so it just kinda..pukes. blech.

you worked around this by labeling one of your interfaces as the external ip. So when the dns query returns the public ip. it says, "holy crap! that is my interface" and it just does a get against its interface.

The proper work around would be to have an entry in the /etc/hosts file, so that the dns lookup (which always checks hosts file first) returns a local address to that machine (be it the interface ip or the loopback). Then the lookup happens locally as well.

Your solution would not work for any other machine on the local segment. The hosts solution, while needing to be done to each local machine, would work.

mtrivs · 2006-01-31 23:28:44

so what would be the propper line to add to my /etc/hosts file?

rdoggsv · 2006-02-01 02:50:35

cactus wrote:

because your local box looks up the ip, then knows it id
you worked around this by labeling one of your interfaces as the external ip. So when the dns query returns the public ip. it says, "holy crap! that is my interface" and it just does a get against its interface.

didnt i just said that already ??

and mtrivs , try adding your public ip and public name as cactus says maybe that will work

mpie · 2006-02-01 06:48:35

and dont forget to edit /etc/resolv.conf

Arch Linux

#1 2006-01-12 07:04:10

Apache & no-ip

#2 2006-01-12 10:06:54

Re: Apache & no-ip

#3 2006-01-12 19:29:18

Re: Apache & no-ip

#4 2006-01-12 20:24:27

Re: Apache & no-ip

#5 2006-01-13 01:48:27

Re: Apache & no-ip

#6 2006-01-13 01:55:08

Re: Apache & no-ip

#7 2006-01-13 02:15:37

Re: Apache & no-ip

#8 2006-01-19 02:04:11

Re: Apache & no-ip

#9 2006-01-31 17:17:47

Re: Apache & no-ip

#10 2006-01-31 17:42:45

Re: Apache & no-ip

#11 2006-01-31 19:47:37

Re: Apache & no-ip

#12 2006-01-31 22:04:14

Re: Apache & no-ip

#13 2006-01-31 23:28:44

Re: Apache & no-ip

#14 2006-02-01 02:50:35

Re: Apache & no-ip

#15 2006-02-01 06:48:35

Re: Apache & no-ip

Board footer