Apply suggestions from code review

Co-authored-by: Jessica <[email protected]>
Co-authored-by: ldecarvalho-doc <[email protected]>

Author: 3 people

compute/instances/troubleshooting/fix-common-issues.mdx

@@ -13,7 +13,7 @@ categories:
   - compute
 ---
 
-This page list the most common issues you may encounter with your Scaleway Instance and provides useful tips how to troubleshoot them.
+This page lists the most common issues you may encounter with your Scaleway Instance and provides useful tips for troubleshooting them.
 
 ## I experience HTTP errors on Instances
 
@@ -28,7 +28,7 @@ This page list the most common issues you may encounter with your Scaleway Insta
 - Application-level errors: Your application code may be crashing or returning incorrect responses.
 - DNS misconfiguration: The domain’s DNS settings might be pointing to the wrong IP or not updated.
 
-### Troubleshooting tips
+### Solution
 - Check security group and firewall rules:
    - In the [Scaleway console](https://console.scaleway.com/instance/security-groups), confirm that ports 80 (HTTP) and 443 (HTTPS) are allowed inbound for the security group used by your Instance.
    - If you manage your own firewall (e.g., iptables, ufw), verify that HTTP and HTTPS traffic is permitted.
@@ -44,7 +44,7 @@ This page list the most common issues you may encounter with your Scaleway Insta
    - If necessary, update the DNS records and wait for propagation.
 
 ### Additional resources
-- [Scaleway Documentation: How to use security groups](/compute/instances/how-to/use-security-groups/)
+- [Scaleway Documentation: How to use security groups](/instances/how-to/use-security-groups/)
 - [Nginx Official Documentation](https://nginx.org/en/docs/)
 - [Apache HTTP Server Documentation](https://httpd.apache.org/docs/)
 
@@ -56,26 +56,26 @@ This page list the most common issues you may encounter with your Scaleway Insta
 - Ping (ICMP) requests are dropped.
 
 ### Possible causes
-- security groups settings: SSH (port `22`) or RDP (port `3389`) might not be open.
+- Security group settings: SSH (port `22`) or RDP (port `3389`) might not be open.
 - Incorrect IP address: You might be connecting to the wrong public IP.
 - User-side firewall or network: Your local network may block outbound SSH or RDP connections.
 - Instance not running: The Instance may be shut down or stuck in an error state.
 
-### Troubleshooting tips
+### Solution
 - Check your Instance status:
    - In the [Scaleway console](https://console.scaleway.com/instance/servers), confirm the Instance is in a running state.
    - Restart the Instance if it’s not responding.
 - Verify the Instance's public IP address:
    - Confirm that the IP in the Scaleway console matches the IP you are using for the connection.
 - Review security groups and local firewalls:
-   - Make sure the default security groups allows SSH or RDP inbound traffic.
+   - Make sure the default security groups allow SSH or RDP inbound traffic.
    - Check your local firewall to ensure outbound SSH (port `22`) or RDP (port `3389`) is allowed.
 - Use the Scaleway console to connect to your Instance:
    - Try using Scaleway’s web-based terminal in the console to rule out local network issues.
 
 ### Additional resources
-- [Scaleway Documentation: How to connect to your Instance](/compute/instances/how-to/connect-to-instance/)
-- [Scaleway Documentation: Troubleshooting SSH connection issues to Instances](/compute/instances/troubleshooting/cant-connect-ssh/)
+- [Scaleway Documentation: How to connect to your Instance](/instances/how-to/connect-to-instance/)
+- [Scaleway Documentation: Troubleshooting SSH connection issues to Instances](/instances/troubleshooting/cant-connect-ssh/)
 
 
 ## I cannot connect to my Instance using an SSH key
@@ -91,7 +91,7 @@ This page list the most common issues you may encounter with your Scaleway Insta
 - Misconfiguration of the SSH daemon: `sshd_config` might disallow key-based authentication.
 - Key not installed: The public key might not have been successfully added to the Instance.
 
-### Troubleshooting tips
+### Solution
 - Check file permissions locally:
    - On your local machine, ensure the private key file has restrictive permissions:
      ```bash
@@ -108,7 +108,7 @@ This page list the most common issues you may encounter with your Scaleway Insta
    - Restart your Instance to re-upload the list of allowed SSH keys.
 
 ### Additional resources
-- [Scaleway Documentation: How to generate an SSH key pair](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/)
+- [Scaleway Documentation: How to generate an SSH key pair](/organizations-and-projects/how-to/create-ssh-key/)
 - [OpenSSH Documentation](https://www.openssh.com/manual.html)
 
 ## How Can I recover access to my Instance?
@@ -121,7 +121,7 @@ This page list the most common issues you may encounter with your Scaleway Insta
 -  The private SSH key associated with the Instance was lost or deleted.
 -  The Instance’s SSH configuration or authorized keys file was altered, removing your access.
 
-### Troubleshooting tips
+### Solution
 - Check for another SSH key:
    - Verify if another SSH key pair is associated with your [Scaleway account](https://console.scaleway.com/project/ssh-keys).
    - Login using the alternative SSH key
@@ -131,21 +131,21 @@ This page list the most common issues you may encounter with your Scaleway Insta
    - Reboot the Instance from the console to re-upload the new key to the Instance.
 
 ### Additional resources
-- [Scaleway Documentation: How to generate an SSH key pair](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/)
-- [Scaleway Documenation: How to power off your Instance](/compute/instances/how-to/power-off-instance/)
+- [Scaleway Documentation: How to generate an SSH key pair](/organizations-and-projects/how-to/create-ssh-key/)
+- [Scaleway Documentation: How to power off your Instance](/instances/how-to/power-off-instance/)
 
 ## My Instance is locked
 
 ### Symptoms
-- Attempts to modify or delete the Instance fail with a “Instance is protected” error.
+- Attempts to modify or delete the Instance fail with an “Instance is protected” error.
 - You see a message in the Scaleway console that the Instance is protected or locked.
 
 ### Possible causes
 - Security measure: The Instance might be locked due to non-payment or administrative hold.
 - User-applied lock: You (or another administrator) enabled resource locking to prevent accidental deletion.
 - Ongoing operation: A pending snapshot or backup can temporarily lock the Instance.
 
-### Troubleshooting tips
+### Solution
 - Check billing and support tickets:
    - Ensure your Scaleway account is in good standing with no overdue invoices.
    - If there is a lock from Scaleway support, resolve any open tickets or compliance issues.
@@ -156,7 +156,7 @@ This page list the most common issues you may encounter with your Scaleway Insta
 
 ### Additional resources
 - [Scaleway Billing FAQ](/faq/billing/)
-- [Scaleway Documentation: How to use the Protected Instance feature](/compute/instances/how-to/use-protected-instance/)
+- [Scaleway Documentation: How to use the Protected Instance feature](/instances/how-to/use-protected-instance/)
 
 ## How can I open port 25 for my Instances?
 
@@ -166,10 +166,10 @@ This page list the most common issues you may encounter with your Scaleway Insta
 
 ### Possible causes
 - Default SMTP restriction: Access to port 25 is restricted by default to prevent spam.
-- security groups settings: The inbound/outbound rules might block port 25.
+- Security group settings: The inbound/outbound rules might block port 25.
 - Missing or incorrect mail server configuration: Postfix, Exim, or another MTA might be misconfigured.
 
-### Troubleshooting tips
+### Solution
 - Configure your security group:
    - In the Scaleway console, ensure outbound connections on port 25 are allowed.
 - Set up proper SPF/DKIM/DMARC:
@@ -178,7 +178,7 @@ This page list the most common issues you may encounter with your Scaleway Insta
    - If port 25 is restricted, consider using a mail relay or an authenticated SMTP service on port 587 or 465.
 
 ### Additional resources
-- [Scaleway Documentation: How to send emails from your Instance](/compute/instances/how-to/send-emails-from-your-instance/)
+- [Scaleway Documentation: How to send emails from your Instance](/instances/how-to/send-emails-from-your-instance/)
 - [Scaleway Tutorial: Setting up a secure mail server on Ubuntu 22.04 LTS (Jammy Jellyfish)](/tutorials/setup-postfix-ubuntu-bionic/)
 - [Scaleway general terms of service](https://www-uploads.scaleway.com/General_Terms_of_Services_v17072024_45d4879c08.pdf)
 - [Postfix Documentation](http://www.postfix.org/documentation.html)
@@ -196,7 +196,7 @@ This page list the most common issues you may encounter with your Scaleway Insta
 - No static routes set: A missing route or gateway could cause traffic to fail.
 - security groups or firewall blocking: The traffic from or to the routed IP might be filtered.
 
-### Troubleshooting tips
+### Solution
 - Verify the IP configuration in the Scaleway console:
    - Confirm that the routed IP is associated with the correct Instance.
 - Update your network configuration files:
@@ -210,10 +210,10 @@ This page list the most common issues you may encounter with your Scaleway Insta
    - Ensure inbound and outbound traffic is allowed for both IP addresses.
 
 ### Additional resources
-- [Scaleway Documentation: How to use flexible IP addresses with Instances](/compute/instances/how-to/use-flexips/)
-- [Scaleway Troubleshooting: Fix unreachable Ubuntu Focal Instance when it has two public IP adresses](/compute/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips/)
-- [Scaleway Troubleshooting: Fix lost IPv6 connectivity on old Debian Buster images when migrating to routed IP](/compute/instances/troubleshooting/fix-lost-ip-connectivity-on-debian-buster/)
-- [Scaleway Troubleshooting: Fix unreachable IPv6 RHEL-based Instances after transitioning to routed IP](/compute/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance/)
+- [Scaleway Documentation: How to use flexible IP addresses with Instances](/instances/how-to/use-flexips/)
+- [Scaleway Troubleshooting: Fix unreachable Ubuntu Focal Instance when it has two public IP addresses](/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips/)
+- [Scaleway Troubleshooting: Fix lost IPv6 connectivity on old Debian Buster images when migrating to routed IP](/instances/troubleshooting/fix-lost-ip-connectivity-on-debian-buster/)
+- [Scaleway Troubleshooting: Fix unreachable IPv6 RHEL-based Instances after transitioning to routed IP](/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance/)
 - [Netplan documenation](https://netplan.readthedocs.io/en/stable/)
 
 ## Disk space errors with Instances
@@ -228,7 +228,7 @@ This page list the most common issues you may encounter with your Scaleway Insta
 - Improper partition setup: Your primary partition might be too small.
 - Uncleaned temporary files: `/tmp`, `/var/tmp`, or application cache directories might be full.
 
-### Troubleshooting tips
+### Solution
 - Check your disk usage:
    - Use `df -h` to check available space on all mounted volumes.
    - Use `du -sh /var/log/*` or other directories to find large files.
@@ -241,8 +241,8 @@ This page list the most common issues you may encounter with your Scaleway Insta
    - Configure `logrotate` or other log management solutions to prevent logs from filling the disk.
 
 ### Additional resources
-- [Scaleway Documentation: How to attach a Block Storage volume to an Instance](/storage/block/how-to/attach-a-volume/)
-- [Scaleway Documentation: How to increase the size of your Block Storage volumes](/storage/block/how-to/increase-block-volume/)
+- [Scaleway Documentation: How to attach a Block Storage volume to an Instance](/block-storage/how-to/attach-a-volume/)
+- [Scaleway Documentation: How to increase the size of your Block Storage volumes](/block-storage/how-to/increase-block-volume/)
 - [Linux Log Rotation Guide](https://linux.die.net/man/8/logrotate)
 
 ## Packet loss issues with Instances
@@ -258,7 +258,7 @@ This page list the most common issues you may encounter with your Scaleway Insta
 - Firewall or rate limits: Overly strict firewall rules can drop packets.
 - Hardware or routing issues: Upstream or local network hardware problems.
 
-### Troubleshooting tips
+### Solution
 - Run basic network diagnostics:
    - Use `ping` and `traceroute` from both your local machine and another external server.
    - Check if packet loss is local or global.
@@ -267,30 +267,30 @@ This page list the most common issues you may encounter with your Scaleway Insta
 - Optimize the MTU
    - Try lowering the MTU (Maximum transmission unit) to 1400 or 1450 and see if packet loss improves, especially in VPN or container setups.
 - Adjust firewall/security groups:
-   - Confirm that your firewall isn not inadvertently dropping packets or rate-limiting ICMP.
+   - Confirm that your firewall is not inadvertently dropping packets or rate-limiting ICMP.
 
 ### Additional resources
-- [Scaleway Documentation: How to use security groups](/compute/instances/how-to/use-security-groups/)
-- [Scaleway Documentation: Preventing outgoing DDoS](/compute/instances/reference-content/preventing-outgoing-ddos/)
+- [Scaleway Documentation: How to use security groups](/instances/how-to/use-security-groups/)
+- [Scaleway Documentation: Preventing outgoing DDoS](/instances/reference-content/preventing-outgoing-ddos/)
 - [Scaleway Tutorial: Configuring Firewalls for Instances](/tutorials/installation-uncomplicated-firewall/)
 
 ## I cannot delete my Instance
 
 ### Symptoms
-- Attempts to delete the Instance fail with a “Instance is protected” error.
+- Attempts to delete the Instance fail with an “Instance is protected” error.
 - You see a message in the Scaleway console that the Instance is protected or locked.
 
 ### Possible causes
 - User-applied lock: You (or another administrator) enabled resource locking to prevent accidental deletion.
 
-### Troubleshooting tips
+### Solution
 - Disable the Protected Instance feature:
    - In the Scaleway console, go to your Instance settings and turn off the lock if you set it manually.
 
 ### Additional resources
-- [Scaleway Documentation: How to use the Protected Instance feature](/compute/instances/how-to/use-protected-instance/)
+- [Scaleway Documentation: How to use the Protected Instance feature](/instances/how-to/use-protected-instance/)
 
 ## Next steps
 
-- Always consult the official [Scaleway Instances Documentation](https://www.scaleway.com/en/docs/compute/instances/) for detailed, up-to-date information to troubleshoot your Instance.
+- Always consult the official [Scaleway Instances Documentation](https://www.scaleway.com/en/docs/instances/) for detailed, up-to-date information to troubleshoot your Instance.
 - If you are still experiencing issues after following these tips, open a [support ticket](https://console.scaleway.com/support) in your Scaleway console, providing detailed descriptions of your issue, logs, screenshots, or error messages. This will help the support team diagnose and resolve your issue more quickly.