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 isn't working: wrong version number #580

Open
burritosoftware opened this issue Jan 28, 2021 · 2 comments
Open

SSL isn't working: wrong version number #580

burritosoftware opened this issue Jan 28, 2021 · 2 comments

Comments

@burritosoftware
Copy link

burritosoftware commented Jan 28, 2021

Hey. I'm trying to connect to Rizon IRC to #chat with SSL, however whenever I enable secure: true in my configuration, I constantly get this message from the debug mode, and it looks like theres some sort of wrong version number?

Network error: Error: 1995905488:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

Connecting without SSL works fine.

EDIT: I see that the underlying library, node-irc, doesn't support TLS, which is a shame. Is there any workaround for this?

@Throne3d
Copy link
Collaborator

Sorry for the (super) late reply – the underlying library, irc-upd, does support TLS, but I'm not sure it's super rigorous (I haven't worked with that part of the code before).

When I tested it locally, I get this version number error when I connect to a port that doesn't support SSL while "secure": true is enabled, but it seems to work as soon as I connect to the right port. Did you put the "port" config inside the "ircOptions" config? ("ircOptions": { "port": 6697, "secure": true }, for example)

@burritosoftware
Copy link
Author

burritosoftware commented Feb 1, 2022

@Throne3d Hi, I'm back after quite a long period. It seems that I am able to connect with "secure": true now, however, this error seems to keep happening when I have sasl on and I try to authenticate via username and password that way.

EDIT: Aaaand I got it to work somehow. I'm assuming port is not by default 6697 even though it says so in README.
EDIT2: It seems that the millisecondsOfSilenceBeforePingSent default value in irc-upd is way too short, for my testing I set it to 100 seconds and it has solved the problem completely.

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

No branches or pull requests

2 participants