Unverified Commit d55c00d8 authored by Sam Ko's avatar Sam Ko Committed by GitHub

docs(errors): minor update to failed-to-find-server-action error page (#76296)

## Why?

Follow up to https://github.com/vercel/next.js/pull/75678#discussion_r1964355401.
parent d1c9aec4
...@@ -12,7 +12,7 @@ When self-hosting your Next.js application across multiple servers, each server ...@@ -12,7 +12,7 @@ When self-hosting your Next.js application across multiple servers, each server
To mitigate this, you can overwrite the encryption key using the `process.env.NEXT_SERVER_ACTIONS_ENCRYPTION_KEY` environment variable. Specifying this variable ensures that your encryption keys are persistent across builds, and all server instances use the same key. This variable **must** be AES-GCM encrypted. To mitigate this, you can overwrite the encryption key using the `process.env.NEXT_SERVER_ACTIONS_ENCRYPTION_KEY` environment variable. Specifying this variable ensures that your encryption keys are persistent across builds, and all server instances use the same key. This variable **must** be AES-GCM encrypted.
In a non-self-hosted environment, you can use a feature such as [Skew Protection](https://vercel.com/docs/deployments/skew-protection) to ensure assets and functions from the previous version are still available, even after a new version is deployed. If you are deploying your Next.js application to Vercel, you can use the feature [Skew Protection](https://vercel.com/docs/deployments/skew-protection) to ensure assets and functions from the previous version are still available, even after a new version is deployed.
## Useful Links ## Useful Links
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment