scaleway · SamyOubouaziz · Apr 17, 2025 · Apr 16, 2025 · Apr 16, 2025
@@ -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**.
 

@@ -17,14 +17,14 @@ categories:
 
 I cannot create a Serverless Containers namespace.
 
-### Cause
+## Cause
 
 This issue can happen for the following reasons:
 
 - You have created too many Serverless Containers namespaces and reached [your account's quota](/organizations-and-projects/additional-content/organization-quotas/#serverless-containers).
 
 - 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).
@@ -28,6 +28,6 @@ world
 "
 ```
 
-### Solution 
+## Solution 
 
 To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`.
@@ -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.
 

@@ -17,14 +17,14 @@ categories:
 
 I cannot create a Serverless Functions namespace.
 
-### Cause
+## Cause
 
 This issue can happen for the following reasons:
 
 - You have created too many Serverless Functions namespaces and reached [your account's quota](/organizations-and-projects/additional-content/organization-quotas/#serverless-functions).
 
 - 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).
@@ -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`.
@@ -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.
 

@@ -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).
 

@@ -28,6 +28,6 @@ world
 "
 ```
 
-### Solution 
+## Solution 
 
 To avoid issues while injecting environment variables and secrets, we recommend encoding them to `base64`.