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

SSL Failed to connect #60

Closed
zephrax opened this issue Nov 8, 2011 · 5 comments
Closed

SSL Failed to connect #60

zephrax opened this issue Nov 8, 2011 · 5 comments

Comments

@zephrax
Copy link
Contributor

zephrax commented Nov 8, 2011

I'm trying to connect to my own irc server using SSL and I got this message:

8 Nov 20:06:00 - UNABLE_TO_VERIFY_LEAF_SIGNATURE
8 Nov 20:06:11 - Unhandled message: { command: 'ERROR',
rawCommand: 'ERROR',
commandType: 'normal',
args: [ 'Closing link: (unknown@ip_address_here) [Registration timeout]' ] }
8 Nov 20:06:11 - Connection got "close" event
8 Nov 20:06:11 - Disconnected: reconnecting
8 Nov 20:06:11 - Waiting 2000ms before retrying

The server is: irc.kernelpanic.com.ar:6697 (SSL) if you wanna try. I don't know what's going on with the link, but maybe it could be an incompatibility with the ircd I'm running.

The server is an Inspircd 2.0.5, hope this can help you.

@zephrax
Copy link
Contributor Author

zephrax commented Nov 8, 2011

I hardcoded the condition to check how it works, and I got connected. But I'm having another problem..

user.match in the case "rpl_namreply" resturns null and break the execution.

The message object is the following:

{ prefix: 'irc.kernelpanic.com.ar',
server: 'irc.kernelpanic.com.ar',
command: 'rpl_namreply',
rawCommand: '353',
commandType: 'reply',
args:
[ 'niobe',
'=',
'#niobe',
'@zephrax neiker @chanserv niobe ' ] }

Maybe everything is related.

@martynsmith
Copy link
Owner

Since I've merged those two pull requests, I believe this issue is resolved.

Can you please re-open this if you're still experiencing issues?

Thanks,

@4poc
Copy link
Contributor

4poc commented Aug 10, 2012

I got the same error, is the patch not in master (anymore)?
looks like its broken again by this commit: 3b3c01f

@martynsmith
Copy link
Owner

Hmmm, I suspect you're right (looks like I did a poor job of reviewing that pull request :-(

Are you able to make a pull request for this?, otherwise I'll try get around to fixing this up :-)

@4poc
Copy link
Contributor

4poc commented Aug 16, 2012

sure: #102

Half-Shot referenced this issue in matrix-org/node-irc Feb 23, 2019
Update nyc to the latest version 🚀
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

3 participants