You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)
This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.
I deployed my production build to Kubernetes, and in the process of creating the secret from a .env file, the actual value contained the double quotes from the .env file in-cluster
From running env in bash in the container
CLERK_SECRET_KEY="sk_test_6o..."
Expected behavior:
A clearer error, if possible?
detect and strip the quotes, more resilient
Actual behavior:
500 on the website homepage with little error context
I looked into chunk/167.js and noticed clerk domains.
Eventually the atob function was the breadcrumb that led to look at the values of the vars.
DOMException [InvalidCharacterError]: Invalid character
at new DOMException (node:internal/per_context/domexception:53:5)
at __node_internal_ (node:internal/util:695:10)
at atob (node:buffer:1330:13)
at u (/app/.next/server/chunks/167.js:1:797)
at /app/.next/server/chunks/167.js:1:991
at h (/app/.next/server/chunks/167.js:1:1040)
at t0 (/app/.next/server/chunks/167.js:5:44563)
at 14452 (/app/.next/server/chunks/452.js:1:1558)
at t (/app/.next/server/webpack-runtime.js:1:127)
at 50854 (/app/.next/server/chunks/13.js:1:10880)
[Error: An error occurred in the Server Components render. The specific message is omitted in production builds to avoid leaking sensitive details. A digest property is included on this error instance which may provide additional details about the nature of the error.] {
digest: '1890365856'
}
Hello @verdverm!
I haven't managed to replicate the issue, I've tried it and the environment variables seems to load as expected, can you provide a minimal reproduction so I can have a better look at it?
Also it's not so clear if that's a Clerk of Next.js issue, as we are depending on Next.js to load the variables, we don't do any parsing of the environment variables.
Preliminary Checks
Reproduction
n/a
Publishable key
pk_test_bWFqb3ItZ29waGVyLTY0LmNsZXJrLmFjY291bnRzLmRldiQ
Description
Steps to reproduce:
"
end up in the ENV varI deployed my production build to Kubernetes, and in the process of creating the secret from a .env file, the actual value contained the double quotes from the .env file in-cluster
From running
env
in bash in the containerExpected behavior:
Actual behavior:
500 on the website homepage with little error context
I looked into
chunk/167.js
and noticed clerk domains.Eventually the
atob
function was the breadcrumb that led to look at the values of the vars.Environment
List of package version
The text was updated successfully, but these errors were encountered: