Skip to content

fix(edge): add troubleshooting indexes #4659

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 21, 2025
Merged

fix(edge): add troubleshooting indexes #4659

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2bed38d
fix(edge): add troubleshooting indexes
RoRoJ Mar 19, 2025
c58708c
fix(lb): remove irrelevant troubleshooting
RoRoJ Mar 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions menu/navigation.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3452,6 +3452,10 @@
],
"label": "Additional content",
"slug": "reference-content"
},
{
"label": "Troubleshooting",
"slug": "troubleshooting"
}
],
"label": "Edge Services",
Expand Down
14 changes: 0 additions & 14 deletions pages/load-balancer/troubleshooting/configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,20 +40,6 @@ 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 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.

### Cause

You are entering an incorrect IP address for your resource, or using private IP address that is outside the standard range for private networks.

### 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 resource, and that it is attached to the same Private Network as the Load Balancer.
- 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.


## My Load Balancer's Elastic Metal backend servers added via private IPs are all down

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.
Expand Down
6 changes: 6 additions & 0 deletions pages/troubleshooting/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -180,6 +180,12 @@ content:
label="Load Balancer"
/>

<ProductCardIllustration
productLogo="edgeServices"
url="/edge-services/troubleshooting/"
label="Edge Services"
/>

<ProductCardIllustration
productLogo="publicGateway"
url="/public-gateways/troubleshooting/"
Expand Down