fix(lb): add troubleshooting

Author: RoRoJ

menu/navigation.json

@@ -3597,6 +3597,22 @@
               },
               {
                 "items": [
+                  {
+                    "label": "I am having problems configuring my Load Balancer",
+                    "slug": "configuration"
+                  },
+                  {
+                    "label": "I am experiencing connection problems and HTTP errors with my Load Balancer",
+                    "slug": "http-connection-errors"
+                  },
+                  {
+                    "label": "I am having problems with my Load Balancer's certificate",
+                    "slug": "certificates"
+                  },
+                  {
+                    "label": "I am experiencing problems with my Kubernetes Load Balancer",
+                    "slug": "k8s-errors"
+                  },
                   {
                     "label": "Load Balancer Limitations",
                     "slug": "load-balancer-limitations"

pages/load-balancer/troubleshooting/certificates.mdx

@@ -25,7 +25,7 @@ invalid argument(s): dns_name does not respect constraint, <domain> does not res
 
 The domain name specified does not resolve to the Load Balancer's public IP address.
 
-### Solutions
+### Solution
 
 Try the following steps:
 
@@ -53,8 +53,8 @@ Let's Encrypt certificates cannot be created for Load Balancers which have a fro
 ### Solution:
 
 Ensure that your Load Balancer has either:
-- An HTTP-protocol backend attached to a frontend listening on port 80, or
-- A TCP-protocol backend attached to a frontend listening on a port other than 80
+- An HTTP-protocol-backend attached to a frontend listening on port 80, or
+- A TCP-protocol-backend attached to a frontend listening on a port other than 80
 
 Alternatively, create and import your own [custom certificate](/load-balancer/how-to/add-certificate/#how-to-import-a-certificate) for your Load Balancer, rather than generating a Let's Encrypt certificate via Scaleway.
 

pages/load-balancer/troubleshooting/configuration.mdx

@@ -21,26 +21,26 @@ If your problem concerns any of the following, see our specific documentation pa
 - General advice and help for configuring [frontends](/load-balancer/reference-content/configuring-frontends/), [backends](/load-balancer/reference-content/configuring-backends/) and [health checks](/load-balancer/reference-content/configuring-health-checks/)
 - [Creating and configuring a Kubernetes Load Balancer](/kubernetes/reference-content/kubernetes-load-balancer/)
 
-## When adding a backend server to my Load Balancer, I get an error that the IP is not owned by Scaleway`
+## When adding a backend server to my Load Balancer, I get the message: IP is not owned by Scaleway
 
 You may be trying to [add a backend server](/load-balancer/how-to/create-frontends-backends/#configuring-traffic-management) to your Load Balancer's backend, and experience the following error:
 
 `HTTP 404: IP not owned by Scaleway`
 
 ### Cause
 
-You are trying to add the IP address of a backend server that is not owned by Scaleway (i.e. is not a Scaleway resource such as an Instance, Elastic Metal server or Managed Database.)
+You are trying to add the IP address of a backend server that is not owned by Scaleway (i.e. is not a Scaleway resource such as an Instance, Elastic Metal server or Managed Database).
 
 ### Solution
 
-Only certain Load Balancer types (L and XL) are compatible with non-Scaleway resources as backend servers. This is indicated as "Multi-cloud provider" compatibility in the [Load Balancer creation form](https://console.scaleway.com/load-balancer/lbs/create).
+Only certain Load Balancer types (L and XL) allow you to add non-Scaleway resources as backend servers. This is indicated as "Multi-cloud provider" compatibility in the [Load Balancer creation form](https://console.scaleway.com/load-balancer/lbs/create).
 
 Either:
 
 - [Resize](/load-balancer/how-to/resize-lb/) your Load Balancer to a type that is compatible with multi-cloud backend servers, or
 - Use only Scaleway resources as backend servers for your Load Balancer
 
-## When adding a backend server via its private IP address, I get an error saying this IP doesn't exist
+## When adding a backend server via its private IP address, I get the message: IP doesn't exist
 
 You may be trying to [add a backend server](/load-balancer/how-to/create-frontends-backends/#configuring-traffic-management) to your Load Balancer's backend using the server's private IP address, and experience an error message saying that the IP doesn't exist.
 
@@ -56,19 +56,18 @@ You are entering an incorrect IP address for your resource, or using private IP
 
 ## My Load Balancer's Elastic Metal backend servers added via private IPs are all down
 
-You may find that your Elastic Metal backend servers, which were added to your Load Balancer's backend via their private IP addresses, are all marked as `DOWN` as soon as you add them, and you are unable to work out why they are failing their health checks.
+You may add Elastic Metal backend servers to your Load Balancer using their private IP address, and find they are marked as `DOWN` as soon as you add them. You are unable to work out why they are failing their health checks.
 
 ### Cause
 
-The Load Balancer is unable to successfully communicate with the Elastic Metal backend servers over the Private Network, resulting in failed health checks, due to a configuration problem.
+The Load Balancer is unable to successfully communicate with the Elastic Metal backend servers over the Private Network, resulting in failed health checks.
 
 ### Solution
 
-- Check that you are entering the correct [private IP address](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address) for your Elastic Metal server, and that it is attached to the same Private Network as the Load Balancer.
+- Check that your health checks and backend servers are correctly configured to work together.
+- Check that you have entered the correct [private IP address](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address) for your Elastic Metal server, and that it is attached to the same Private Network as the Load Balancer.
 - Elastic Metal servers require additional manual configuration of their network interface, unlike Instances and other resource types. Ensure you have [followed the necessary configuration steps](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks).
 
-Ensure that the Elastic Metal servers have been correctly configured for the Privat Network. Note that additional steps are required.
-
 
 ## My Load Balancer's IP address is appearing in the backend application's logs, instead of the real client IP address.
 
@@ -80,7 +79,7 @@ Proxy Protocol has not been activated on your Load Balancer, meaning that inform
 
 ### Solution
 
-Activate [Proxy Protocol](/load-balancer/reference-content/configuring-backends/#proxy-protocol) on your Load Balancer, and ensure that your backend server is [correctly configured](/tutorials/proxy-protocol-v2-load-balancer/) to handle the activation of this protocol.
+Activate [Proxy Protocol](/load-balancer/reference-content/configuring-backends/#proxy-protocol) on your Load Balancer, and ensure that your backend server is [correctly configured](/tutorials/proxy-protocol-v2-load-balancer/) to handle this protocol.
 
 ## Security rules not being applied as expected, and I am having difficulties in filtering incoming traffic through my Load Balancer 
 
@@ -90,9 +89,9 @@ You may find that traffic is not being filtered as expected via your Load Balanc
 
 Instance Security Groups and/or Load Balancer ACLs are incorrectly configured.
 
-### Solutions
+### Solution
 
-Instance [Security Groups](instances/how-to/use-security-groups/) should still filter public traffic arriving on your backend server Instances, as long as that traffic is arriving over the public interface, i.e. the Instance in question is attached to the Load Balancer via its public IP and not private IP.
+Instance [Security Groups](instances/how-to/use-security-groups/) should still filter public traffic arriving on your backend server Instances, as long as that traffic is arriving over the public interface. This means the Instance in question must be attached to the Load Balancer via its public IP and not any private IP.
 - Ensure that your Instance is attached via its public IP address. If your Instance behind a Load Balancer is attached via a private IP address, the Security Group rules will not be applied.
-- Double check your [Security Group rules](/instances/how-to/use-security-groups/#how-to-choose-security-group-settings), and that they correspond to the required ports, protocols and IP addresses configured for your Load Balancer
-- To filter incoming traffic to your backend servers **as it passes through the Load Balancer**, use [Load Balancer ACLs](/load-balancer/how-to/create-manage-acls/).
+- Double check your [Security Group rules](/instances/how-to/use-security-groups/#how-to-choose-security-group-settings), to verify that they correspond to the required ports, protocols and IP addresses configured for your Load Balancer
+- To filter incoming traffic to your backend servers **as it passes through the Load Balancer**, use [Load Balancer ACLs](/load-balancer/how-to/create-manage-acls/).

pages/load-balancer/troubleshooting/http-connection-errors.mdx

@@ -17,22 +17,22 @@ You may experience connection problems and HTTP errors when attempting to connec
 
 This page helps you find solutions to some of these most common errors.
 
-### I am getting a 400 Bad Request error when accessing my application through my Load Balancer
+## I am getting a 400 Bad Request error when accessing my application through my Load Balancer
 
 You may find that when attempting to connect to the domain linked to your Load Balancer / the application being served by your backend servers, you receive a `400 Bad Request` error.
 
-## Cause
+### Cause
 
 400 Bad Request errors occur when the backend servers cannot process a request due to client-side issues, or an incompatibility in the way that requests are passed through the Load Balancer and received by the backend server.
 
-## Solutions
+### Solutions
 
 - Try accessing your application directly, and not through your Load Balancer, to eliminate the possibility that the problem does not come from the Load Balancer. Use a tool such as `cURL` or Postman to compare headers and body content to check how the Load Balancer is modifying requests.
-- Check your Load Balancer's [logs](/load-balancer/how-to/monitor-lb-cockpit/#how-to-view-and-understand-your-load-balancer-logs) for any additional information about the way the request was handled.
+- Check your Load Balancer's [Grafana dashboard](/load-balancer/how-to/monitor-lb-cockpit/) for any additional information about the way the request was handled.
 - Verify your certificate and [SSL bridging/offloading/passthrough](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) settings. For example, if SSL is terminated at the Load Balancer, but the backend expects HTTPS, requests may be rejected.
 - Check if [Proxy Protocol](load-balancer/reference-content/configuring-backends/#proxy-protocol) is enabled on your Load Balancer. If your backend server is not configured to handle Proxy Protocol headers correctly, it may reject the requests. Try [disabling Proxy Protocol](/load-balancer/how-to/manage-frontends-and-backends/#how-to-edit-backends-and-health-checks) on your Load Balancer to see if it resolves the issue. If the issue is resolved when Proxy Protocol is disabled, [ensure your backend server is correctly configured for Proxy Protocol](/tutorials/proxy-protocol-v2-load-balancer/) before re-enabling.
 
-### I am getting a 503 Service Unavailable error when trying to access my application through my Load Balancer 
+## I am getting a 503 Service Unavailable error when trying to access my application through my Load Balancer 
 
 You may find that when attempting to connect to the domain linked to your Load Balancer / the application being served by your backend servers, you receive a `503 Service Unavailable` error.
 
@@ -42,7 +42,7 @@ You may find that when attempting to connect to the domain linked to your Load B
 
 ### Solutions
 
-- Check the health of your backend servers. If the servers are failing their health checks, this is likely to be the reason for the error. Investigate the reason for the failing health check, and either make the necessary changes to the servers so they are able to successfully respond to health checks, or [modify your health check settings](/load-balancer/reference-content/configuring-health-checks/) as necessary.
+- Check the health of your backend servers. If the servers are failing their health checks, this is likely to be the reason for the error. Investigate the reason for the failing health check, and reconfigure your server or [health check settings](/load-balancer/reference-content/configuring-health-checks/) as necessary.
 - Check that your Load Balancer is not exceeding its bandwidth. Each Load Balancer type has a [maximum bandwidth](https://www.scaleway.com/en/pricing/network/#load-balancer) it can handle. If you are exceeding this bandwidth, a 503 error is likely. [Check your Load Balancer's metrics](/load-balancer/how-to/monitor-lb-cockpit/), and [resize your Load Balancer](/load-balancer/how-to/resize-lb/) if necessary.
 - Check your Load Balancer's [backend protection settings](/load-balancer/reference-content/configuring-backends/#backend-protection), and compare with [Cockpit data](/load-balancer/how-to/monitor-lb-cockpit/). If backend protection compared to request/connection volume is set in such a way that all backend servers are becoming overloaded, you may need to add additional backend servers or adjust your backend protection settings.