Skip to content

fix(instances): Document api-metadata as a cause of problem with SSH … #5490

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
Sep 4, 2025
Merged

fix(instances): Document api-metadata as a cause of problem with SSH … #5490

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5a73e82
fix(instances): Document api-metadata as a cause of problem with SSH …
Sep 2, 2025
dd72f4a
Apply suggestions from code review
nerda-codes Sep 3, 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
12 changes: 11 additions & 1 deletion pages/instances/troubleshooting/fix-common-issues.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,7 @@ This page lists the most common issues you may encounter with your Scaleway Inst
- Wrong username: Using `root` versus a custom user.
- 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.
- No access to Scaleway's api-metadata: Api-metadata is responsible for loading the SSH keys.

### Solution
- Check file permissions locally:
Expand All @@ -100,6 +101,15 @@ This page lists the most common issues you may encounter with your Scaleway Inst
- Re-add your SSH Key in the Scaleway console:
- Go to the [SSH keys](https://console.scaleway.com/project/ssh-keys) tab in the **Project** section of theScaleway console, remove the old SSH key, then add your new, correct public key.
- Restart your Instance to re-upload the list of allowed SSH keys.
- Make sure that your Instance has access to the api-metadata by running the following command in the serial console:
```bash
# curl http://169.254.42.42/
```
The following output should display:
```json
{"api": "api-metadata", "description": "Metadata API, just query http://169.254.42.42/conf or http://169.254.42.42/conf?format=json to get info about yourself", "version": "12.23.0"}
```
No output means that access to the api-metadata is blocked. Identify the reason for the block and try running the command above again.

### Additional resources
- [Scaleway Documentation: How to generate an SSH key pair](/organizations-and-projects/how-to/create-ssh-key/)
Expand Down Expand Up @@ -287,4 +297,4 @@ This page lists the most common issues you may encounter with your Scaleway Inst
## Next steps

- Always consult the official [Scaleway Instances Documentation](/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.
- 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.