Problem with license (retool-onpremise-api)

Self Hosted Retool
1

Hello this is the error from docker: retool-onpremise-api (ps license is new)

INF Rechecking license status... | timestamp=2023-02-16T10:01:07.941Z

(node:22) [DEP0111] DeprecationWarning: Access to process.binding('http_parser') is deprecated.

(Use retool_backend --trace-deprecation ... to show where the warning was created)

(node:22) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /snapshot/retool_development/node_modules/@tryretool/common/package.json.

Update this package.json to use a subpath pattern like "./*".

(node:22) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /node_modules/@tryretool/workflowsBackend/package.json.

Update this package.json to use a subpath pattern like "./*".

(node:22) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /node_modules/@tryretool/common/package.json.

Update this package.json to use a subpath pattern like "./*".

(node:22) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /packages/common/package.json imported from /packages/common/build/workflows/utils.js.

Update this package.json to use a subpath pattern like "./*".

ERR [object Object] | timestamp=2023-02-16T10:01:08.466Z

Encountered error

Error: Could not validate a license

at checkLicenseStatus (/snapshot/retool_development/backend/transpiled/server/modules/licensing.js)

at async startOnPremServer (/snapshot/retool_development/backend/transpiled/server/main.js)

at async main (/snapshot/retool_development/backend/transpiled/server/main.js)

2

Hey @Daniele_Bulgarelli! Happy to help here. Just to double check, was your Retool instance working before? And how have you deployed Retool?

Usually this error means your license key is either incorrect or missing (thank you for sending those logs by the way) and this causes your license checks to fail (your Retool instance pings our servers every 6 hours to ensure that your license key is valid).

This can also happen if you have a trailing whitespace at the end of your license key (most common in Kubernetes deployments).