x
all questions login
General DNS & Domains Dyn Email Update Clients Dyn Developer

I'm at the end of my rope here. I have been working for a couple of days (on and off) to try and make my web site available to the WAN. I have been through the setup guide and the wizard a dozen times, to no avail. My home server has three legs to it:

  1. VNC server - up and running, totally successful using COTVNC
  2. SFTP - no problem; I can upload, download, rsync - you name it. Super sweet.
  3. Web site - forget it. Absolutely not. buddin.dyndns.org is not available to the WAN. The error I get says the server is unavailable. I should note that as a proper server, the computer is awake 24/7

I feel like this last component should've been the easiest part. Just so you know, here are some of the things I've made sure to do:

  • Cox communications blocks port 80, so I edited the Apache httpd.conf file to listen on ports 80 and 8080
  • Restarted apache after making changes
  • assigned my server to a static IP on the LAN (192.168.0.6). The server is also running the dyndns updater daemon in the background.
  • Configured my router (motorola sgb6580) to forward port 8080 (and port 80; I can't see the website locally if I don't do this) to the server's IP (above)
  • Turned off router WAN blocking (not the firewall, though)
  • In the process of getting my file server and VNC server up and running, I also forwarded ports 20-22 and 5900 to the server IP. As I noted, these work fine, so port forwarding/incorrect configuration is not my problem.

Like I mentioned, I'm at the end of my rope here. All I want to do is host one web site for our family to see updates, videos, etc., of our new son. Nothing complicated. No need to configure multiple hosts or anything like that.

Any help would be appreciated.

more ▼

asked Dec 18 at 07:26 PM

hownow\'s gravatar image

hownow
1 1 2

10|600 characters needed characters left

1 Answer:

If you aren't using port 80 then you have to specify the port - http://buddin.dyndns.org:8080/ - which works. If you don't want to have people remember the port then you'll also need a second hostname to use as a WebHop.


Thanks for taking the time to go over this and for the help. I might try tweaking Apache and using a reverse proxy to get rid of the port number. Cheers, -H

You can't get rid of the port number without a WebHop, since your ISP blocks port 80.

more ▼

answered Dec 18 at 08:16 PM

Cry Havok\'s gravatar image

Cry Havok ♦
52k 13 26 222

Thanks for taking the time to go over this and for the help. I might try tweaking Apache and using a reverse proxy to get rid of the port number. Cheers, -H

Dec 19 at 03:33 AM hownow
10|600 characters needed characters left
Your answer
osqa.question.ask.tags.preview.show

© 1998-2011  Dynamic Network Services Inc.  -  Legal Notices  -  Privacy Policy  -  Contacts     

Powered by Qato