From d5fc4e1dc26979e42f8f8190b7eab04623261f49 Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 16 Apr 2025 16:40:48 +0200 Subject: [PATCH 1/2] fix(srv): harmonize H2/H3 in serverless troubleshootings MTA-5945 --- .../troubleshooting/502-error-when-scaling.mdx | 4 ++-- .../troubleshooting/cannot-create-namespace.mdx | 4 ++-- .../troubleshooting/cannot-inject-secret-variable.mdx | 2 +- .../troubleshooting/tests-fail-on-container.mdx | 4 ++-- .../troubleshooting/cannot-create-namespace.mdx | 4 ++-- .../troubleshooting/cannot-inject-secret-variable.mdx | 4 ++-- .../troubleshooting/tests-fail-on-function.mdx | 4 ++-- pages/serverless-functions/troubleshooting/timeout-error.mdx | 4 ++-- 8 files changed, 15 insertions(+), 15 deletions(-) diff --git a/pages/serverless-containers/troubleshooting/502-error-when-scaling.mdx b/pages/serverless-containers/troubleshooting/502-error-when-scaling.mdx index 1f63e11556..648af340e2 100644 --- a/pages/serverless-containers/troubleshooting/502-error-when-scaling.mdx +++ b/pages/serverless-containers/troubleshooting/502-error-when-scaling.mdx @@ -17,13 +17,13 @@ categories: 502 errors can sometimes occur on Serverless Containers during the autoscaling process when new container instances are being created. -### Cause +## Cause When a new instance is created, the Serverless health check verification is performed by default on the HTTP port. Once the port is opened, the resource is considered ready, and traffic starts being forwarded to it. This issue typically occurs when traffic is sent too early to the newly created container before it is fully deployed. -### Possible solutions +## Possible solutions To ensure the Serverless Container is completely ready, both in terms of the HTTP port and the software scope, it is recommended to use **custom health checks**. diff --git a/pages/serverless-containers/troubleshooting/cannot-create-namespace.mdx b/pages/serverless-containers/troubleshooting/cannot-create-namespace.mdx index 7818a3be2a..b55f3e4a34 100644 --- a/pages/serverless-containers/troubleshooting/cannot-create-namespace.mdx +++ b/pages/serverless-containers/troubleshooting/cannot-create-namespace.mdx @@ -17,7 +17,7 @@ categories: I cannot create a Serverless Containers namespace. -### Cause +## Cause This issue can happen for the following reasons: @@ -25,6 +25,6 @@ This issue can happen for the following reasons: - You have created too many Registry namespaces and reached [your account's quota](/organizations-and-projects/additional-content/organization-quotas/#container-registry). -### Possible solutions +## Possible solutions Make sure that you have not exceeded the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-containers/#path-namespaces-list-all-your-namespaces). \ No newline at end of file diff --git a/pages/serverless-containers/troubleshooting/cannot-inject-secret-variable.mdx b/pages/serverless-containers/troubleshooting/cannot-inject-secret-variable.mdx index 0b5a7e5e43..4b896a78e0 100644 --- a/pages/serverless-containers/troubleshooting/cannot-inject-secret-variable.mdx +++ b/pages/serverless-containers/troubleshooting/cannot-inject-secret-variable.mdx @@ -28,6 +28,6 @@ world " ``` -### Solution +## Solution To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`. diff --git a/pages/serverless-containers/troubleshooting/tests-fail-on-container.mdx b/pages/serverless-containers/troubleshooting/tests-fail-on-container.mdx index 9444fd7f8e..50f9016b7d 100644 --- a/pages/serverless-containers/troubleshooting/tests-fail-on-container.mdx +++ b/pages/serverless-containers/troubleshooting/tests-fail-on-container.mdx @@ -17,11 +17,11 @@ categories: I get error messages when testing Serverless Containers using the Scaleway Console. -### Cause +## Cause Testing **Private** Serverless Containers is not possible using the Scaleway console due to CORS limitations. -### Possible solutions +## Possible solutions - Change the visibility of your function to **public**. Public containers can be executed anonymously. diff --git a/pages/serverless-functions/troubleshooting/cannot-create-namespace.mdx b/pages/serverless-functions/troubleshooting/cannot-create-namespace.mdx index 025bd952e6..6eaa9b70c4 100644 --- a/pages/serverless-functions/troubleshooting/cannot-create-namespace.mdx +++ b/pages/serverless-functions/troubleshooting/cannot-create-namespace.mdx @@ -17,7 +17,7 @@ categories: I cannot create a Serverless Functions namespace. -### Cause +## Cause This issue can happen for the following reasons: @@ -25,6 +25,6 @@ This issue can happen for the following reasons: - You have created too many Registry namespaces and reached [your account's quota](/organizations-and-projects/additional-content/organization-quotas/#container-registry). -### Possible solutions +## Possible solutions Make sure that you have not exceeded the maximum number of allowed namespaces with the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-functions/#path-namespaces-list-all-your-namespaces). \ No newline at end of file diff --git a/pages/serverless-functions/troubleshooting/cannot-inject-secret-variable.mdx b/pages/serverless-functions/troubleshooting/cannot-inject-secret-variable.mdx index 63f0884702..8634416409 100644 --- a/pages/serverless-functions/troubleshooting/cannot-inject-secret-variable.mdx +++ b/pages/serverless-functions/troubleshooting/cannot-inject-secret-variable.mdx @@ -17,7 +17,7 @@ categories: My environment variable or secret is not properly injected in my function during its execution. -### Cause +## Cause Environment variables or secrets that are too large, contain carriage returns and spread over several lines, as shown below, will not be injected properly. @@ -28,6 +28,6 @@ world " ``` -### Solution +## Solution To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`. \ No newline at end of file diff --git a/pages/serverless-functions/troubleshooting/tests-fail-on-function.mdx b/pages/serverless-functions/troubleshooting/tests-fail-on-function.mdx index 92149e3e1b..d13bfd7277 100644 --- a/pages/serverless-functions/troubleshooting/tests-fail-on-function.mdx +++ b/pages/serverless-functions/troubleshooting/tests-fail-on-function.mdx @@ -17,11 +17,11 @@ categories: I get error messages when testing Serverless Functions using the Scaleway Console. -### Cause +## Cause Testing **Private** Serverless Functions is not possible using the Scaleway console due to CORS limitations. -### Possible solutions +## Possible solutions - Change the visibility of your function to **public**. Public functions can be executed anonymously. diff --git a/pages/serverless-functions/troubleshooting/timeout-error.mdx b/pages/serverless-functions/troubleshooting/timeout-error.mdx index 50dac1975c..ed6f801bc1 100644 --- a/pages/serverless-functions/troubleshooting/timeout-error.mdx +++ b/pages/serverless-functions/troubleshooting/timeout-error.mdx @@ -17,11 +17,11 @@ categories: I am experiencing timeout errors when using Scaleway Serverless Functions. -### Cause +## Cause Timeout happens when your function cannot return any result in the defined amount of time. -### Possible solutions +## Possible solutions - Increase the Timeout parameter in the [Scaleway console](https://console.scaleway.com/) or with the [API](https://www.scaleway.com/en/developers/api/serverless-functions/#path-functions-update-an-existing-function). From b55097632db7b55bbea4286b268d09ddb97b23fd Mon Sep 17 00:00:00 2001 From: SamyOubouaziz Date: Wed, 16 Apr 2025 16:42:15 +0200 Subject: [PATCH 2/2] fix(srv): harmonize H2/H3 in serverless troubleshootings --- .../troubleshooting/cannot-inject-secret-variable.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/serverless-jobs/troubleshooting/cannot-inject-secret-variable.mdx b/pages/serverless-jobs/troubleshooting/cannot-inject-secret-variable.mdx index f60610fd35..4bcd82bd99 100644 --- a/pages/serverless-jobs/troubleshooting/cannot-inject-secret-variable.mdx +++ b/pages/serverless-jobs/troubleshooting/cannot-inject-secret-variable.mdx @@ -28,6 +28,6 @@ world " ``` -### Solution +## Solution To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`.