Network – Hostry Help Center https://help.hostry.com Full information on how to use HOSTRY, provided by 24/7 community based support Mon, 08 Feb 2021 08:27:23 +0000 en-US hourly 1 https://wordpress.org/?v=5.9.12 https://help.hostry.com/wp-content/uploads/cache/2021/01/cropped-apple-icon-180x180-1/836712163.png Network – Hostry Help Center https://help.hostry.com 32 32 Correcting network configuration after Snapshot recovery https://help.hostry.com/knowledge-base/correcting-network-configuration-after-snapshot-recovery/ Wed, 28 Oct 2020 09:02:18 +0000 https://help.hostry.com/?post_type=ht_kb&p=2480 Snapshot is a copy of files and directories of the file system at a specific point in time. File systems at this point can later be mounted read-only.

So, after the snapshot recovery period has passed on the new VPS, problems may arise caused by changing the MAC address of the network adapter. Typically, when you change a network adapter, the operating system creates a new network adapter for it. Typically you will see the network adapter on “eth1” (or eth2 if you have a private network enabled).

CentOS

This operating system describes the following steps to correct network configuration after snapshot recovery:

  1. First you need to log into your server, this can be done as a consequence of this;
  2. Delete the contents of /etc/udev/rules.d/70-persistent-net.rules
  3. Open /etc/sysconfig/network-scripts/ifcfg-eth0 and change the content to the following:
DEVICE=eth0
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=yes
BOOTPROTO=dhcp
DNS1=8.8.8.8
NAME="System eth0"

After this three steps, you need to restart VPS

Debian & Ubuntu

This operating system describes the following steps to correct network configuration after snapshot recovery:

  1. First you need to log into your server, this can be done as a consequence of this;
  2. Delete the contents of /etc/udev/rules.d/70-persistent-net.rules
  3. Review the contents of /etc/network/interfaces and update all IP addresses to match the current server.

After this three steps, you need to restart VPS

]]>