|
My Web Hop appears to not be working. I have a feeling my ISP has blocked the port for the redirect, but I can't be certain. Is there any tried and true way to find out of the redirect is blocked? The only other possibility may be that my updater may be messed up, but I kind of doubt that's the case. Thank you. |
|
This rather looks like a misconfigured WebHop. It would be ideal if you could post the WebHop and the target hostname here, or at least an example how you did it. The WebHop is unchanged for the last three years. Here it is: http://heartfullofdirt.com A-record 67.189.223.68 Aug. 16, 2010 10:49 PM http://www.heartfullofdirt.com WebHop http://www2.heartfullofdirt.com:8111/ Mar. 25, 2009 6:44 PM http://www2.heartfullofdirt.com A-record 67.189.223.68 Aug. 16, 2010 10:49 PM I hope this well help you help me! Thanks.
Aug 22 at 06:53 PM
celtgaul
|
Do not respond with a comment. This has no reliable notification. From the Open Port tool result and my own observations it seems to me that you don't run a service listening on port tcp/8111. This is not a problem with your WebHop, but with Are you still able to access your service on port 8111 from within your LAN? Another possibility is that the internal IP address of your server has changed, and the port forwarding rule on the router is pointing to the wrong internal IP address. Better use a static internal IP address for your server outside the DHCP range of your router then, if not already the case. I cannot access the site on port 8111. (I have since changed it to port 8102) I've confirmed that my internal ip is matched to the correct port on my router. Certain diagnostic tools are saying that both ports 8111 and 8102 are not being blocked by my ISP, but I'm skeptical. I've also changed my httpd.conf file to listen to port 8102. I'm beginning to think the problem may be in Apache. Ever since I reinstalled Snow Leopard my Apache installation has been down. If you have any other ideas, I'd be grateful. Thanks.
Aug 22 at 08:33 PM
celtgaul
Also get bad results from netstat command: netstat -anolfind ":8102" netstat: illegal option -- o
Aug 22 at 08:35 PM
celtgaul
|
|
Again, do not respond with a comment. This has no reliable notification. Add another Answer instead! If you changed your application (Apache server's http.conf) to listen on port 8102, first ensure that you can reach your Apache server over port 8102 from another computer within the same network (LAN). Further, you must change your port forwarding rule on the router as well, of course. And you must change your WebHop too. The netstat command I listed was explicitly for Windows only. I don't have a Mac and don't intend to buy one at this occasion. You have to use the Mac equivalent commands instead. Try with Whatever, try to get to your webserver internally using its internal name or IP address (and port) before you take any efforts to reach it from outside with your domainname and port, because this doesn't work then anyway. Thanks. I don't have another Mac, so cannot check internally. I opened port 8012 on the router and listed it in the "Listen" section of httpd.conf. I also changed the hop - still no luck. netstat -an isn't showing much either. Port 8102 isn't listed as "listening." Curiously, most of the ports show for Comcast are in the 50000 range!
Aug 23 at 01:40 AM
celtgaul
|
|
If netstat shows that your webserver is not listening on the port you have configured (e.g. 8012), you must repair (or only start) your webserver. There is no way to continue with anything else before your webserver is functioning. You should at least be able to access it from the same server, using the machine's IP address, but you may need to configure the webserver (httpd.conf) to accept the IP address of that machine as source. Whatever, this is nothing to do with DynDNS, so your best bet is to seek for help in an Apache related forum, ideally where the Mac version is dealt with. |
|
If you use your WAN IP, or non-WebHop hostname, and the relevant port, what does the open port tool show? Can you still access the web server from another host on your local network? Okay, this is where it gets curious. Note the response from the open port tool: n attempted connection to 67.189.223.68:8111 was refused. This typically indicates that there are no services available on that port, but that it is NOT being blocked by a firewall or your ISP. So, it appears that services aren't available on that port, but that it is not being blocked! My router has that port open, though. Any idea of what I'm missing? Thanks.
Aug 22 at 06:55 PM
celtgaul
|
1 2 next page »