Skip to content
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

Library never connects to server #451

Closed
belldandu opened this issue Mar 10, 2016 · 2 comments
Closed

Library never connects to server #451

belldandu opened this issue Mar 10, 2016 · 2 comments

Comments

@belldandu
Copy link

hey guys so i wrote a script that uses your library a few months back and since the recent update your library no longer connects. i have made no changes to the script as it is the same as when it was first made and worked
https://gist.github.com/kamijoutouma/16224ead91cd25977d37

Can someone explain why code that is exactly the same with no changes just suddenly stops working?

I didn't see any changes to the docs and the code follows the docs almoust to a T. yet for some reason the node irc library doesn't even bother to even try connecting. it never even makes it to any events to even tell me what the error is.

So unless you guys made some undocumented completely broken changes i am stumped.

@jirwin
Copy link
Collaborator

jirwin commented Mar 10, 2016

Spent some time debugging this with @KamijouTouma and it appears the issue lies in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812708.

Closing this as it has to do with openssl on the server and is out of the control of node-irc.

@jirwin jirwin closed this as completed Mar 10, 2016
@belldandu
Copy link
Author

@jirwin Gonna note that this workaround does fix some of the issues. Found it after doing a bit of digging over at letsencrypt who i use for ssl anyway.

apt-get remove ca-certificates
apt-get autoremove
apt-get install ca-certificates

Viola i can connect to espernet now via the command openssl s_client -CApath /etc/ssl/certs -connect irc.esper.net:6697 but still cant use the secure option in the script (which is kinda weird) and the command doesn't work for all of their servers so i think they use different certs for each server anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants