DA error log

[donkeyKICK]

I get the following error in the DA error log every time I log in (admin level). But I don't seem be having any problems:

2007:08:20-09:25:43: Can't connect to ssl!
2007:08:20-09:25:43: ->error ssl

Should / can I do anything about this?

 

[donkeyKICK]

Anyone? I'm still getting this...

 

[smtalk]

Please post an output of:

/usr/local/directadmin/directadmin c | grep ssl

 

[donkeyKICK]

Sure!


[root@server ~]# /usr/local/directadmin/directadmin c | grep ssl
ssl_port=0
ssl=1
ssl_redirect_host=(null)
apachecert=/etc/httpd/conf/ssl.crt/server.crt
apachekey=/etc/httpd/conf/ssl.key/server.key
[root@server ~]#


Thanks!

 

[Paulius]

My error log is full of the exact same errors and my directadmin file contains the exact same content as donkeyKICK.

Any ideas on what this might be and how to fix it?

 

[donkeyKICK]

Anyone? Still not resolved.

 

[nobaloney]

I'm getting the same error. Perhaps some kind of bug in the error reporting system?

Jeff

 

[DirectAdmin Support]

Hello,

Those errors are normal.

That happens when the "SSL_accept()" function returns a non-zero result.
The purpose of this function is to wait for the client to say "hi hello" in the ssl language.

If a user connect to https DA via http, then he won't be speaking ssl, thus the handshake fails and we get that error.

The "-> error ssl" is just the "errno" of the function failure (SSL_ERROR_SSL for anyone interested)... and after this happens, this is where DA sends the Location header redirect to https via plaintext, as a best guess as to what's going on.

Anyway, bottom line, it's Users connecting in plaintext to an SSL connection.

I could hide the errors.. or use the actual SSL_get_error() function instead of printing "-> error ssl".. doesn't matter to me

John