DNS Hosting Not Working

[sa3atsky]

Hi, I've followed this guide (http://wiki.amahi.org/index.php/Hosting_a_website) thoroughly and still am unable to host my Amahi server online.
I currently have a TP-Link TL-MR3420 Router, very feature-packed and reliable.
Right now I'm only able to access my DNS addresses from within my network.

• * DHCP Server settings are disabled in the router and dictated by the Amahi Server itself.
  * I've assigned a static IP for the Amahi Server (192.168.1.13).
  * In my routers Port Forwarding -> Virutal Servers -> I've assigned port TCP 80 for my Amahi Server (192.168.1.13)
  * - Also tried assigning a different random port (443) and going to my address "sa3atsky.yourhda.com:443". but doesn't work altogether
  * In my app .conf file I've added both (yourhda.com and dyndns.com) DNS addresses to the ServerAlias string:

• * Attempted Enabling\Disabling "SPI Firewall" on my Router.
  * There is also a "IP & MAC Binding" setting in my router. Tried binding my Amahi Servers MAC address and IP# like assigning static IP
  * Additionally, there is a Dynamic DNS setting in my router itself. I've also enabled the service to my address "hash.dyndns.tv" -- still nothing

Would appreciate if anyone would help me troubleshoot this issue. I'm pulling hairs and out of ideas at the moment.

[bigfoot65]

Hello,

Sorry to hear it is still not working. Have you tried any other port than 443? That one is typically reserved for secure communication, i.e. not 80. The browser might try to detect that as secure and negotiate https instead. I would suggest you try a 4 digit port, like 5432 or something of that nature.

Another thing, there may be a problem adding dyndns to the app conf file too. I would recommend you only add username.yourhda.com. Don't forget you need to restart httpd after changes.

Sounds like you have hit all the obvious things, so now its gonna be a battle to find the problem. I suggest using a tool like wireshark to see what happens when you try to hit username.yourhda.com. It might reveal where the connection is being blocked or getting stuck.

[sa3atsky]

After playing with a lot of settings here and there, tried setting a 4-digit port. Can't access the server with anything other than the usual port 80 - and only from within my network..

tried disabling DHCP server on Amahi and setting it back to the router, restarting both devices on and off with different settings
Also tried enabling DMZ in my router settings for my server to make it even more open to outside connections.. nothing

Using Wireshark Capture:
192.168.1.13 Port 80 - Goes unresponsive for a minute then gives me "Can't get list of interfaces: The other host terminated the connection"
192.168.1.13 Port 5432 - Can't get list of interfaces: Is the server properly installed on 192.168.1.13? connect() failed: No connection could be made because the target machine actively refused it. (code 10061)
http://sa3atsky.yourhda.com Port 80 - Can't get list of interfaces: getaddrinfo() The requested name is valid, but no data of the requested type was found.
http://sa3atsky.yourhda.com Port 5432 - Can't get list of interfaces: getaddrinfo() The requested name is valid, but no data of the requested type was found.

sorry for the n00bness,, am I supposed to Filter the list to "Http" and allow it to capture while I browse the Ip address and look for any irregularities?

[sa3atsky]

I have no clue how to use this software or what Im supposed to do.. Im out of ideas as well, giving up on this Amahi server altogether..

For future reference, someone should update the Http hosting guide with more router-specific tutorials, or at least some troubleshooting tips when things go wrong - seems rather incomplete.

Cheers, I'll check back into this post if there are any updates

[bigfoot65]

Hello,

Sorry to hear you are still having difficulty. There are so many makes/models of routers and network configurations that is is virtually impossible to document them all. If users want to add things to the wiki, that is great. Unfortunately, most get theirs working by whatever method and do not share the steps.

We rely heavily on users to add to the wiki. Our team is very small and does not have the resources to test/document every type of router/networking situation. I wished we could, but we have so many higher priority tasks that there just is not time. The Amahi community is what keeps us going and without there contributions we would not be successful.

The only other thing I can think of is to try Amahi Web-Apps Proxy. It might work for your situation. If the only requirement for your home server is to have an app or two exposed to the outside, then Amahi is not for you. In that case I would recommend trying a distro like Ubuntu and using DynDNS to allow outside access.

We hope you will not throw in the towel and keep forging to find the solution to your situation. If not, I can understand your frustration and desire to not spend a lot more time trying to make it work.

[mattcaron]

I'll take a crack at it.

(1) Have you tried forwarding things like this before, as in, without Amahi? If it works, then it's Amahi. If it doesn't, it's not Amahi.
(2) Assuming your box is doing NAT, fiddling firewall settings isn't going affect port forwarding.
(3) Is there a "DMZ host" option". I'd try setting that to the Amahi server. It's likely not where you want to be permanently (finer grained control and all that), but might get you somewhere.
(4) Are you absolutely certain that your ISP isn't filtering ports to make it so that you can't do what you are trying to do?
(5) Note that just because you set a port on your router doesn't mean it's redirecting that to port 80 on the Amahi server unless you specifically told it to do so.
(6) With wireshark - I think you're using it in some mode where it's trying to connect to the remote host, hence why it is not working. I honestly don't know what you're trying to do there. That said, I use wireshark all the time, so I might be able to help.. if I understood what you were trying to do.

I'm not sure that helps, but unfortunately, your problem description doesn't leave me with much understanding of your network setup other than "it's not working".

That said, I fear that if you give up on Amahi server, it won't help - I think your problem is your networking config, not Amahi. As such, whatever other server you attempt to use will likely have the same problem. I think we need to fix your network first.