Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

401 error when listing issues

See original GitHub issue

Expected

setup with jira
able to view active issues with jira ls.

Actual

setup with jira is successful (entering site address/username/password)
the following error is received when running jira ls (both powershell and cmd). I have at least 8 issues assigned to me in Jira.

jira ls
(node:25112) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:25112) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
Error: got 401 response
    at Response.toError (C:\Users\<username>\AppData\Roaming\npm\node_modules\cmd-jira\node_modules\superagent\lib\node\response.js:100:13)
    at Response.setStatusProperties (C:\Users\<username>\AppData\Roaming\npm\node_modules\cmd-jira\node_modules\superagent\lib\node\response.js:179:12)
    at new Response (C:\Users\<username>\AppData\Roaming\npm\node_modules\cmd-jira\node_modules\superagent\lib\node\response.js:40:8)
    at IncomingMessage.<anonymous> (C:\Users\<username>\AppData\Roaming\npm\node_modules\cmd-jira\node_modules\superagent\lib\node\index.js:712:22)
    at IncomingMessage.emit (events.js:326:22)
    at endReadableNT (_stream_readable.js:1244:12)
    at processTicksAndRejections (internal/process/task_queues.js:80:21) {
  status: 401
}
No issues

System info

Windows 10 pro
jira-cmd vv0.5.4
npm v6.14.6

Further research

From some googling, I found this thread.

I tried logging in with just the first part of my email address, before the @ symbol
I received the same error.

Issue Analytics

State:
Created 3 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

2reactions

manish-makwanacommented, Jul 28, 2020

BTW, still getting the warning about setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to 0. Anything I can do to suppress or fix this? I tried setting it to 1 in powershell:

PS >$env:NODE_TLS_REJECT_UNAUTHORIZED=1

PS >get-childitem Env:NODE_TLS_REJECT_UNAUTHORIZED

Name                           Value
----                           -----
NODE_TLS_REJECT_UNAUTHORIZED   1

But the warning still shows up when running jira ls etc.

(node:17880) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.

0reactions

palashkulshcommented, Jul 29, 2020

I’ll be creating a new issue to track handling of this warning.