Skip to content

Commit 4e31d89

Browse files
committed
docs(gen): update
1 parent 5160876 commit 4e31d89

File tree

2 files changed

+56
-4
lines changed

2 files changed

+56
-4
lines changed

pages/object-storage/troubleshooting/cannot-access-data.mdx

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
meta:
3-
title: I cannot access my data
4-
description: Troubleshoot issues related to accessing data in Scaleway Object Storage.
3+
title: I cannot access my objects
4+
description: Troubleshoot issues related to accessing objects in Scaleway Object Storage.
55
content:
6-
h1: I cannot access my data
7-
paragraph: Troubleshoot issues related to accessing data in Scaleway Object Storage.
6+
h1: I cannot access my objects
7+
paragraph: Troubleshoot issues related to accessing objects in Scaleway Object Storage.
88
tags: help troubleshooting object storage blocked data locked fail unable impossible
99
dates:
1010
validation: 2024-12-09
@@ -26,6 +26,10 @@ I am experiencing issues while trying to access my buckets and objects stored on
2626

2727
- Go to the [Status page](https://status.scaleway.com/) to see if there is an ongoing incident on the Scaleway infrastructure.
2828

29+
- Make sure that you are using a valid [API key](https://console.scaleway.com/iam/api-keys).
30+
31+
- Make sure that the bearer of the API key (IAM [user](/iam/concepts/#user) or [application](/iam/concepts/#application)) has the appropriate [IAM permission set](/iam/how-to/view-permission-sets/) to perform the desired actions.
32+
2933
- Retrieve the logs of your buckets using any Amazon S3-compatible tool to identify the cause of the problem:
3034
- [Rclone](https://rclone.org/docs/#logging)
3135
- [S3cmd](https://s3tools.org/usage)
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
meta:
3+
title: I am experiencing DNS/Edge Services issues
4+
description: Learn to troubleshoot issues when using Edge Services or DNS with Scaleway Object Storage.
5+
content:
6+
h1: I am experiencing DNS/Edge Services issues
7+
paragraph: Learn to troubleshoot issues when using Edge Services or DNS with Scaleway Object Storage.
8+
tags: help troubleshooting object storage dns domains edge services cannot does not work
9+
dates:
10+
validation: 2025-03-24
11+
posted: 2025-03-24
12+
categories:
13+
- storage
14+
- object-storage
15+
---
16+
17+
<Macro id="requirements" />
18+
19+
- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
20+
21+
## Problem
22+
23+
I am experiencing DNS and/or Edge Services issues when using Scaleway Object Storage.
24+
25+
## Possible cause
26+
27+
There are many factors that can cause DNS and Edge Services issues with Scaleway Object Storage. However, most of the time, the root cause does not come from the Object Storage configuration, but from Domains and DNS, or Edge Services.
28+
29+
## Solutions
30+
31+
According to the type of issue you are experiencing:
32+
33+
- Refer to the [Edge Services troubleshooting documentation](/edge-services/troubleshooting/) for dedicated help pages.
34+
35+
- Refer to the [Domains and DNS troubleshooting documentation](/domains-and-dns/troubleshooting/) for dedicated help pages.
36+
37+
## Going further
38+
39+
If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below:
40+
- Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`)
41+
- Bucket name
42+
- Object name (if the request concerns an object)
43+
- Request type (PUT, GET, etc.)
44+
- HTTP status code
45+
- Date and time (timestamp)
46+
- User-agent (SDK, client, console, etc.)
47+
- Transaction ID (if possible)
48+
- Log / trace of the error (if possible)

0 commit comments

Comments
 (0)