up vote 0 down vote favorite
share [g+] share [fb]

UPDATED:

Now, when I type my external ip like xxx.xxx.xxx.xxx:8079, i can access xampp defaults page. But the strange is that when someone else from outside my network, try to access it using the same ip, it doesnt work. I Think it should, because its the external ip.

I'm getting crazy. I have tried for hours to access xampp defaults page from outside my local network.

My ISP blocks port 80 and 8080. So I changed apache to listen to port 8079

Listen 8079

My local computer ip is 10.1.1.2

I can access the webserver, from any computer on my local network when I type http://10.1.1.2:8079

I also oppended the port 8079 on my modem, as the image shows bellow. (I think i did it right)

enter image description here

When apache is running on my computer, if I test the port 8079 at http://canyouseeme.org/ i get the message "Success: I can see your service on xxx.xxx.xxx.xxx on port (8079) Your ISP is not blocking port 8079"

If apache is not running I get "Error: I could not see your service on xxx.xxx.xxx.xxx on port (8079) Reason: Connection refused".

So, it's clear that the port 8079 is oppened. But when I type xxx.xxx.xxx.xxx:8079 on google chrome for example, I get Oops! Google Chrome could not connect to xxx.xxx.xxx.xxx:8079

What can I do to solve this, to allow apache to server the pages? I don't know what else I shoud configure.

Please, help me.

Thanks.

link|improve this question
29% accept rate
Where are you trying to access it from? Using the internet address won't work from within your local network - at least, not without special support for doing so in your router. – Shane Madden Aug 4 '11 at 0:26
Well, get your ISP to open port 80 to begin with; that shouldn't be a problem for professional-grade Internet access. – womble Aug 4 '11 at 0:46
Have you tested with a friend? Often trying to connect to the external IP of a NAT box from the inside will not work as expected. This may already be working correctly for others on the internet, just not you on your internal network. – akramer Aug 4 '11 at 5:56
feedback

1 Answer

up vote 0 down vote

I wonder if your apache config is set to block non-local IP addresses? This would cause the port to respond to the above test with a HTTP error, which still shows the port as open.

Is the /NameVirtualhost field set to '*' in your site's apache conf?

Is 'AllowFrom all' set in your virtual directory? http://httpd.apache.org/docs/2.2/howto/access.html

Also, make sure you specify the http:// protocol in your url as well as the port number.

link|improve this answer
Connection refused looks like it is something to do with your httpd.conf (or other config file). Something like MySQL does with BIND 127.0.0.1. – kobaltz Aug 4 '11 at 0:47
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.