fix(vpc): add more troubleshooting

Author: RoRoJ

pages/vpc/troubleshooting/cant-access-vpc-pn.mdx

@@ -1,9 +1,9 @@
 ---
 meta:
-  title: I'm experiencing connectivity issues with my VPC or Private Network
+  title: I'm experiencing connectivity or routing issues with my VPC or Private Network
   description: Troubleshoot access and connectivity issues with your Scaleway VPC or Private Network. Learn how to resolve common problems and get your network up and running smoothly.
 content:
-  h1: I'm experiencing connectivity issues with my VPC or Private Network
+  h1: I'm experiencing connectivity or routing issues with my VPC or Private Network
   paragraph: Troubleshoot access and connectivity issues with your Scaleway VPC or Private Network. Learn how to resolve common problems and get your network up and running smoothly.
 tags: vpc private-network access connectivity ssh ip
 dates:
@@ -13,50 +13,49 @@ categories:
   - network
 ---
 
-You may experience loss of connectivity between resources in a VPC or Private Network, or problems accessing your private resources via SSH.
+You may have problems with connectivity between resources in a VPC or Private Network, or issues with routing packets.
 
-This page helps you solve potential errors that related to VPC access and reachability.
+This page helps you solve potential errors that related to VPC connectivity and routing.
 
-## I can't connect to a resource attached to a Private Network via SSH
+## My Managed Database cannot communicate with other resources in my VPC
 
-### SSH bastion connection problems
+This is normal, as VPC routing is not yet supported by Managed Databases for PostgreSQL or Managed Databases for Redis. Adding support for Managed Databases is planned for the future.
 
-You may be attempting to connect to a Scaleway Instance via [SSH bastion](/public-gateways/how-to/use-ssh-bastion/), and experience errors such as:
+## I cannot deactivate routing on my VPC
 
-- `UNREACHABLE: Failed to connect to the host via ssh: Connection closed by remote host`
-- `Connect failed: No address associated with hostname: Connection closed by UNKNOWN port 123`
+This is standard behavior:
 
-### SSH bastion connection solutions
+- Once you have activated routing on a VPC, you cannot deactivate it
+- You do not have the option to create a new VPC where routing is deactivated
 
-**Try using an IP address instead of a hostname**. An error such as `No address associated with hostname` suggests a problem with DNS resolution of the resource hostname. Try using the resource's private IP address in your connection command instead of its hostname.
+## I cannot route between VPCs/Private Networks in different regions, or different Scaleway Projects.
 
-**Check the validity of your Private Network and/or resource names**. Issues can be caused when:
-    - Names contain dots. Replace dots with dashes (`my.instance` —> `my-instance`). We generally recommend avoiding using dots in your resource names to avoid issues.
-    - Private Network names share the same name as a TLD. See our [dedicated troubleshooting docment](/vpc/troubleshooting/pn-name/#tld-naming-problem-with-private-networks).
-    - A [legacy Public Gateway](/public-gateways/concepts/#legacy-gateway) is attached to a Private Network, and its DNS is [taking priority over that of the Private Network](/public-gateways/concepts/#legacy-gateway). Ensure you are using correct hostnames in accordance with your Public Gateway in this case.
+Currently, routing is only supported between Private Networks in a single VPC. We do not support:
 
-**Ensure your SSH keys are up to date**. If you add new SSH keys to your Project credentials after activating SSH bastion, you will need to perform a reimport to update the bastion with the new keys. [Follow instructions in the dedicated documentation](/public-gateways/how-to/use-ssh-bastion/#how-to-reimport-ssh-keys).
+- Routing between two different VPCs
+- Routing between Private Networks in different Scaleway Projects, or different regions
 
-**Ensure your Instance is not overloaded**. An error such as `Connection closed by UNKNOWN port 123` could be linked to excessive traffic on this port of your Instance, an overload of the Instance's resources (CPU, RAM etc.), or an excessive number of simultaneous connections.
+Watch out for our VPC Peering solution, planned for the future, which will enable communication between different VPCs.
 
-Check the load on the Instance, and try again.
+## I am experiencing issues with Elastic Metal server connectivity to a Private Network
 
-## SSH connection problems (non-bastion)
+Note that some manual configuration of the network interface is required when attaching Elastic Metal servers to Private Networks. Follow the steps in our [dedicated documentation](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks).
 
-You may be attempting to connect to a Scaleway Instance that is attached to a Private Network, via SSH using its public IP address, and experiencing timeout errors.
+## I am experiencing issues with VM (hosted on Elastic Metal server) connectivity to a Private Network
 
-### SSH connection solutions (non-bastion)
+Ensure you have correctly attached the VM to the Private Network by specifying the MAC address, and carried out necessary configuration of the network interface for your VM, e.g. [via the Proxmox interface](/tutorials/setup-elastic-metal-proxmox-cluster-with-private-networks/#configuring-the-private-network).
 
-**Use SSH bastion**. If the Instance is attached to a Private Network on which there is also a Public Gateway advertising the default route, it is normal that you cannot connect using the public IP. Use SSH bastion instead: see our [dedicated troubleshooting page](/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway/)
+<Message type="tip">
+Using the same MAC address on VMs in different AZs, or switching such MAC addresses between AZs, is not compatible with VPC routing. Ensure each VM has a unique MAC address.
+</Message>
 
-## Resources cannot communicate in a VPC
+## My resources cannot communicate via their hostnames
 
+See our dedicated documentation on [resolving private DNS errors](/vpc/troubleshooting/private-dns-dhcp-not-working/).
 
-- Check status
+## I am experiencing other connectivity issues
+
+Check the [Scaleway Status page](https://status.scaleway.com/), to see whether there are any ongoing incidents which could affect the connectivity or network access of your resources.
 
-- MAC address issue 
-loss of connectivity between resources in the same VPC. Reason: L’adresse MAC a été dupliqué entre votre proxmox de par1 et de par2. Basculer une même MAC d'une zone à l'autre n'est pas compatible avec le routage du VPC. Nous vous suggérons très fortement de ne plus basculer cette VM, car cela risque d’engendrer à nouveau les désagréments rencontrés. Nous vous recommandons de changer la MAC de votre VM, puis d'envoyer une gratuitous ARP dans le PN (avec arping par exemple), de manière à ce que les autres VMs soient à jour avec la nouvelle MAC.
 
-- Different VPCs/Projects cannot communicate (no peering)
 
-- DNS?