Skip to content

Commit d1aecc6

Browse files
SamyOubouazizbene2k1RoRoJ
authored
Apply suggestions from code review
Co-authored-by: Benedikt Rollik <[email protected]> Co-authored-by: Rowena Jones <[email protected]>
1 parent 2c1086b commit d1aecc6

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

console/account/how-to/recover-a-lost-password.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ If you forget or lose your password, you can request to reset it.
3838
4. Enter your new password and click **Reset password** to set the new password for your account. You are redirected to the Login page.
3939
5. Log in to the console with your email address and your new password.
4040

41-
## Recover your password if you lost your email account
41+
## Recover your password if you lost access to your email account
4242

4343
If you lose access to your email account, you will not be able to reset the password directly from the Scaleway console.
4444

faq/serverless-jobs.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ Scaleway Serverless Jobs is part of the Scaleway ecosystem, it can therefore be
9292

9393
## Can I run multiple Serverless Jobs at the same time?
9494

95-
When starting a Job, you can use contextual options to define the number of jobs to execute at the same time. Refer to the [dedicated documentation](/serverless/jobs/how-to/run-job/#how-to-run-a-job-with-contextual-options) for more information.
95+
When starting a job, you can use contextual options to define the number of jobs to execute at the same time. Refer to the [dedicated documentation](/serverless/jobs/how-to/run-job/#how-to-run-a-job-with-contextual-options) for more information.
9696

9797
## How can I configure access to a Private Network?
9898

serverless/containers/how-to/add-a-custom-domain-to-a-container.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ HTTP-01 challenge failure (and by extension, a custom domain in `error` status)
8181
| DNS record is not available yet. | This can be the case if the custom domain is created immediately after the CNAME is configured on your DNS provider side. | As a rule of thumb, wait a few minutes after creating the CNAME on your DNS provider, or at least wait until the DNS record is available on main resolvers (`1.1.1.1`, `8.8.8.8`). |
8282
| DNS cache is stale (still pointing to an old endpoint). | If the custom domain was pointing to another endpoint before adding the CNAME record to the Serverless Container, and if the TTL is greater than the maximum time of the check (3 min), it can sometimes happen that the custom domain still resolves to the old endpoint, thus making the challenge fail. | Wait until DNS entry is available and use a smaller TTL. |
8383
| Negative DNS cache is stale | If the initial check fails (DNS record is not available yet), and the negative TTL configured on your DNS provider side is high, the negative TTL will prevent subsequent checks from querying the nameserver again, until it expires. Depending on the negative TTL configured, this can take more or less time. | Either reduce the negative TTL in your DNS provider configuration, or just wait until you are sure DNS record is available. If you already tried to add the custom domain and faced this issue, you likely have to wait for the negative TTL to expire before making another attempt (so the cache can also expire on our side). |
84-
| Route `/.well-known/acme-challenge` is not handled correctly. | To perform the HTTP-01 challenge, a call will be made on `<your_custom_domain>/.well-known/acme-challenge/<token>`. If you are using a proxying/caching tool (like Cloudflare) between the custom domain and the Serverless Container endpoint, a cached version of that route can be served, making the check fails. | Do not configure caching rules for routes starting with `/.well-known/acme-challenge`. Rerfer to the example below with Cloudflare. |
84+
| Route `/.well-known/acme-challenge` is not handled correctly. | To perform the HTTP-01 challenge, a call will be made on `<your_custom_domain>/.well-known/acme-challenge/<token>`. If you are using a proxying/caching tool (like Cloudflare) between the custom domain and the Serverless Container endpoint, a cached version of that route can be served, making the check fails. | Do not configure caching rules for routes starting with `/.well-known/acme-challenge`. Refer to the example below with Cloudflare. |
8585

8686
Example of configuration on Cloudflare to disable caching with "Cache rules":
8787

0 commit comments

Comments
 (0)