We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I attempted to run the setup:
npx @sentry/wizard@latest -i nextjs --saas --org my-org--project javascript-nextjs
and I am getting the following error
■ Loading Wizard failed. │ ● { │ "message": "self-signed certificate in certificate chain", │ "name": "Error", │ "stack": "Error: self-signed certificate in certificate chain\n at AxiosError.from (C:\\Users\\\\AppData\\Local\\npm-cache\\_npx\\ddb126e78325956c\\node_modules\\axios\\dist\\node\\axios.cjs:857:14)\n at RedirectableRequest.handleRequestError (C:\\Users\\\\AppData\\Local\\npm-cache\\_npx\\ddb126e78325956c\\node_modules\\axios\\dist\\node\\axios.cjs:3169:25)\n at RedirectableRequest.emit (node:events:518:28)\n at RedirectableRequest.emit (node:domain:489:12)\n at eventHandlers.<computed> (C:\\Users\\\\AppData\\Local\\npm-cache\\_npx\\ddb126e78325956c\\node_modules\\follow-redirects\\index.js:49:24)\n at ClientRequest.emit (node:events:530:35)\n at ClientRequest.emit (node:domain:489:12)\n at emitErrorEvent (node:_http_client:101:11)\n at TLSSocket.socketErrorListener (node:_http_client:504:5)\n at TLSSocket.emit (node:events:518:28)\n at Axios.request (C:\\Users\\\\AppData\\Local\\npm-cache\\_npx\\ddb126e78325956c\\node_modules\\axios\\dist\\node\\axios.cjs:4258:41)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async makeInitialWizardHashRequest (C:\\Users\\\\AppData\\Local\\npm-cache\\_npx\\ddb126e78325956c\\node_modules\\@sentry\\wizard\\dist\\src\\utils\\clack\\index.js:834:17)\n at async askForWizardLogin (C:\\Users\\\\AppData\\Local\\npm-cache\\_npx\\ddb126e78325956c\\node_modules\\@sentry\\wizard\\dist\\src\\utils\\clack\\index.js:770:24)\n at async getOrAskForProjectData (C:\\Users\\\\AppData\\Local\\npm-cache\\_npx\\ddb126e78325956c\\node_modules\\@sentry\\wizard\\dist\\src\\utils\\clack\\index.js:668:35)\n at async runNextjsWizardWithTelemetry (C:\\Users\\\\AppData\\Local\\npm-cache\\_npx\\ddb126e78325956c\\node_modules\\@sentry\\wizard\\dist\\src\\nextjs\\nextjs-wizard.js:69:67)\n at async C:\\Users\\\\AppData\\Local\\npm-cache\\_npx\\ddb126e78325956c\\node_modules\\@sentry\\wizard\\dist\\src\\telemetry.js:22:25\n at async withTelemetry (C:\\Users\\\\AppData\\Local\\npm-cache\\_npx\\ddb126e78325956c\\node_modules\\@sentry\\wizard\\dist\\src\\telemetry.js:16:16)\n at async run (C:\\Users\\\\AppData\\Local\\npm-cache\\_npx\\ddb126e78325956c\\node_modules\\@sentry\\wizard\\dist\\src\\run.js:135:13)", │ "config": { │ "transitional": { │ "silentJSONParsing": true, │ "forcedJSONParsing": true, │ "clarifyTimeoutError": false │ }, │ "adapter": [ │ "xhr", │ "http", │ "fetch" │ ], │ "transformRequest": [ │ null │ ], │ "transformResponse": [ │ null │ ], │ "timeout": 0, │ "xsrfCookieName": "XSRF-TOKEN", │ "xsrfHeaderName": "X-XSRF-TOKEN", │ "maxContentLength": -1, │ "maxBodyLength": -1, │ "env": {}, │ "headers": { │ "Accept": "application/json, text/plain, */*", │ "User-Agent": "axios/1.8.2", │ "Accept-Encoding": "gzip, compress, deflate, br" │ }, │ "method": "get", │ "url": "https://sentry.io/api/0/wizard/", │ "allowAbsoluteUrls": true │ }, │ "code": "SELF_SIGNED_CERT_IN_CHAIN" │ } │ └ Please try again in a few minutes and let us know if this issue persists: https://github.com/getsentry/sentry-wizard/issues
The text was updated successfully, but these errors were encountered:
Hello, this might not be an issue with the Wizard but with your npm setup. Do you use a custom registry?
Sorry, something went wrong.
No branches or pull requests
I attempted to run the setup:
npx @sentry/wizard@latest -i nextjs --saas --org my-org--project javascript-nextjs
and I am getting the following error
The text was updated successfully, but these errors were encountered: