|
| 1 | +--- |
| 2 | +meta: |
| 3 | + title: I am having problems configuring my Load Balancer |
| 4 | + description: Troubleshoot problems that you may experience when configuring your Load Balancer, such as adding backend servers, setting up Private Networks and dealing with security concerns. |
| 5 | +content: |
| 6 | + h1: I am having problems configuring my Load Balancer |
| 7 | + paragraph: Troubleshoot problems that you may experience when configuring your Load Balancer, such as adding backend servers, setting up Private Networks and dealing with security concerns. |
| 8 | +tags: load-balancer configuration backend server error security ip |
| 9 | +dates: |
| 10 | + validation: 2025-03-06 |
| 11 | + posted: 2025-03-06 |
| 12 | +categories: |
| 13 | + - network |
| 14 | +--- |
| 15 | + |
| 16 | +If your problem concerns any of the following, see our specific documentation pages: |
| 17 | + |
| 18 | +- [Troubleshooting certificate configuration](/load-balancer/troubleshooting/certificates/) |
| 19 | +- [Setting up SSL bridging, offloading or passthrough](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) |
| 20 | +- [Troubleshooting connection and HTTP errors](/load-balancer/troubleshooting/http-connection-errors/) |
| 21 | +- 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/) |
| 22 | +- [Creating and configuring a Kubernetes Load Balancer](/kubernetes/reference-content/kubernetes-load-balancer/) |
| 23 | + |
| 24 | +## When adding a backend server to my Load Balancer, I get the message: IP is not owned by Scaleway |
| 25 | + |
| 26 | +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: |
| 27 | + |
| 28 | +`HTTP 404: IP not owned by Scaleway` |
| 29 | + |
| 30 | +### Cause |
| 31 | + |
| 32 | +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). |
| 33 | + |
| 34 | +### Solution |
| 35 | + |
| 36 | +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). |
| 37 | + |
| 38 | +Either: |
| 39 | + |
| 40 | +- [Resize](/load-balancer/how-to/resize-lb/) your Load Balancer to a type that is compatible with multi-cloud backend servers, or |
| 41 | +- Use only Scaleway resources as backend servers for your Load Balancer |
| 42 | + |
| 43 | +## When adding a backend server via its private IP address, I get the message: IP doesn't exist |
| 44 | + |
| 45 | +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. |
| 46 | + |
| 47 | +### Cause |
| 48 | + |
| 49 | +You are entering an incorrect IP address for your resource, or using private IP address that is outside the standard range for private networks. |
| 50 | + |
| 51 | +### Solution |
| 52 | + |
| 53 | +- 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 resource, and that it is attached to the same Private Network as the Load Balancer. |
| 54 | +- Verify that you are using a private IP address that is within the standard ranges used for private networks as described in [RFC1918](https://en.wikipedia.org/wiki/Private_network#Private_IPv4_addresses). Only IP addresses from within one of these ranges are supported by Scaleway Load Balancer. |
| 55 | + |
| 56 | + |
| 57 | +## My Load Balancer's Elastic Metal backend servers added via private IPs are all down |
| 58 | + |
| 59 | +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. |
| 60 | + |
| 61 | +### Cause |
| 62 | + |
| 63 | +The Load Balancer is unable to successfully communicate with the Elastic Metal backend servers over the Private Network, resulting in failed health checks. |
| 64 | + |
| 65 | +### Solution |
| 66 | + |
| 67 | +- Check that your health checks and backend servers are correctly configured to work together. |
| 68 | +- 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. |
| 69 | +- 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). |
| 70 | + |
| 71 | + |
| 72 | +## My Load Balancer's IP address is appearing in the backend application's logs, instead of the real client IP address. |
| 73 | + |
| 74 | +You may find that as requests are passed from the client, through the Load Balancer, to your backend servers, that the client's original IP address is replaced with the Load Balancer's IP address in your backend application's logs. This is problematic if you need the original IP address for localization, security or other purposes. |
| 75 | + |
| 76 | +### Cause |
| 77 | + |
| 78 | +Proxy Protocol has not been activated on your Load Balancer, meaning that information about the original client's connection is not being passed through to the backend servers. |
| 79 | + |
| 80 | +### Solution |
| 81 | + |
| 82 | +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. |
| 83 | + |
| 84 | +## Security rules are not being applied as expected, and I am having difficulties in filtering incoming traffic through my Load Balancer |
| 85 | + |
| 86 | +You may find that traffic is not being filtered as expected via your Load Balancer, and that Instances in your backend are not dropping unauthorized traffic as expected. |
| 87 | + |
| 88 | +### Cause |
| 89 | + |
| 90 | +Instance security groups and/or Load Balancer ACLs are incorrectly configured. |
| 91 | + |
| 92 | +### Solution |
| 93 | + |
| 94 | +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. |
| 95 | +- 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. |
| 96 | +- 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 |
| 97 | +- 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/). |
0 commit comments