If you have an K-Line on a network, like freenode for example and try to connect, znc will throw some SSL error, instead of showing the K-Line reason, like a normal IRC client.
And some lovely output in the IRC client. <*status> Disconnected from IRC (error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol). Reconnecting... <*status> Disconnected from IRC. Reconnecting... <*status> Disconnected from IRC (error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol). Reconnecting... <*status> Disconnected from IRC. Reconnecting... <*status> Disconnected from IRC (Connection reset by peer). Reconnecting... <*status> Disconnected from IRC. Reconnecting...
ZNC should at least show the K-Line message while using SSL, to prevent confusion.
23:02:36 !irc.foobar.com *** Looking up your hostname... 23:02:37 !irc.foobar.com *** Checking Ident 23:02:37 !irc.foobar.com *** Couldn't look up your hostname 23:02:46 !irc.foobar.com *** No Ident response 23:02:46 -!- You are banned from this server- Temporary K-line 1440 min. - Joining #meh (2015/1/27 22.41) 23:02:46 -!- ERROR Closing Link: 99.99.99.99 (*** Banned ) 23:02:46 -!- Irssi: Connection lost to 999.999.999.999
Is there a fix for this yet? Because I cannot connect to #freenode now with SSL. It keeps disconnecting me, but without SSL it works fine... Any suggestion? :) I am on ZNC 1.4
Is there a fix for this yet? Because I cannot connect to #freenode now with SSL. It keeps disconnecting me, but without SSL it works fine... Any suggestion? :) I am on ZNC 1.4
<!-- github-comment-id:72701987 -->
No there isn't. If you can connect without SSL, this is separate issue. What is the error message you get and are you sure that you have + in front of the SSL port number?
No there isn't. If you can connect without SSL, this is separate issue. What is the error message you get and are you sure that you have `+` in front of the SSL port number?
<!-- github-comment-id:72702314 -->
I can connect with SSL but when I do that i get the exact same error as described above.. so I switched to NON-SSL. ;) That works fine.
And yes of course I had a + infront of the port number ;)
I can connect with SSL but when I do that i get the exact same error as described above.. so I switched to NON-SSL. ;) That works fine.
And yes of course I had a + infront of the port number ;)
<!-- github-comment-id:72719708 -->
You can check to see if the IP is banned by loading up 2 SSH terminals (I'm presuming you're using a Debian based Linux system here) and running 1 of the commands in each.
socat tcp-l:12345,reuseaddr,fork 'tcp:[IPv4/IPv6 of the network you're connecting too]:6697,bind=[Your system's IPv4/IPv6 address]'
2 ) gnutls-cli -p 12345 --insecure -V 127.0.0.1
Please note: Don't remove the ['s and ]'s on the first command.
You can check to see if the IP is banned by loading up 2 SSH terminals (I'm presuming you're using a Debian based Linux system here) and running 1 of the commands in each.
1) socat tcp-l:12345,reuseaddr,fork 'tcp:[IPv4/IPv6 of the network you're connecting too]:6697,bind=[Your system's IPv4/IPv6 address]'
2 ) gnutls-cli -p 12345 --insecure -V 127.0.0.1
Please note: Don't remove the ['s and ]'s on the first command.
<!-- github-comment-id:72724547 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
If you have an K-Line on a network, like freenode for example and try to connect, znc will throw some SSL error, instead of showing the K-Line reason, like a normal IRC client.
And some lovely output in the IRC client.
<*status> Disconnected from IRC (error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol). Reconnecting...<*status> Disconnected from IRC. Reconnecting...<*status> Disconnected from IRC (error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol). Reconnecting...<*status> Disconnected from IRC. Reconnecting...<*status> Disconnected from IRC (Connection reset by peer). Reconnecting...<*status> Disconnected from IRC. Reconnecting...ZNC should at least show the K-Line message while using SSL, to prevent confusion.
23:02:36 !irc.foobar.com *** Looking up your hostname...23:02:37 !irc.foobar.com *** Checking Ident23:02:37 !irc.foobar.com *** Couldn't look up your hostname23:02:46 !irc.foobar.com *** No Ident response23:02:46 -!- You are banned from this server- Temporary K-line 1440 min. - Joining #meh (2015/1/27 22.41)23:02:46 -!- ERROR Closing Link: 99.99.99.99 (*** Banned )23:02:46 -!- Irssi: Connection lost to 999.999.999.999Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
This is similar to #320 that ZNC needs to detect whether peer talks SSL or not.
Is there a fix for this yet? Because I cannot connect to #freenode now with SSL. It keeps disconnecting me, but without SSL it works fine... Any suggestion? :) I am on ZNC 1.4
No there isn't. If you can connect without SSL, this is separate issue. What is the error message you get and are you sure that you have
+in front of the SSL port number?I can connect with SSL but when I do that i get the exact same error as described above.. so I switched to NON-SSL. ;) That works fine.
And yes of course I had a + infront of the port number ;)
You can check to see if the IP is banned by loading up 2 SSH terminals (I'm presuming you're using a Debian based Linux system here) and running 1 of the commands in each.
2 ) gnutls-cli -p 12345 --insecure -V 127.0.0.1
Please note: Don't remove the ['s and ]'s on the first command.