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
{{ message }}
This repository was archived by the owner on Oct 29, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 29, 2025. It is now read-only.
orgDomains.ts Match of WEBAPP_URL with ALLOWED_HOSTNAME failed #434
My logs atill have lot of issues, working on them 😋
agenda | @calcom/web:start: ✓ Ready in 1873ms
agenda | @calcom/web:start: {"0":"getDeploymentKey","1":"Signature token not found in database or set in environment variable","_meta":{"runtime":"Nodejs","runtimeVersion":"v18.20.8","hostname":"d6c9ee501fc5","name":"[undefined]","parentNames":"[undefined]","date":"2025-08-06T14:04:11.896Z","logLevelId":5,"logLevelName":"ERROR","path":{"fullFilePath":"/calcom/apps/web/.next/server/chunks/72305.js:1:7062","fileName":"72305.js","fileNameWithLine":"72305.js:1","fileColumn":"7062","fileLine":"1","filePath":"/.next/server/chunks/72305.js","filePathWithLine":"/.next/server/chunks/72305.js:1","method":"s"}}}
agenda | @calcom/web:start: react-i18next:: You will need to pass in an i18next instance by using initReactI18next
agenda | @calcom/web:start: {"0":"RateLimit","1":"Disabled because the UNKEY_ROOT_KEY environment variable was not found.","_meta":{"runtime":"Nodejs","runtimeVersion":"v18.20.8","hostname":"d6c9ee501fc5","name":"[undefined]","parentNames":"[undefined]","date":"2025-08-06T14:04:13.691Z","logLevelId":4,"logLevelName":"WARN","path":{"fullFilePath":"/calcom/apps/web/.next/server/chunks/76526.js:1:7251","fileName":"76526.js","fileNameWithLine":"76526.js:1","fileColumn":"7251","fileLine":"1","filePath":"/.next/server/chunks/76526.js","filePathWithLine":"/.next/server/chunks/76526.js:1","method":"o"}}}
agenda | @calcom/web:start: (node:173) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
agenda | @calcom/web:start: (Use `node --trace-warnings ...` to show where the warning was created)
agenda | @calcom/web:start: [PERF]: getUserEventGroups(1) took 1333.913137987256ms
agenda | @calcom/web:start: [PERF]: getEventTypesFromGroup(1) took 90.83725100755692ms
agenda | @calcom/web:start: `markdownToSafeHTMLClient` should not be used on the server side. use markdownToSafeHTML instead
agenda | @calcom/web:start: [DEPRECATED] Use `createWithEqualityFn` instead of `create` or use `useStoreWithEqualityFn` instead of `useStore`. They can be imported from 'zustand/traditional'. https://github.com/pmndrs/zustand/discussions/1937
For this case I think we can close the issue, right?
About "Signature token not found in database or set in environment variable" and "Disabled because the UNKEY_ROOT_KEY environment variable was not found", do you know any workaround to not print it everytime in logs?
The UNKEY_ROOT_KEY message is only a warning therefore you could remove it by settings the log level higher NEXT_PUBLIC_LOGGER_LEVEL=4.
The signature token sounds like you missing a key on build, but is an error therefore hard to remove from logs. I mean you can set the logger level even higher but yeah.
Activity
krumware commentedon Jul 14, 2025
Related to #319
HannesOberreiter commentedon Aug 6, 2025
fyi setting
RESERVED_SUBDOMAINSto the subdomain path and allowed host only for the top level did solve it for me. Don't ask me why though.ivancarlosti commentedon Aug 6, 2025
It's working fine, thanks!!
My logs atill have lot of issues, working on them 😋
For this case I think we can close the issue, right?
HannesOberreiter commentedon Aug 6, 2025
Yeah the translation failing to load is another issue, which I too have :/ #438
ivancarlosti commentedon Aug 6, 2025
About "Signature token not found in database or set in environment variable" and "Disabled because the UNKEY_ROOT_KEY environment variable was not found", do you know any workaround to not print it everytime in logs?
HannesOberreiter commentedon Aug 6, 2025
The
UNKEY_ROOT_KEYmessage is only a warning therefore you could remove it by settings the log level higherNEXT_PUBLIC_LOGGER_LEVEL=4.The signature token sounds like you missing a key on build, but is an error therefore hard to remove from logs. I mean you can set the logger level even higher but yeah.