Page 1 of 1

SSL: Not Connecting?

Posted: Tue Jul 20, 2004 3:50 am
by Grey
I've read the FAQ, I've searched the forums, and I've asked in #unreal-support, still no luck, so I'll pose my problem here, and pray to the forum gods for support:

I have a gentoo and slackware machine, that refuse to connect to each other when ssl is enabled, any known problems?

I've generated the certificates using the Config program, and both servers connect fine without SSL, when I try to connect with SSL, I enable listen::option::ssl on both, on the same port (7029), and enable link::option::ssl in both server configs, then, when I oper up on the machines and try "/connect othermachine.com" it says "*** Connecting to othermachine.com[othermachine.com].", and never goes past that, on either, I've tried as a leaf connecting to a hub, and a hub connecting to a leaf.

Any Idea's?

Posted: Tue Jul 20, 2004 4:45 am
by Syzop
Any Idea's?
Yeah, give yourself the snomask junk mode (/mode yournick +s +j) on both sides and then try to connect, then see if you get some junk msgs :p.
And another hint: double check with '/stats P' that the port is in fact SSL (or even better: try to connect with a ssl client [assuming the port isn't serversonly]).
*sleepzor*

Posted: Tue Jul 20, 2004 9:24 pm
by Grey
both servers work fine with SSL, I have 3 ports open, 6667, for normal IRC, 6697 for SSL IRC, and 7029 for Servers, the SSL IRC works fine all the time, but as soon as I change 7029 to SSL, it all goes wrong,
And I dont even get any error messages, it's very frustrating,

I'll try with +s+j, but I'm usually a global op when I start messing around with it all,

Posted: Sun Jul 25, 2004 1:50 am
by Plasma
Are you indicating to your IRC client that it is an SSL enabled port your trying to connect to?

/server irc.somenetwork.com +6697

Would connect to SSL port 6697 using mIRC (the + sign indicates its an SSL port)

Posted: Sun Jul 25, 2004 8:55 am
by w00t
I will add that netronet, (my net :P) has experienced a lot of problems with server->server SSL. We eventually had to turn it off on our main two hubs, since they refused to link-- when they had been linked just 2 seconds ago.... Riiight...

Client SSL works fine though.