So I had the normal irssi config stuff all defined and all setup from my non-bouncer days. So I figured, with the bouncer, it shouldn’t be hard to get changed over etc..

Here is what I had pre-bouncer:

servers= { { address = “server.com”; chatnet = “derp”; port = “1820”; use_ssl = “yes”; ssl_verify = “no”; autoconnect = “Yes”; }, ); chatnets = { derp = { type = “IRC”; nick = “username”; };

After much raging, I finally figured out how to configure this to use my znc account on my bouncer (which has ssl enabled and port 1234, it also supports multiple networks which are defined after your username):

servers = ( { ## My bouncer!!! address = “znc.server.com”; password = “username/networkname:password”; chatnet = “derp”; port = “1234”; use_ssl = “yes”; ssl_verify = “no”; autoconnect = “Yes”; }, ); chatnets = { derp = {type = “IRC”;}; };

EDIT: Lets say you do have another network setup with your znc bouncer. Here’s how that would look in your irssi config if you wanted to connect to both:

servers = ( { ## My bouncer!!! address = “znc.server.com”; password = “username/networkname:password”; chatnet = “derp”; port = “1234”; use_ssl = “yes”; ssl_verify = “no”; autoconnect = “Yes”; }, { ## My bouncer connection for second network!!!! address = “znc.server.com”; password = “username/secondnetworkname:password”; chatnet = “anotherone”; port = “1234”; use_ssl = “yes”; ssl_verify = “no”; autoconnect = “Yes”; }, ); chatnets = { derp = {type = “IRC”;}; anotherone = {type = “IRC”;}; };

NOTE: If you have a server block but you don’t want to join that server, instead of commenting out the entire block, just change autoconnect to “no”.

and you will NOT be joined to that server. Pretty nifty if you have a ton of servers in your config but don’t want to join all of them upon irssi start.

Mario Loria is a builder of diverse infrastructure with modern workloads on both bare-metal and cloud platforms. He's traversed roles in system administration, network engineering, and DevOps. You can learn more about him here.