DynDNS (No-IP) + HestiaCP

Community Support DNS
1

Hello,
Now I have a VPS I rent with HestiaCP but I would like to place the website in my home on my own server.
I don’t have a fixed ip address so I would like to do that with dyn-dns like no-ip or something.
Is that a possibility? Does anyone has experience with that?
Thank you.

2

I don’t think it’s possible.

Hestiacp supports nat. You can try to configure port forwarding on the router.

3

Hestia doesnt support installation on dynamic ips. You’ll need to get a static atleast.

1 Like
4

A static ip is not possible.
However, my router is a Fritzbox and support DynDNS.
Could it be possible if I configure the router with DynDNS (via No-IP for example) and then also configure port forwarding to the internal ip address of the Hestia CP server?
Thank you. Verus.

5

I just can repeat myself: Without static ip, hestia will not run smoothly (or it even do not run at all). So there is no way to get it running, beside that, yes, you can forward ports using nat - but still a fixed ip is needed.

6

Will this change in the future? It would help a lot of people.

7

This can’t be done with in Hestia

8

yes can this be done freedns.afraid.org, I have done this on my test VPS.

1 Like
9

Hi, and everything works because people here say that it doesn’t work?

10

Hi,

Sure, this is possible! In fact, why shoulld it not?

Any IP, fixed or static, is an IP. HestiaCP is configured to work with an IP and has nothing to do with “static” or “dynamic” quality.

The only difference between a “static” or “dynamic” IP is that it changes. No more and no less.

Once you have installed Hestia on one IP, then you will simply need to write a bash script to update everywhere the new IP to substitute the old IP in the system. That is it.

However, I debate only theoretically here and oppose others, who denied. I cannot write a bash script to achieve that what you want.

11

hi all
no need to write any scripts.

  1. set ubuntu-VPS to have static IP of your local network, an IP that you don’t use from another device.
  2. login to your router, open ports 8083, 80,443 of the VPS to the static IP of your local network.
  3. create a subdomain here https://freedns.afraid.org/subdomain/
  4. do a new installation of hestiacp with your subdomain.
  5. if you can’t login to your hestiacp with the subdomain, login with your local network IP.
    go here FreeDNS - Free subdomain AND domain hosting! click quick cron example at the bottom of the page, copy what looks like this

wget --no-check-certificate -O - https://freedns.afraid.org/dynamic/update.php?Y1FkVkg67y lYaGhLRgtr dlpaVVkyZ1U0OjE5NzEzMzEw >> /tmp/freedns_youname _mooo_com.log 2>&1 &

Add a Cron Job. to your hestiacp, set it to run every minute.
reboot your VPS and you’re good to go

12

You need at least one more step, reboot your server every time the ip changes, or run v-update-sys-ip every time the ip changes. Indeed, Hestia adds this command to rc.local to run that script on every reboot:

❯ cat /etc/rc.local
#!/bin/sh
/usr/local/hestia/bin/v-update-sys-ip
exit 0

v-update-sys-ip does several things, one of them is changing the public ip used by the ftp server to announce the ip to be used for passive connections, also changes the NAT for your local ip, changes dns records…

13

Hi,

Such rebooting mentality is actually coming more from the Windows environment. In Linux, one should reboot only when there are massive changes in several binaries directly interfacing with the environment, like Kernal update, php update, etc.

A change of IP is not affecting in any direct or indirect form of the environment of Limux.

In this case, only the NAT association changes and a new public IP will be inserted because the statis IP remains unchanged, which is a local binding with the router.

As a result, one simply needs to update the NAT IP association and reload the service or restart. Then, the remote binding of the service will be updated and domestic or local binding will remain the same, while ensuring that the service is - or remains - accessible on the network even during the reloading or restarting.

Logically, no reboot is required.

As a result of above logic, either one can use available HestiaCP script to update the public IP, or write once own to capture the public IP and insert in the respective file, which will also reload the network config.

I am using my own scripts and not HestiaCP scripts everywhere. Hence, just discussing an alternative. Using HestiaCP is the recommended solution here for others.