# Problems connecting to twitter node

**URL:** <https://discourse.nodered.org/t/problems-connecting-to-twitter-node/7862>\
**Category:** General\
**Created:** [12 February 2019 06:47 UTC](https://discourse.nodered.org/t/problems-connecting-to-twitter-node/7862 "2019-02-12T06:47:17Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![faisalchishti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/faisalchishti/32/18445_2.png) [@faisalchishti](https://discourse.nodered.org/u/faisalchishti)\
**Post date:** [12 February 2019 06:47 UTC](https://discourse.nodered.org/t/problems-connecting-to-twitter-node/7862/1 "2019-02-12T06:47:17Z")

</div>

I am trying to connect to twitter node and getting below error.

12 Feb 12:14:58 - [warn] [twitter in:Keyword search] stream error: Error: connect ETIMEDOUT

I am connected on my office network and suspect it is the firewall that is blocking it.

Is there a way to run twitter node behind a proxy? Any workarounds?

EDIT: Same with the feed parser node. I am getting below error:

[error] [feedparse:BT SPORT RSS] Error: ETIMEDOUT

Is there a way to use Twitter/feed parser nodes behind a proxy?

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [12 February 2019 07:11 UTC](https://discourse.nodered.org/t/problems-connecting-to-twitter-node/7862/2 "2019-02-12T07:11:11Z")

</div>

Check with your IT security department as to whether you are allowed to access Twitter over your corporate network. It may be blocked.

---

<div class="post-metadata">

**Author:** ![faisalchishti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/faisalchishti/32/18445_2.png) [@faisalchishti](https://discourse.nodered.org/u/faisalchishti)\
**Post date:** [12 February 2019 07:15 UTC](https://discourse.nodered.org/t/problems-connecting-to-twitter-node/7862/3 "2019-02-12T07:15:47Z")

</div>

I can access twitter on my browser. Is there a way to run the Twitter node behind a proxy?

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [12 February 2019 08:55 UTC](https://discourse.nodered.org/t/problems-connecting-to-twitter-node/7862/4 "2019-02-12T08:55:41Z")

</div>

You can configure a proxy for Node-RED, that may help.

> <https://github.com/node-red/node-red/issues/353>

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [12 February 2019 09:11 UTC](https://discourse.nodered.org/t/problems-connecting-to-twitter-node/7862/5 "2019-02-12T09:11:30Z")

</div>

But before going to the effort, talk to your corporate IT.

---

<div class="post-metadata">

**Author:** ![faisalchishti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/faisalchishti/32/18445_2.png) [@faisalchishti](https://discourse.nodered.org/u/faisalchishti)\
**Post date:** [12 February 2019 09:58 UTC](https://discourse.nodered.org/t/problems-connecting-to-twitter-node/7862/6 "2019-02-12T09:58:56Z")

</div>

Spoke to IT, the Twitter node needs to be run behind a proxy but I am not sure if the Twitter node allows that. I don't see any way to do it.

---

<div class="post-metadata">

**Author:** ![faisalchishti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/faisalchishti/32/18445_2.png) [@faisalchishti](https://discourse.nodered.org/u/faisalchishti)\
**Post date:** [12 February 2019 09:59 UTC](https://discourse.nodered.org/t/problems-connecting-to-twitter-node/7862/7 "2019-02-12T09:59:29Z")

</div>

This does not help in running Twitter node behind a proxy.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [13 February 2019 10:31 UTC](https://discourse.nodered.org/t/problems-connecting-to-twitter-node/7862/8 "2019-02-13T10:31:46Z")

</div>

Hi @faisalchishti

we don't have any immediate plans for the Twitter node. This is the first time the question of running it behind a proxy has come up. I can't imagine it would be too much work to add - just not on my todo list.

If someone wanted to take it on, it would be nice first contribution.

(No need to ping me on twitter - if you want my input on a subject, @-mention me here)

---

<div class="post-metadata">

**Author:** ![faisalchishti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/faisalchishti/32/18445_2.png) [@faisalchishti](https://discourse.nodered.org/u/faisalchishti)\
**Post date:** [13 February 2019 10:56 UTC](https://discourse.nodered.org/t/problems-connecting-to-twitter-node/7862/9 "2019-02-13T10:56:00Z")

</div>

Hi @knolleary

I see issue #243 was raised in 2016 for the same. Hope somebody with the right expertise picks it up and gets it running.

> feat(twitter): Add proxy support on twitter node.  
> #243 opened Oct 18, 2016 by Bigous

Thanks for the update!