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

Cannot connect to some servers that IRSSI can. #436

Open
gabevenberg opened this issue Nov 13, 2024 · 4 comments
Open

Cannot connect to some servers that IRSSI can. #436

gabevenberg opened this issue Nov 13, 2024 · 4 comments

Comments

@gabevenberg
Copy link

Im trying to connect to the IRC server at mbrserver.com:6667, which works with IRSSI, but not with tiny. With tiny, I receive an error saying I received a corrupt message. Ill see if I can do some debugging in wireshark later this week...

@osa1 osa1 added the bug label Nov 13, 2024
@osa1
Copy link
Owner

osa1 commented Nov 13, 2024

IIRC we log all incoming messages if you enable logging with TINY_LOG=trace tiny. You may be able to see the message that's causing issues in the log file there. The log file will be in your logs directory (if you specify that in your tiny config) or in the current working directory, with name tiny_debug_logs.txt.

@gabevenberg
Copy link
Author

tiny_debug_logs.txt
Here you go. Did some experimentation and it only appears to happen when tls is turned on.

@osa1
Copy link
Owner

osa1 commented Nov 13, 2024

Port 6667 should be for non-TLS connections, for TLS the port should be 6697.

Which port are you using in irssi and are you enabling TLS? I suspect irssi automatically enables/disables TLS based on the port you use. I just quickly tried this, it looks like this server does not support TLS, so you should use these settings:

    - addr: mbrserver.com
      port: 6667
      tls: false

If you want TLS you should use this:

    - addr: mbrserver.com
      port: 6697
      tls: true

But it looks like this server doesn't support TLS, so use the first one.

@osa1 osa1 closed this as completed Nov 13, 2024
@osa1 osa1 removed the bug label Nov 13, 2024
@osa1
Copy link
Owner

osa1 commented Nov 13, 2024

I remember other users getting confused about this before, we should probably generate a warning when the TLS mode and port don't match, or allow leaving the port part empty and use the default ones based on the TLS mode.

@osa1 osa1 reopened this Nov 13, 2024
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