SSL Problem.

M

Migdiradmin

Verified User
Joined
Jan 5, 2020
Messages
152
How can i resolve this?

Code: 
2020:01:29-16:31:34: Can't connect to ssl!
2020:01:29-16:31:34: -> A failure in the SSL library occurred, usually a protocol error.
2020:01:29-16:31:34: -> error:00000001:lib(0):func(0):reason(1)
2020:01:29-18:31:31: Can't connect to ssl!
2020:01:29-18:31:31: -> A failure in the SSL library occurred, usually a protocol error.
2020:01:29-18:31:31: -> error:00000001:lib(0):func(0):reason(1)
2020:01:30-08:30:30: Can't connect to ssl!
2020:01:30-08:30:30: -> A failure in the SSL library occurred, usually a protocol error.
2020:01:30-08:30:30: -> error:00000001:lib(0):func(0):reason(1)
2020:01:30-12:43:30: Can't connect to ssl!
2020:01:30-12:43:30: -> A failure in the SSL library occurred, usually a protocol error.
2020:01:30-12:43:30: -> error:00000001:lib(0):func(0):reason(1)
2020:01:30-14:26:15: Can't connect to ssl!
2020:01:30-14:26:15: -> A failure in the SSL library occurred, usually a protocol error.
2020:01:30-14:26:15: -> error:00000001:lib(0):func(0):reason(1)
2020:01:30-17:08:53: Can't connect to ssl!
2020:01:30-17:08:53: -> A failure in the SSL library occurred, usually a protocol error.
2020:01:30-17:08:53: -> error:00000001:lib(0):func(0):reason(1)
2020:01:31-09:45:39: Can't connect to ssl!
2020:01:31-09:45:39: -> A failure in the SSL library occurred, usually a protocol error.
2020:01:31-09:45:39: -> error:00000001:lib(0):func(0):reason(1)
2020:01:31-10:02:50: Can't connect to ssl!
2020:01:31-10:02:50: -> A failure in the SSL library occurred, usually a protocol error.
2020:01:31-10:02:50: -> error:00000001:lib(0):func(0):reason(1)
2020:01:31-10:10:13: handshake_timeout(12) is larger than timeout(10). Lowering handshake_timeout to match timeout.
2020:01:31-10:10:13: request_timeout(20) is larger than timeout(10). Lowering request_timeout to match timeout.
2020:01:31-10:10:14: handshake_timeout(12) is larger than timeout(10). Lowering handshake_timeout to match timeout.
2020:01:31-10:10:14: request_timeout(20) is larger than timeout(10). Lowering request_timeout to match timeout.
2020:01:31-10:10:15: handshake_timeout(12) is larger than timeout(10). Lowering handshake_timeout to match timeout.
2020:01:31-10:10:15: request_timeout(20) is larger than timeout(10). Lowering request_timeout to match timeout.
2020:01:31-10:10:25: handshake_timeout(12) is larger than timeout(10). Lowering handshake_timeout to match timeout.
202:01:31-10:10:25: request_timeout(20) is larger than timeout(10). Lowering request_timeout to match timeout.
2020:01:31-10:13:27: handshake_timeout(12) is larger than timeout(10). Lowering handshake_timeout to match timeout.
2020:01:31-10:13:27: request_timeout(20) is larger than timeout(10). Lowering request_timeout to match timeout.
 
What's the actual problem? :) Last lines are just the warnings, I think you've lowered timeout in directadmin.conf, to get it back to 60:
Code: 
/usr/local/directadmin/directadmin set timeout 60
service directadmin restart
 
You are talkming about this in the panel?:
directadmin.com/admin/settings/server

Timeout (seconds) 60
Session Timeout (minutes) 60

Its by default 60.
 
What's the output of:
Code: 
/usr/local/directadmin/directadmin c | grep ^timeout
+ still waiting for the answer on what the actual problem is :)
 
Code: 
[root@server ~]# /usr/local/directadmin/directadmin c | grep ^timeout
timeout=60
[root@server ~]#
 
Okay, may you let us know the actual problem? As I'm still not sure what problem you are experiencing.
 
I dont have a problem but i have to ignore the error in var/log/directadmin/error.log ?


Code: 
2020:01:31-11:21:19: handshake_timeout(12) is larger than timeout(10). Lowering handshake_timeout to match timeout.
2020:01:31-11:21:19: request_timeout(20) is larger than timeout(10). Lowering request_timeout to match timeout.
2020:01:31-12:47:02: Can't connect to ssl!
2020:01:31-12:47:02: ->syscall
2020:01:31-12:47:02: Can't connect to ssl!
2020:01:31-12:47:02: ->syscall
 
The default "timeout" is 60.. you can lower it if you want, I wouldn't want to linger below 20s.. but it's up to you.
If you do lower the global timeout setting, then there are other per-step timeouts, eg:
Code: 
handshake_timeout=12
request_timeout=20
so just make sure those are below whatever your "timeout" is set to, and that will prevent those warnings.

As for "Can't connect to ssl!", this can happen if a client connect to http on the https:2222 port. DA does catch this and will redirect to https.
However, DA is only assuming that's what's happening, and the redirect is a guess. There could actually be some ssl error, in which case we'd want to know that, hence the log. If you cross reference your 2020-Jan-31.log, for the 12:47:02 timestamp, you might catch the IP that's doing it... thus be able to let them know to try an https URL instead. I could add a da.conf option, if there is any demand for it, to simply stop logging the SSL errors, assuming it's the http issue.
 
You must log in or register to reply here.
Back
Top