Manual process for setting Twitter Node credentials?

[Scott C. Lemon]

I have been trying to set-up a new Twitter node for a demo, and no matter what I do I keep getting:

Something went wrong with the authentication process. The following error was returned:
401: dummy error
One known cause of this type of failure is if the clock is wrong on system running Node-RED

The Node-RED install is on my local network, behind NAT, and the clock is accurate.  Nothing else of value in the error logs.

It is attempting an OAuth handshake?  Or?

Is there a manual process around this?

Thanks!

[Julian Knight]

Have you checked the clock? Is it correct?

[Colin Law]

Is the clock timezone correct?

Colin

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/ffa9ab1c-e2b9-45b5-9302-23b19c2554be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Scott C. Lemon]

yep ... and yep ... correct time, and correct timezone ...  :-/

On Wednesday, November 2, 2016 at 3:42:55 PM UTC-6, Colin Law wrote:

Is the clock timezone correct?

Colin

On 2 November 2016 at 16:51, Scott C. Lemon <scott...@gmail.com> wrote:

I have been trying to set-up a new Twitter node for a demo, and no matter what I do I keep getting:

Something went wrong with the authentication process. The following error was returned:
401: dummy error
One known cause of this type of failure is if the clock is wrong on system running Node-RED

The Node-RED install is on my local network, behind NAT, and the clock is accurate.  Nothing else of value in the error logs.

It is attempting an OAuth handshake?  Or?

Is there a manual process around this?

Thanks!

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

[Scott C. Lemon]

I'm baffled.

After I had rebooted my machine, and moved to a new location, it suddenly worked for me!

I'm trying to see if I can recreate the failure.

[Raúl Martínez]

Were you able to find the root cause, I'm still getting the same error

[Scott C. Lemon]

No.  :-(

This is one of those VERY frustrating issues that occurred, and now I can't recreate.  I have NO clue what caused it, but it has to be associated with the OAuth handshake and maybe IP address?

When I was first trying this is simply would not work.  When I shut down, and then went to a new location, it simply worked.

I have not had to try again from scratch, and so I haven't yet determined what the issue was.

[Nicholas O'Leary]

> but it has to be associated with the OAuth handshake and maybe IP address?

I believe it is related to Twitter rate limiting authentications from a particular IP.

The proper long term solution is for us to update the twitter node so you can provide your own twitter app id, rather than use the one baked into the node.

Nick

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/d1f893bd-f13b-47db-89a7-b003696698a2%40googlegroups.com.

[Raúl Martínez]

I read the "clock" authentication does not work behind a proxy. I'll try from a proxy free network later today and let you know if it is related.

[Raúl Martínez]

Hello again,

I validated what I found in a previous article, the twitter authentication mechanism does not work behind a proxy. That's why it worked for us in a "different location"

Regards