-
Notifications
You must be signed in to change notification settings - Fork 546
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection refused #17
Comments
Hi. I submitted the patch for connecting over https and it is working for me. The only difference is that I am using the default host and port. |
The patch indeed fixed the issue but the npm package isn't patched yet, as of October 9th. |
Still not updated :( |
Hi, i have the same problem. |
You need to clone the repo instead of using npm. The npm package does not contain the https fix. |
Thanks @dustin10 FYI If you need to use npm to deploy via package.json you can get the source from the last commit using something like this: { Cheers.. |
@Tmeister Great! |
Hiya,
I tried throwing this in a quick app, but am getting connection refused and I can't figure out why. I read thru the module. I guess twitter is refusing the connection?
I've tried variously tracking and following. I also tried using the NPM version and a repo-cloned version, which I noticed had some big differences, one of them being http vs https. Niether worked, both returned the same error above. I also tried running the module on its own, not wrapped in an express app, as below. The app, mostly from your example:
The text was updated successfully, but these errors were encountered: