Amahi Forums

Hi,

Good day!

I have made 2 fresh installs and both failed to resolve the above issue. First I thought that this was due in fact that I initiated my setup process here in the office when I created my Amahi account

Long story short, I did the process all over again and this time, everything was done in my house or home network

My HDA sever is being resolved by the "yourhda.com" registrar with a different IP 220.255.2.158 instead of 115.66.36.156 and hence try if I may Iwouldn't be able to connect to my server from the internet due to this

I am subscribed to Singtel thru their Fibre Service and I suspect the problem may have something to do with this

My dyndns account can resolve my other servers properly without any issues for 4 years now using the same account ever since

Can anyone help me and correct this issue

I also suspect that the Amahi registrar server may have something to do with this issue and can be possibly corrected from Amahi side

This is the only critical issue I am encountering otherwise all features and functions are working fine

I may have gone overboard by building a new and powerful PC from scratch and not just any old PC hardware

My goal is to use an energy efficient low power UEFI bios motherboard capable of detecting natively 3TB HDDS

I would want to use this HDA server with Greyhole implemented using 8 pcs 3TB HDD for a combined storage capacity of 18TB

I am pretty much intrigued and wowed with the features especially VPN and PDC


Marl

Hello,

Does your HDA profile reflect the correct IP address you intend to use for your HDA? If not, then you may need to create a new one. Obviously this will mean a reinstall using the new install code.

If it does reflect correctly, check your IP for the HDA and gateway info. There is a command you can run to change the gateway IP. See the wiki for further guidance.

http://wiki.amahi.org/index.php/Network_troubleshooting

It is possible you might be able to change the gateway which in turn changes the HDA IP and all clients. It may require a restart of your HDA and possibly your network. Its a long shot, but worth trying before having to go through a reinstall.

We currently don't have much in the way of changing IP or gateway info on Amahi at this time. For most, creating a new HDA profile has been the solution. We hope to change that one day.

Hi Sir,


Let me give you a blow by blow on the steps I did

Last week, I was so eager to install Amahi after hurriedly building my server from scratch, buying new energy efficient parts and a UEFI bios which supports 3TB

Since I am mostly in the office, I initiated creating my first account wingcmdr.yourhda.com

I was able to successfully install and run the server when I came home and I was successfully able to run all the apps I was interested with except the 3 game apps which doesn't seem able to install and just goes on preparing to install

After which I decided, its time to gain access from the internet and that is when I configured my router for VPN port forwariding as well as HTTPS and FTP and SSH

That is when I noticed that yourhda.com registrar server are not able to resolve my correct Public IP from my ISP

This was when I thought that maybe, since I created my Amahi Profile in the office then somehow I am being associated from a different location with a different IP address

That was when I decided to give it another try but this time I will do everything at home

Long story short, after undergoing the same process, I still end up with the wrong IP being resolved by yourhda.com registrar server

As per your suggestion to change he gateway address, I can do that even from webmin but my gateway address is the address given out by my 2Wire router which is 192.168.1.254

su -

[enter root password]

hda-change-gw [gateway IP]

Example if your default gateway (router) has an IP of 192.168.0.1:

hda-change-gw 192.168.0.1

Note: You will need to restart your server after applying the change.


As per your question if I have the correct information in my HDA profile, I can say I have checked all of them

nic eth0 <----- onboard lan card
Network 192.168.1.*
Static IP 192.168.1.15 <----- an IP I have chosen to coexist with my other computing devices
subnet 255.255.255.0
Gateway 192.168.1.254 <------- This is my correct 2Wire Router Gateway IP address
Nickname MyCloudServer <----- my prefered Nickname
IP Address 220.255.2.158 <------- Wrong!

One thing to note about all these is that when I turn on my server and it gets connected to the internet, my Amahi Control Panel is able to detect that it is on which tells me my server is able to reach and communicate with the yourhda.com registrar server

The only problem is, the yourhda.com server resolves my public IP incorrectly

I have attached a screenshot of my profile

Many thanks in advanced

Hello,

Does your HDA profile reflect the correct IP address you intend to use for your HDA? If not, then you may need to create a new one. Obviously this will mean a reinstall using the new install code.

If it does reflect correctly, check your IP for the HDA and gateway info. There is a command you can run to change the gateway IP. See the wiki for further guidance.

http://wiki.amahi.org/index.php/Network_troubleshooting

It is possible you might be able to change the gateway which in turn changes the HDA IP and all clients. It may require a restart of your HDA and possibly your network. Its a long shot, but worth trying before having to go through a reinstall.

We currently don't have much in the way of changing IP or gateway info on Amahi at this time. For most, creating a new HDA profile has been the solution. We hope to change that one day.

Did you change your gateway to match your router? Your post indicated you used 192.168.0.1 instead of your actual router. Is it possible there is a firewall with your ISP that is blocking access? If Amahi DynDNS cannot get your ISP assigned IP address, it will now see your HDA as running.

I know sometimes it takes time for it to hook up the connection between the two. We did just update the DynDNS recently, so it may require you email support to get it fixed.

Hi Sir,


I copied and paste the procedure from your link that's why it reflects192.168.0.1

BTW, I have my own dyndns account I have been using for 4 years now

http://wingcmdr.ham-radio-op.net:80 <------ I can use this to get to my homeserver

Can I somehow use my own dyndns account?

Is this possble with the bundled VPN client or do I need to use he Cisco 32 / 64 bit client?

Can yourhda.com registrar get it wrong somehow if I am a fibre subscriber with my ISP Singtel?

I wish configurations would be a bit flexible

Also, thank you very much for your effort so far to help me

Did you change your gateway to match your router? Your post indicated you used 192.168.0.1 instead of your actual router. Is it possible there is a firewall with your ISP that is blocking access? If Amahi DynDNS cannot get your ISP assigned IP address, it will now see your HDA as running.

I know sometimes it takes time for it to hook up the connection between the two. We did just update the DynDNS recently, so it may require you email support to get it fixed.

I have heard of many folks using their own DynDNS. I am unsure of the procedures, but you could check the wiki.

Also, your ISP connection could cause issues if there is some type of firewall or ports blocked that Amahi cannot pass.

As for VPN clients, any should work as long as they are compatible with OpenVPN. The wiki provides links to a few I believe.

Your problems are not typical, so may require more digging. Check log files, ISP standards for ports, etc. I am sure given time and perseverance, things can be sorted out.