You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently almost all node-red supports proxy when you set the http_proxy environment variable.
Twitter node does not support it because it depends on oauth package and it does not support proxys (there are at least 5 pull requests to add proxy support to it, some of them from 2012 but none was accepted) so you cannot authenticate so you cannot work with it behind a proxy.
The message we receive points to clock, etc... It could be changed too (the error that came is ETIMEDOUT - it has nothing to do with clock)
My suggestion here is to depend only from request which already supports oauth.
The text was updated successfully, but these errors were encountered:
Currently almost all node-red supports proxy when you set the http_proxy environment variable.
Twitter node does not support it because it depends on
oauth
package and it does not support proxys (there are at least 5 pull requests to add proxy support to it, some of them from 2012 but none was accepted) so you cannot authenticate so you cannot work with it behind a proxy.The message we receive points to clock, etc... It could be changed too (the error that came is ETIMEDOUT - it has nothing to do with clock)
My suggestion here is to depend only from
request
which already supportsoauth
.The text was updated successfully, but these errors were encountered: