Network Problems

Depending on how your system is configured, you may need to set up your network manually. The settings you need depend on which network range your server's IP address falls in.

If you're on Windows, see Windows Network instead — the steps below are for Linux.

IPv4 Network Ranges

IP range Default gateway Netmask
38.45.64.x – 38.45.67.x 38.45.64.1 /22 or 255.255.252.0
38.45.69.x 38.45.69.1 /24 or 255.255.255.0
38.45.71.x 38.45.71.1 /24 or 255.255.255.0
38.45.72.x 38.45.72.1 /24 or 255.255.255.0
38.29.171.x 38.29.171.1 /24 or 255.255.255.0

IPv6

Default gateway: 2001:550:5a00::1

Nameservers

Nameservers can be whatever public resolvers you prefer. Google's public DNS (8.8.8.8 and 8.8.4.4) works well if you don't have a preference.

Diagnosing a network problem

Before changing any configuration, confirm where the problem actually is:

1. Check the interface has an IP address assigned:
ip addr show (or ifconfig on older systems)

2. Ping your own gateway. If this fails, the problem is your local network configuration:
ping -c 4 <your gateway from the table above>

3. Ping an outside address by IP (this rules DNS in or out):
ping -c 4 8.8.8.8

4. If step 3 works but websites don't load, check DNS resolution:
ping -c 4 google.com

5. If the gateway ping fails, trace the path to narrow down where it breaks:
traceroute <your gateway>

Common causes

• Wrong netmask for your range (see table above — the 38.45.64.x – 67.x block is a /22, not a /24)
• Gateway IP mistyped or missing from the interface configuration
• Network interface down or not brought up on boot
• A firewall (iptables/firewalld/ufw) blocking outbound traffic
• DNS server unreachable while the network itself is fine (see step 4 above)

Setting a static IP

Before making any changes below, confirm your actual interface name using ip addr show from step 1 above. Common names are eth0, ens18, and enp1s0 depending on your OS and virtualization platform — the examples below use eth0, but replace it with whatever name appears on your system.

Rocky Linux / AlmaLinux / CentOS

Using nmcli (replace the IP, gateway, and interface name with your own):

nmcli con mod eth0 ipv4.addresses 38.45.71.10/24
nmcli con mod eth0 ipv4.gateway 38.45.71.1
nmcli con mod eth0 ipv4.dns "8.8.8.8 8.8.4.4"
nmcli con mod eth0 ipv4.method manual
nmcli con up eth0

Debian / Ubuntu (Netplan)

Edit the netplan config, typically at /etc/netplan/00-installer-config.yaml. Replace eth0 with your actual interface name:

network:
  version: 2
  ethernets:
    eth0:
      addresses: [38.45.71.10/24]
      routes:
        - to: default
          via: 38.45.71.1
      nameservers:
        addresses: [8.8.8.8, 8.8.4.4]

Apply the change with:

netplan apply

Still stuck?

If you've confirmed your IP, netmask, and gateway match the table above and you're still unable to reach the network, open a support ticket and include the output of ip addr show and traceroute so we can look into it from our end.

  • 4 Users Found This Useful
Was this answer helpful?

Related Articles

Server is Unreachable

If your server is unreachable, work through these steps before opening a ticket — most causes can...