Amahi Forums

Here is the set up

Using Verizon DSL.

HDA is serving DHCP and DNS

Fedora 19 minimal install with no GUI, running Amahi, not sure if 6 or 7. Installed owncloud, which installed fine. Clicked through to owncloud and created some users and password.

If I enter HDA in the browser (chrome) of a computer on the network, I am prompted for username and password, and I get to the Amahi Dashboard. So far, so good.
If I try accessing username.yourhda.com, I end up at the login screen for my Verizon router. I am also unable to access anything from outside the network when entering username.yourhda.com.

From my Amahi Control Panel

Home Domain amahi.net
Network 192.168.1.*
HDA IP Address 192.168.1.60
Network Gateway 192.168.1.1

From the HDA Dashboard, DNS Aliases

calendar 192.168.1.60
hda 192.168.1.60
help 192.168.1.60
owncloud 192.168.1.60
router 192.168.1.1
search 192.168.1.60
setup 192.168.1.60

Also, can someone please explain this from the Owncloud wiki

Via a web browser to access ownCloud from a...
Server Console: http://owncloud
Workstation: http://owncloud.server_name

When I try http://owncloud.username I end up at a google search or bad dns page.

Did you forward port 80 on your router to the HDA IP address? You may need to disable remote management on your router if it's enabled. Also search the forums for possible solutions as it seems I have seen this before.

Will do. Thanks.

OK, so the wierdness continues.

I have several computers on the same network as the HDA. Computer #1, when typing into a browser "HDA" the dashboard appears. When typing into a browser "Owncloud" the owncloud application appears, and when I type "username.yourhda.com" the HDA dashboard appears.

I can also access "username.yourhda.com" from outside the network.

On computer #2, I have 3 browsers, Chrome, Firefox, and Internet Explorer, this is what happens when I type in various things

Chrome and Internet Explorer
"HDA" = HDA dashboard
"owncloud"= Owncloud login
"username.yourhda.com"= Home Router
"username.yourhda.com/remote.php/webdav"=Blank Screen

Firefox
"HDA" AND "owncloud"= the following error
"The following error was encountered while trying to retrieve the URL: http://hda/ or http://owncloud/
Unable to determine IP address from host name "hda" or "owncloud"
The DNS server returned:
Name Error: The domain name does not exist.
This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct.
Your cache administrator is webmaster."

"username.yourhda.com" AND "username.yourhda.com/remote.php/webdav"= the following error
"The following error was encountered while trying to retrieve the URL: http://username.yourhda.com/ or http://username.yourhda.com/remote.php/webdav/
Connection to XX.XXX.XXX.XXX failed. (The X's is my ISP issued IP address)
The system returned: (110) Connection timed out
The remote host or network may be down. Please try the request again.
Your cache administrator is webmaster."

First, is it normal that "username.yourhda.com" from inside the network connects to the router?

Why am I getting the hostname error in Firefox?

The username.hda.com should not connect to the router. Ensure web remote from outside your network is off.

Also ensure that the HDA is the only DHCP and DNS server. You might also want to ensure the browser cache is deleted for all browsers.

Thanks

Where can I "Ensure web remote from outside your network is off."

I will flush all caches, but I have already flushed the Chrome cache before I tested and posted the results I did above.

That's part of your router setup.

[ Post made via Android ]

OK. That is off, and has been off since before I posted above, and all caches have been flushed. Still the same.

Is the dhcp and dns off on the router?

[ Post made via Android ]

I actually have two routers.

I use a WRT54G for wireless, and my ISP's (Verizon) Actiontec unit for wired and modem. Both have the DHCP disabled. The WRT54's DNS settings are disabled , and the "DynamicDNS" is disabled. In the actiontec, once the DHCP is disabled, the DNS is greyed out, so I assume it is disabled.