diff --git a/pages/apple-silicon/how-to/access-remote-desktop-mac-mini.mdx b/pages/apple-silicon/how-to/access-remote-desktop-mac-mini.mdx index e53b5f090c..1b9bb839da 100644 --- a/pages/apple-silicon/how-to/access-remote-desktop-mac-mini.mdx +++ b/pages/apple-silicon/how-to/access-remote-desktop-mac-mini.mdx @@ -7,7 +7,7 @@ content: paragraph: Learn how to access a Mac mini using remote desktop clients on macOS, Windows, and Linux. tags: apple-silicon, connection, mac-mini, mac-mini dates: - validation: 2024-07-22 + validation: 2025-01-30 posted: 2021-05-26 categories: - bare-metal diff --git a/pages/apple-silicon/how-to/connect-to-mac-mini-ssh.mdx b/pages/apple-silicon/how-to/connect-to-mac-mini-ssh.mdx index 5373ea25f2..fbca788d03 100644 --- a/pages/apple-silicon/how-to/connect-to-mac-mini-ssh.mdx +++ b/pages/apple-silicon/how-to/connect-to-mac-mini-ssh.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to connect to a Scaleway Mac mini using SSH, providing step-by-step instructions and necessary requirements. tags: apple-silicon, connection, mac-mini, mac-mini-m1 dates: - validation: 2024-07-22 + validation: 2025-01-30 posted: 2021-05-26 categories: - bare-metal diff --git a/pages/apple-silicon/how-to/install-package-manager-mac-mini.mdx b/pages/apple-silicon/how-to/install-package-manager-mac-mini.mdx index 4723c79021..e4b4ac5f72 100644 --- a/pages/apple-silicon/how-to/install-package-manager-mac-mini.mdx +++ b/pages/apple-silicon/how-to/install-package-manager-mac-mini.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to install the Homebrew package manager to a Scaleway Mac mini. tags: apple-silicon, connection, mac-mini, mac-mini-m1 dates: - validation: 2024-07-22 + validation: 2025-01-30 posted: 2021-05-26 categories: - bare-metal diff --git a/pages/apple-silicon/how-to/shutdown-mac-mini.mdx b/pages/apple-silicon/how-to/shutdown-mac-mini.mdx index 887dde4045..36200a8661 100644 --- a/pages/apple-silicon/how-to/shutdown-mac-mini.mdx +++ b/pages/apple-silicon/how-to/shutdown-mac-mini.mdx @@ -8,7 +8,7 @@ content: paragraph: This guide provides instructions on how to properly shutdown a Scaleway Mac mini. tags: mac-mini, mac-mini-m1, apple-silicon, shutdown dates: - validation: 2024-07-22 + validation: 2025-01-30 posted: 2021-05-26 categories: - bare-metal diff --git a/pages/apple-silicon/how-to/update-os-mac-mini.mdx b/pages/apple-silicon/how-to/update-os-mac-mini.mdx index 6f39bd78ea..ab75ab8894 100644 --- a/pages/apple-silicon/how-to/update-os-mac-mini.mdx +++ b/pages/apple-silicon/how-to/update-os-mac-mini.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to update the operating system of a Scaleway Mac mini. tags: apple-silicon, connection, mac-mini, mac-mini-m1 dates: - validation: 2024-07-22 + validation: 2025-01-30 posted: 2021-05-26 categories: - bare-metal diff --git a/pages/apple-silicon/how-to/upgrade-macos-to-beta.mdx b/pages/apple-silicon/how-to/upgrade-macos-to-beta.mdx index 3f87c2cc48..0c0a7d2c5b 100644 --- a/pages/apple-silicon/how-to/upgrade-macos-to-beta.mdx +++ b/pages/apple-silicon/how-to/upgrade-macos-to-beta.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to upgrade the macOS of a Scaleway Mac mini to a beta version. tags: apple-silicon mac-mini beta macos dates: - validation: 2024-07-30 + validation: 2025-01-30 posted: 2024-07-30 categories: - bare-metal diff --git a/pages/apple-silicon/quickstart.mdx b/pages/apple-silicon/quickstart.mdx index e6beffc47c..f7a8ebeac9 100644 --- a/pages/apple-silicon/quickstart.mdx +++ b/pages/apple-silicon/quickstart.mdx @@ -7,7 +7,7 @@ content: paragraph: This page shows you how to get started with Scaleway's Apple silicon. tags: apple-silicon mac-mini- mac mini mac-mini ios dates: - validation: 2024-07-25 + validation: 2025-01-30 posted: 2021-05-26 categories: - bare-metal diff --git a/pages/dedibox-ip-failover/how-to/assign-failover-ip.mdx b/pages/dedibox-ip-failover/how-to/assign-failover-ip.mdx index a540c3550e..8e1aaf3415 100644 --- a/pages/dedibox-ip-failover/how-to/assign-failover-ip.mdx +++ b/pages/dedibox-ip-failover/how-to/assign-failover-ip.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to assign a failover IP for Scaleway Dedibox servers. tags: dedibox failover failover-ip dates: - validation: 2024-07-22 + validation: 2025-01-30 posted: 2021-07-29 categories: - dedibox-network diff --git a/pages/dedibox-ip-failover/how-to/configure-debian-ubuntu.mdx b/pages/dedibox-ip-failover/how-to/configure-debian-ubuntu.mdx index 41ca7bedd3..9ea47b5996 100644 --- a/pages/dedibox-ip-failover/how-to/configure-debian-ubuntu.mdx +++ b/pages/dedibox-ip-failover/how-to/configure-debian-ubuntu.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to configure a Dedibox failover IP on Debian or Ubuntu Linux. tags: failover-failover IP ip debian ubuntu dedibox linux dates: - validation: 2024-07-22 + validation: 2025-01-30 posted: 2021-07-29 categories: - dedibox-network diff --git a/pages/dedibox-ip-failover/how-to/configure-network-virtual-machine.mdx b/pages/dedibox-ip-failover/how-to/configure-network-virtual-machine.mdx index 321f1e085a..b31f7e0b42 100644 --- a/pages/dedibox-ip-failover/how-to/configure-network-virtual-machine.mdx +++ b/pages/dedibox-ip-failover/how-to/configure-network-virtual-machine.mdx @@ -7,7 +7,7 @@ content: paragraph: Learn how to configure network settings for virtual machines on various operating systems, including Ubuntu, Debian, CentOS, and Windows Server. tags: dedibox network virtual-machine virtual machine ubuntu debian centOS windows-server dates: - validation: 2024-07-22 + validation: 2025-01-30 posted: 2021-07-29 categories: - dedibox-network @@ -36,74 +36,75 @@ Find below examples of network interface configurations on different distributio Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for configuring network interfaces. For older releases, refer to the Debian configuration. -1. Log into your virtual machine and open the network configuration file `/etc/netplan/01-netcfg.yaml` in a text editor of your choice, for example `nano`: - ``` +1. Log into your virtual machine and open the network configuration file `/etc/netplan/01-netcfg.yaml` in a text editor of your choice: + ```sh sudo nano /etc/netplan/01-netcfg.yaml ``` -2. Create a network configuration as follows. Replace `fail.over.ip.address` with your failover IP address: +2. Create a network configuration as follows. Replace `` with your failover IP address: ```yaml network: - ethernets: + version: 2 + ethernets: ens18: - addresses: - - [ "fail.over.ip.address/32" ] - nameservers: - addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers) - routes: - - to: default - via: 62.210.0.1 - - to: 62.210.0.1/32 - via: fail.over.ip.address - scope: link - version: 2 + addresses: + - /32 + nameservers: + addresses: [ "51.159.47.28", "51.159.47.26" ] + routes: + - to: default + via: 62.210.0.1 + - to: 62.210.0.1/32 + via: + scope: link ``` 3. Save the file and exit the text editor. 4. Apply the new configuration: - ``` + ```sh sudo netplan apply ``` ## Debian -1. Log into the virtual machine and edit the file `/etc/network/interfaces` with a text editor of your choice, for example, `nano`: - ``` +1. Log into the virtual machine and edit the network configuration file: + ```sh sudo nano /etc/network/interfaces ``` -2. Configure the network interface as follows. Replace `fail.over.ip.address` with your failover IP address: - ``` +2. Configure the network interface as follows. Replace `` with your failover IP address: + ```ini auto eth0 - iface eth0 inet static - address fail.over.ip.address + iface eth0 inet static + address netmask 255.255.255.255 pointopoint 62.210.0.1 gateway 62.210.0.1 ``` 3. Save the file and exit the text editor. -4. Set the DNS server information by editing the file `/etc/resolv.conf`: - ``` +4. Set the DNS server information: + ```sh sudo nano /etc/resolv.conf ``` -5. Set the DNS resolver by adding the following lines to the file. Then save it and exit the text editor: - ``` +5. Add the following DNS resolvers: + ```plaintext nameserver 51.159.47.28 nameserver 51.159.47.26 ``` - - Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each data center](/account/reference-content/scaleway-network-information/#dns-cache-servers) - -6. Activate the network on your virtual machine by running: - ``` +6. Activate the network on your virtual machine: + ```sh sudo ifup eth0 ``` + *Alternatively, you can restart networking with:* + ```sh + sudo systemctl restart networking + ``` ## CentOS -1. Log into the virtual machine and edit the file `/etc/sysconfig/network-scripts/ifcfg-eth0` with a text editor of your choice, for example, `nano`: - ``` +1. Log into the virtual machine and edit the network configuration file: + ```sh sudo nano /etc/sysconfig/network-scripts/ifcfg-eth0 ``` -2. Configure the network interface as follows. Replace `fail.over.ip.address` with your failover IP address and `virtual:mac:address` with the virtual MAC of the VM: - ``` +2. Configure the network interface as follows. Replace `` with your failover IP address and `` with the virtual MAC of the VM: + ```ini DEVICE=eth0 BOOTPROTO=none ONBOOT=yes @@ -112,34 +113,41 @@ Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for PEERDNS=yes TYPE=Ethernet NETMASK=255.255.255.255 - IPADDR=fail.over.ip.address + IPADDR= GATEWAY=62.210.0.1 - DNS1=51.159.47.28 # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers) + DNS1=51.159.47.28 DNS2=51.159.47.26 ARP=yes - HWADDR=virtual:mac:address + HWADDR= ``` -3. Save the file and close the text editor. -4. Edit the file `/etc/sysconfig/network-scripts/route-eth0` as follows, then save and exit the text editor: +3. Save and close the text editor. +4. Create or edit the routing configuration file: + ```sh + sudo nano /etc/sysconfig/network-scripts/route-eth0 ``` + Add the following lines: + ```ini 62.210.0.1 dev eth0 default via 62.210.0.1 dev eth0 ``` -5. Run the following command to bring the network interface up: - ``` +5. Activate the network interface: + ```sh sudo ifup eth0 ``` ## Windows Server -1. Connect to the desktop of your VM in the virtual console, then open the network settings of your server. -2. Enter the following information in the network adapter configuration: - * Address: failover IP - * Subnetmask: `255.255.255.255` - * Gateway: `62.210.0.1` - * DNS 1: `51.159.47.28` - * DNS 2: `51.159.47.26` - - - Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each data center](/account/reference-content/scaleway-network-information/#dns-cache-servers) - \ No newline at end of file +1. Open the network settings on your VM by navigating to: + ``` + Control Panel → Network & Internet → Change Adapter Options + ``` +2. Select your network adapter and enter the following details: + - **IP Address**: `` + - **Subnet Mask**: `255.255.255.255` + - **Gateway**: `62.210.0.1` + - **DNS 1**: `51.159.47.28` + - **DNS 2**: `51.159.47.26` + + + Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each data center](/account/reference-content/scaleway-network-information/#dns-cache-servers) + \ No newline at end of file diff --git a/pages/dedibox-ip-failover/how-to/configure-reverse-dns.mdx b/pages/dedibox-ip-failover/how-to/configure-reverse-dns.mdx index df15d2a2d2..24d93963dd 100644 --- a/pages/dedibox-ip-failover/how-to/configure-reverse-dns.mdx +++ b/pages/dedibox-ip-failover/how-to/configure-reverse-dns.mdx @@ -1,37 +1,51 @@ --- meta: title: How to configure the reverse DNS of a Dedibox failover IP - description: This page explains how to configure the reverse DNS for a Dedibox failover IP in the Online.net consle. + description: This page explains how to configure the reverse DNS for a Dedibox failover IP in the Scaleway Dedibox console. content: - h1: How to configure the reverse DNS of a Dediboxfailover IP - paragraph: This page explains how to configure the reverse DNS for a Dedibox failover IP in the Online.net consle. + h1: How to configure the reverse DNS of a Dedibox failover IP + paragraph: This page explains how to configure the reverse DNS for a Dedibox failover IP in the Scaleway Dedibox console. tags: dedibox dns failover-ip failover dates: - validation: 2024-07-22 + validation: 2025-01-30 posted: 2021-07-29 categories: - dedibox-network --- -Failover IP addresses allow you to have several IP addresses with your server. This allows you to assign IP addresses to different websites or to virtual machines. +Failover IP addresses allow you to assign multiple IP addresses to your server. This enables you to allocate different IPs to websites, virtual machines, or services. -Your failover IP can be routed at any time to your servers in just a few minutes by using our Account Management console or through our API. By switching your failover IP addresses from one server to another, the hosted services remain available without reconfiguring the IP address. +Your failover IP can be routed at any time to your servers within a few minutes using the Scaleway Account Management console or API. By transferring failover IP addresses between servers, hosted services remain available without requiring IP reconfiguration. -You can add a failover IP address(es) for each server according to the offer and your service level. +You can add failover IP addresses to each server based on your offer and service level. - A Dedibox account logged into the [console](https://console.online.net) - A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox) -1. From your Scaleway console, click **Server** > **Network configuration**. The list of your failover IPs and IP blocks displays. - -2. Click **Edit reverses**. The list of your reverse DNS settings displays. -3. Enter the new reverse DNS record and click **Update**. - - - - Make sure to have a valid **[A record](/dedibox-dns/concepts/#dns-record)** for forwarding DNS configured and pointing to your IP address before changing the reverse DNS of it. - +## Configuring Reverse DNS +1. From your Scaleway console, navigate to **Server** > **Network Configuration**. The list of your failover IPs and IP blocks is displayed. + +2. Click **Edit Reverse DNS**. The list of your current reverse DNS records appears. +3. Enter the new reverse DNS record and click **Update**. + + + + Ensure that a valid **[A record](/dedibox-dns/concepts/#dns-record)** is configured and pointing to your IP address before updating the reverse DNS. + + + + Reverse DNS updates may take some time to propagate. You can verify changes using the following commands: + + - Linux/macOS: + ```sh + dig -x + ``` + - Windows: + ```sh + nslookup + ``` + diff --git a/pages/dedibox-ip-failover/how-to/configure-windows.mdx b/pages/dedibox-ip-failover/how-to/configure-windows.mdx index b454f3a644..cf4ce07f78 100644 --- a/pages/dedibox-ip-failover/how-to/configure-windows.mdx +++ b/pages/dedibox-ip-failover/how-to/configure-windows.mdx @@ -7,7 +7,7 @@ content: paragraph: Learn how to configure a Scaleway Dedibox failover IP on Windows Server 2019. tags: dedibox failover-ip windows server windows-server-2019 dates: - validation: 2024-07-22 + validation: 2025-01-30 posted: 2021-07-29 categories: - dedibox-network diff --git a/pages/elastic-metal/how-to/configure-ipv6-hypervisor.mdx b/pages/elastic-metal/how-to/configure-ipv6-hypervisor.mdx index 37174e5c18..8fc76c7345 100644 --- a/pages/elastic-metal/how-to/configure-ipv6-hypervisor.mdx +++ b/pages/elastic-metal/how-to/configure-ipv6-hypervisor.mdx @@ -7,7 +7,7 @@ content: paragraph: This guide explains how to configure IPv6 virtual machines on Proxmox on Elastic Metal, including how to find and configure the IPv6 gateway. tags: elastic-metal ipv6 virtual-machine proxmox dates: - validation: 2024-07-30 + validation: 2025-01-30 posted: 2024-07-30 categories: - bare-metal @@ -18,36 +18,34 @@ When you install your server with a virtualization solution like Proxmox, you ca This guide covers the steps for configuring the network interfaces on different distributions inside a virtual machine on a Proxmox host using flexible IPv6 addresses on Elastic Metal servers. - The DNS cache server (nameserver) may be different depending on the physical location of your server. Refer to our [network information documentation](/account/reference-content/scaleway-network-information/#dns-cache-servers) to find the IPv6 addresses to use with your machine. + The DNS cache server (nameserver) may vary depending on the physical location of your server. Refer to our [network information documentation](/account/reference-content/scaleway-network-information/#dns-cache-servers) to find the IPv6 addresses to use with your machine. - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Elastic Metal server](/elastic-metal/how-to/create-server/) with a hypervisor (Proxmox) installed on it +- An [Elastic Metal server](/elastic-metal/how-to/create-server/) with a hypervisor (Proxmox) installed - A [flexible IPv6](/elastic-metal/how-to/order-flexible-ip/) - A [virtual MAC address](/elastic-metal/how-to/add-virtual-mac-address/) ## Finding your IPv6 gateway -1. Log into your virtual machine using SSH. - -2. Identify your network interface: +1. Log into the virtual machine using SSH. +2. Identify the network interface: ```sh ip a ``` - Take note of your network interface name (e.g., `ens18`). - -3. Find your IPv6 gateway: + Take note of the interface name (e.g., `ens18`). +3. Find the IPv6 gateway: ```sh ip -6 route ``` - Look for the line that specifies the default route. It should look like the following: + Look for the line specifying the default route: ``` default via fe80::xxxx:xxxx:xxxx:xxxx dev ens18 proto static metric 1024 onlink ``` - The `fe80::xxxx:xxxx:xxxx:xxxx` part is your link-local IPv6 gateway address. + The `fe80::xxxx:xxxx:xxxx:xxxx` part is the link-local IPv6 gateway address. ## Ubuntu - Configuration with Netplan @@ -55,8 +53,7 @@ This guide covers the steps for configuring the network interfaces on different ```sh sudo nano /etc/netplan/01-netcfg.yaml ``` - -2. Create the network configuration: +2. Configure the network settings: ```yaml network: version: 2 @@ -81,8 +78,7 @@ This guide covers the steps for configuring the network interfaces on different - 51.159.47.28 - 51.159.47.26 ``` - Replace `FLEXIBLE_IPv4`, `FLEXIBLE_IPv6`, and `LINK_LOCAL_IPv6_GATEWAY` with your actual IP addresses. - + Replace the placeholders with actual values. 3. Apply the configuration: ```sh sudo netplan apply @@ -94,9 +90,8 @@ This guide covers the steps for configuring the network interfaces on different ```sh sudo nano /etc/network/interfaces ``` - 2. Configure the network interface: - ```sh + ```plaintext auto ens18 iface ens18 inet static address FLEXIBLE_IPv4 @@ -107,18 +102,15 @@ This guide covers the steps for configuring the network interfaces on different netmask 64 gateway LINK_LOCAL_IPv6_GATEWAY ``` - Replace `FLEXIBLE_IPv4`, `FLEXIBLE_IPv6`, and `LINK_LOCAL_IPv6_GATEWAY` with your actual IP addresses. - 3. Set the DNS resolver: ```sh sudo nano /etc/resolv.conf ``` - 4. Add the following lines, then save and exit the file. - ``` +4. Add the following lines: + ```plaintext nameserver 51.159.47.28 nameserver 51.159.47.26 ``` - 5. Activate the network configuration: ```sh sudo ifup ens18 @@ -130,9 +122,8 @@ This guide covers the steps for configuring the network interfaces on different ```sh sudo nano /etc/sysconfig/network-scripts/ifcfg-ens18 ``` - 2. Configure the network interface: - ``` + ```ini DEVICE=ens18 BOOTPROTO=none ONBOOT=yes @@ -149,21 +140,14 @@ This guide covers the steps for configuring the network interfaces on different ARP=yes HWADDR=virtual:mac:address ``` - Replace `FLEXIBLE_IPv4`, `FLEXIBLE_IPv6`, and `virtual:mac:address` with your actual IP addresses and MAC address. - -3. Bring up the network interface: +3. Enable the network interface: ```sh sudo ifup ens18 ``` -4. Find the IPv6 gateway: - ```sh - ip -6 route - ``` - -## Debugging configuration issues +## Debugging Configuration Issues -If your IPv6 configuration does not work as expected, follow these steps to troubleshoot: +If your IPv6 configuration does not work, try the following: 1. Check the interface configuration: ```sh @@ -171,23 +155,20 @@ If your IPv6 configuration does not work as expected, follow these steps to trou ip route ip -6 route ``` - 2. Run a ping test: ```sh - ping6 google.com + ping -6 google.com ``` - -3. Check the DNS resolution: +3. Verify DNS resolution: ```sh dig google.com dig -6 google.com ``` - -4. Review your network logs: +4. Check firewall settings: ```sh - sudo journalctl -u systemd-networkd + sudo iptables -L -v -n + sudo ip6tables -L -v -n ``` - 5. Restart network services: ```sh sudo systemctl restart systemd-networkd @@ -195,5 +176,6 @@ If your IPv6 configuration does not work as expected, follow these steps to trou 6. Verify the link-local address: ```sh ip -6 addr show dev ens18 - ping6 LINK_LOCAL_IPv6_GATEWAY - ``` \ No newline at end of file + ping -6 LINK_LOCAL_IPv6_GATEWAY + ``` + diff --git a/pages/elastic-metal/how-to/create-virtual-mac-group.mdx b/pages/elastic-metal/how-to/create-virtual-mac-group.mdx index d4e3a043ef..42498d51f7 100644 --- a/pages/elastic-metal/how-to/create-virtual-mac-group.mdx +++ b/pages/elastic-metal/how-to/create-virtual-mac-group.mdx @@ -7,7 +7,7 @@ content: paragraph: This page explains how to create a virtual MAC group for Scaleway Elastic Metal servers tags: virtual-mac mac-group elastic-metal dates: - validation: 2024-07-22 + validation: 2025-01-30 posted: 2021-05-26 categories: - bare-metal diff --git a/pages/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx b/pages/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx index 7d5dc1be36..917782e0cd 100644 --- a/pages/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx +++ b/pages/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx @@ -7,7 +7,7 @@ content: paragraph: This page helps you recover or avoid unreachable Ubuntu 20.04 Focal Instance when it has two public IP addresses. tags: ubuntu-focal focal 20.04 multiple ipv4 ip dates: - validation: 2024-07-23 + validation: 2025-01-30 posted: 2024-07-23 categories: - compute