-
Notifications
You must be signed in to change notification settings - Fork 600
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
SASL+TLS leads to connection failure #39
Comments
Could you paste the crash ? I'm using TLS+SASL myself without any issues (on freenode) |
|
I've added verbose debugging of the IRC bridge connection when you enable debug. You can now debug SASL and compare it with and without TLS. It should be exactly the same though. The gateway now also when a bridge fails to startup. So no NPE anymore. |
hmm, the NPE disappeared, but no debug log is shown. I have no idea it's broken. |
You did run matterbridge with -debug? |
Sure. |
Could you paste your config? |
Wow, figured out now. It was the IRC port settings. No debug output there, though. |
As the title says, the connection fails and the bridge crashes with NPE.
TLS+NickServ is okay, SASL without TLS also works. Since it's TLS, no packet inspection can be easily done on my side.
Although this may be an upstream issue, since you are the writer of the SASL part I'm writing here.
The text was updated successfully, but these errors were encountered: