But we're not using SSL at all anywhere in Groupwise other than fronting the web frontend to Webaccess and Mobility, it's disabled on every page.
Everything installed on a single fully patched SLES11SP4, OES2015SP1 server
All groupwise components @ 14.2.3-129832
Everything was working fine until 10:54 this morning, no changes have been made, configuration files have not changed. Then we start getting the below errors on various logins, after a restart the first login sometime works and doesn't try to use https, but subsequent logins do.
12:56:44, <SOAP>, -, INFO, USER, Login
12:56:44, <SOAP>, -, INFO, USER, poaList: poa 0=https://IP:7191/soap
12:56:44, <SOAP>, -, INFO, USER, Exception invoking negotiateLoginRequest: HTTP transport error: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
12:56:44, <SOAP>, -, INFO, USER, Unable to connect to the POA @ https://IP:7191/soap
12:56:44, <SOAP>, -, INFO, USER, Unrecognized SSL message, plaintext connection?
Where on earth is it picking up that it needs to use https from? I can't find anything in any configuration file saying to use it. The only mention of SSL in webacc.cfg is about KeyShieldSSO.
If I try and wget the soap address over https it responds with exactly what I expect:
--2019-03-01 13:34:50-- https://IP:7191/soap
Connecting to IP:7191... connected.
OpenSSL: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
Unable to establish SSL connection.
So why has it suddenly decided to start trying to use https?
I've checked the server certs as per the other post, and they're all fine and valid (self signed and we don't use them anyway).
Completely stumped as to why it would suddenly start trying to use ssl, have no idea how it detects to use it or not.