Subj : Re: letsyncrypt issue
To   : Dumas Walker
From : Digital Man
Date : Sun Feb 15 2026 02:57 pm

  Re: Re: letsyncrypt issue
  By: Dumas Walker to FUSION on Sun Feb 15 2026 10:21 am

 > >  DW> And, of course, the irc is broken, too:
 >
 > >  DW> Looking up irc.synchro.net
 > >                 ^^^^^^^^^^^^^^^
 > >  DW> * * Subject: /CN=endofthelinebbs.com
 > >                       ^^^^^^^^^^^^^^^^^^^
 > > this will never work because the hosts don't match
 >
 > I noticed that but that is what happend when I plugged irc.synchro.net into
 > hexchat in the server name field and told it to connect.  I did *not* put
 > *any* info in there for endofthelinebbs.com.

irc.synchro.net is a rotating hostname, it points to *all* of the IRC servers (and there's a lot of them). That can be seen using tools like nslookup, host, dig, etc.:

Name:    irc.synchro.net
Addresses:  2600:6c88:8c40:5b:f1d0:1:103:705
          2604:880:52:866:f1d0:1:124:5016
          2001:19f0:6000:94c9::68:234
          2001:19f0:6000:94c9::81:241
          71.95.196.34
          51.75.174.224
          158.220.122.223
          192.138.210.158
          45.32.81.241
          138.197.129.1
          108.242.55.251
          203.191.174.253
          59.167.142.49
          45.32.68.234

 > I can only assume that came from the host end as I only saw that response
 > the one time it connected.  The other few times, when it got other errors
 > or timed-out, that erroneous address didn't show up.

Simple turn off TLS in the IRC client and it'll use TCP port 6667 (didn't I already explani this?) and work. Or heck, just use the IRC option from the chat menu on your own BBS!
-- 
                                            digital man (rob)

Synchronet "Real Fact" #67:
SEXYZ is as a 32-bit replacement for [F]DSZ, CE-XYZ and other protocol drivers
Norco, CA WX: 59.8øF, 58.0% humidity, 6 mph WNW wind, 0.00 inches rain/24hrs

.