Jump to content

Apache works locally but not remotely


Aster

Recommended Posts

Hi all,

 

This problem has been driving me mad for a over a week, so I really hope someone can help.

 

I have a debian linux box sitting behind a 'Livebox' Sagem router which I want to use as a web server.  As this router (supplied by my ISP) is particularly annoying, I can't use port 80, so want to use port 18080 and have opened it up in the firewall. I have ADSL so I have also set up a dyndns link.

 

The site works fine when connecting locally from another PC on the LAN (ie 192.168.1.11:18080) so I assume Apache is working ok on port 18080, but won't work when I try mysite.dyndns.org:18080.  Using dyndns' open port tool it says this port is open.  I have tested this further by stopping Apache, port 18080 is 'refused', then when Apache is started again, it is once again 'open' - so the request must be reaching Apache - right?

 

I am really confused, port 18080 works locally, it can be reached with dyndns' port check tool, but refuses to serve web pages.  Also, there is no record in Apache's access log of anything outside the LAN (should there be?).

 

I'm a newbie to both linux and web servers but I have tried to make changes to my virtual hosts configuration, tried using iptables to route it back to Apache's port 80, tried reinstalling apache and a few other things which now slip my mind, but to no avail.  Does anyone have any idea where I'm goin wrong?

 

Thanks in advance!

Link to comment
Share on other sites

Thanks for replying.

 

I've got a windows laptop as well as the Debian box, which I'm using to test both on the LAN (using 192:168.1.11:18080), and internet (using mysite.dyndns.org:18080).

 

I've also tried from work, using both the dyndns address and myIpaddress:18080, and just get the 'Unable to connect' error.

 

I wondered if Apache has some way of blocking external ipaddresses, though when I check the config files I definitely have:

 

Order allow,deny

allow from all

 

Is there anywhere else I should check.

 

Any help much appreciated!

 

Link to comment
Share on other sites

Well I'm fairly sure that it is reaching Apache, as when I stop Apache and use the 'open port tool' on dyndns.com it comes back 'refused' (which they say means the port is not blocked but nothing's listening on it) and when I start Apache again and retry I get port is 'open' - ie there is something listening on it.  This must be Apache as it's the only server I have listening on any ports apart from mysql, and that's only on localhost (and a completely different port).

 

It'd be useful to know what dyndns' tool uses to check - so at least I could see what Apache is responding to and what it won't - does anyone have any ideas?

 

I'm stuck!

Link to comment
Share on other sites

Sorry for the delay, I've been trying to use a packet sniffer to work out what packets were arriving, but I couldn't get it working.

 

The only records in access.log refer to local connections and error.log (level set to debug) show nothing untoward.  I'm still completely lost.

 

Considering a reinstall which I'd rather not do, but if I have to...

Link to comment
Share on other sites

Also, if your trying to access the site via name from within the LAN, the machine your accessing it from will need an entry within its /etc/hosts file.

 

Your name (*dyndns.org) won't resolv properly from within the LAN.

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.