node-red / node-red/node-red-nodes
Twitter output node gives 401
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
I had posted this issue in the node-red repo and will remove it from there.
I have a Twitter output node that throws a 401 in the debug tab whenever I attempt to send a payload. I have authenticated it properly (several times) but get this:
Error: HTTP Error 401: Unauthorized, API message: {"errors":[{"code":32,"message":"Could not authenticate you."}]}
I'm sure this used to work fine.
Time Zone/Date & Time are setup properly on node red host and OAuth completes successfully (I see this at the end of the OAuth flow: Authorised - you can close this window and return to Node-RED)
What am I missing?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Twitter output node failure with the reported payload and reviewing the authentication flow that ends with the OAuth success message. Compare the credentials used for that flow with the request that returns HTTP 401; done means the node sends the payload without the reported authentication error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100