CLOSED: FAQ: Does Amahi require to be running as a DHCP server?

[dbegert]

Hi! I recently installed Amahi 9 on Fed 23, but am stuck at the "Transitioning to your Amahi server" step. I tried both options on the "Transition to Amahi" page (https://wiki.amahi.org/index.php/Transition_to_Amahi) -- (1) turning off DHCP in my router, and, alternatively, (2) keeping DHCP enabled, but setting the Primary and Secondary DNS to be the IP of the Amahi server -- but was unable to access http://hda in either case.

I just noticed on the FAQ page, however, that there is a third option: no change in either the DHCP or the DNS on the router (https://www.amahi.org/faq#is-dhcp-server-required).

Does this mean that if my Amahi server is turned on, I should be able to access http://hda any time, even without making any changes to the DHCP and DNS settings in the router?

If I cannot access http://hda with my default router settings, does that mean that something went wrong during the installation and that I should try again?

Thanks for any advice you can provide. Let me know if it would be helpful for me to provide any more details. Thanks!

[bigfoot65]

(1) turning off DHCP in my router, and, alternatively, (2) keeping DHCP enabled, but setting the Primary and Secondary DNS to be the IP of the Amahi server -- but was unable to access http://hda in either case.

When making this change, you need to renew the DHCP lease for your client machine or it will not see the changes. We recommend you let Amahi do the DHCP and DNS server for best results.

Does this mean that if my Amahi server is turned on, I should be able to access http://hda any time, even without making any changes to the DHCP and DNS settings in the router?

Same applies here, need to renew the client machine DHCP lease. Also have you tried accessing the HDA via IP address. If that does not work, then there are bigger issues.

[dbegert]

Oh my... this is very embarrassing. I was able to solve my problem and the solution seems obvious now.

I tried typing in the IP address that I had picked for my Amahi server, to no avail. When that didn't work I figured that I must have messed something up on the install. Sure enough, when I went back through, I realized that when I was signing up for my install code I had simply left the values for my existing gateway as "192.168.1.1," which was the value that had automatically come up. The instructions said that if I did not know my gateway that Amahi would try to determine it for me automatically (or some wording to that effect). Since I didn't know it, I left the values as they were.

Only later, when I got into my router setting to try the "transitioning to Amahi server" step, did I realize that my gateway was 192.168.0.1. But at that point it didn't occur to me that it was a problem that my router gateway and the gateway address that I'd given during the Amahi install were different. I was still under the impression that the installer had figured out whatever it needed to figure out about my gateway address automatically.

So I finally I realized that I needed to delete my first try HDA, get a new install code, and reinstall. This time through I noticed that the instructions clearly state "This is the most important setting" under Your Existing Network Gateway.

Pay attention to the instructions, kids!

[bigfoot65]

Glad you got it sorted out.

I presume we can close this thread.