2017-03-26T09:52:13+0200] <Dominus> hi, what am I doing wrong in regard to connecting to Freenode? *status is always showing me a lot of "If you trust this certificate, do /znc AddTrustedServerFingerprint ..." and eventually I'm not connecting anymore unless I add some of those
[2017-03-26T09:52:56+0200] <MetaNova> you aren't using 'chat.freenode.net' I bet
[2017-03-26T09:53:28+0200] <MetaNova> what address did you specify?
[2017-03-26T09:57:44+0200] <Dominus> chat.freenode.net +6697
[2017-03-26T09:58:05+0200] <Dominus> should I leave the +6697 out?
[2017-03-26T09:58:15+0200] <MetaNova> no, you need the +6697
[2017-03-26T09:58:38+0200] <MetaNova> which exact server did you get that message from?
[2017-03-26T10:01:55+0200] <Dominus> rajaniemi.freenode.net, weber.freenode.net, card. , karatkievich, and and and...
[2017-03-26T10:02:45+0200] <MetaNova> yes, that domain resolves to 18 IP addresses
[2017-03-26T10:02:48+0200] • Dominus: is still on znc 1.6.3 if that is relevant
[2017-03-26T10:02:57+0200] <MetaNova> I am asking which one you connected to which generated the invalid cert message
[2017-03-26T10:03:20+0200] <MetaNova> so that I might test it and see, for myself, that it is in fact invalid
[2017-03-26T10:03:43+0200] <Dominus> those generated that
[2017-03-26T10:04:15+0200] <Dominus> at least those genearated the "if you trust this..."
[2017-03-26T10:04:37+0200] <MetaNova> uhm
[2017-03-26T10:05:35+0200] <MetaNova> no, it doesn't
[2017-03-26T10:06:07+0200] <metanova_> just generated a fresh config, added chat.freenode.net +6697, connected immediately and without any cert errors
[2017-03-26T10:06:30+0200] <metanova_> so, no, 'those' servers do not all generate that error
[2017-03-26T10:07:25+0200] <Dominus> I'm just looking at *status and that is what is written there
[2017-03-26T10:07:47+0200] <metanova_> I don't believe you, as I just proved that at least one of those servers does not generate that error.
[2017-03-26T10:08:01+0200] <metanova_> I'm presently connected to niven.freenode.net
[2017-03-26T10:08:08+0200] <metanova_> try specifying that server
[2017-03-26T10:09:55+0200] <Dominus> apparently I connected eventually to some server, but that is what I see in my status. I've sent you a dropbox link with the latest one
[2017-03-26T10:11:03+0200] <MrC> Not Dominus's fault if a server is poorly configured.  If LE certs are used, every server should be specified as a SAN as well as every alternative RR..  nothing he can do about that.  Or alternatively, different certs on each server that includes irc.*, chat.*, servername.*, and every RR..
[2017-03-26T10:12:50+0200] <metanova_> there is something wrong with your setup
[2017-03-26T10:13:01+0200] <metanova_> I just connected to the specific server which generated your error
[2017-03-26T10:13:04+0200] <metanova_> no issue.,
[2017-03-26T10:14:14+0200] <MrC> Suppose ca-certificates (Debian/Ubuntu) or the equivalent package could be missing..  "dpkg -l | grep ca-certificates"
[2017-03-26T10:14:18+0200] <Dominus> yeah, my initial question was "what am I doing wrong" as I thought if there were a general problem I'd have seen that on the net by now
[2017-03-26T10:14:54+0200] <Dominus> my znc runs on an OS X mac mini
[2017-03-26T10:14:59+0200] <MetaNova> the simple answer is, you're not doing anything wrong from a user standpoint
[2017-03-26T10:15:21+0200] <MetaNova> the extended answer is, there is something about your system which is preventing normal operation
[2017-03-26T10:15:39+0200] <MetaNova> and I unfortunately do not know where to start with that
[2017-03-26T10:16:04+0200] <MetaNova> you may want to consider trying the latest stable
[2017-03-26T10:16:14+0200] <Dominus> ok, thanks that makes sense (user vs system)
[2017-03-26T10:16:31+0200] <metanova_> o/
[2017-03-26T10:17:22+0200] <Dominus> will do the upgrade then (as soon as my kids let me)
[2017-03-26T10:20:20+0200] <Dominus> thanks for the help
[2017-03-26T10:23:46+0200] <MetaNova> Dominus: best of luck
[2017-03-26T10:23:58+0200] <Dominus> thanks
[2017-03-26T10:24:52+0200] <MetaNova> and also, be sure to try the command MrC suggested
[2017-03-26T10:25:13+0200] <MetaNova> it could very well be the local cert package is missing/damaged
[2017-03-26T10:25:39+0200] <Dominus> dpkg is not a standard OS X command, but I'll see if there is some equivalanet
[2017-03-26T10:25:52+0200] <MetaNova> installing/reinstalling the ca-certificates package (or whatever it may be named for a Mac) could very well fix the problem
[2017-03-26T10:25:56+0200] <MetaNova> yes
[2017-03-26T10:26:09+0200] <MetaNova> in fact, that is the more likely fix
[2017-03-26T10:26:15+0200] <MetaNova> to be honest