Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSL handshake failure fatal alert #6496

Closed
cyberduck opened this issue Jan 22, 2012 · 4 comments
Closed

SSL handshake failure fatal alert #6496

cyberduck opened this issue Jan 22, 2012 · 4 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jan 22, 2012

6af9fac created the issue

Hi there,

I can successfully log into my site with FTP. However, it offers the ability (via your dialog) to use FTP-SSL. I used to select 'Change' and it worked successfully.

Recently, my website was relocated (new server, new IP address) and I can no longer use FTP-SSL. When I try to log in, it won't connect but I also don't get an error in the GUI.

From the Log Drawer I see:

220 ProFTPD 1.3.3g Server (Main FTP Server) [71.18.87.92]
AUTH TLS
234 AUTH TLS successful

From the Console:

Jan 22 11:24:18 twentyseven [0x0-0x35b35b].ch.sudo.cyberduck[14512]: 2012-01-22 11:24:18,047 [background-29] ERROR ch.cyberduck.core.Session - SSL Handshake failed: Received fatal alert: handshake_failure

I feel like there's a certificate that is saved somewhere which is causing a problem. Can you direct me to the problem?
Thanks a lot.
David

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 23, 2012

@dkocher commented

This is a failure in the SSL handshake protocol to secure the connection. Can you let me know the address of the server to debug the issue.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 23, 2012

6af9fac commented

Replying to [comment:3 dkocher]:

This is a failure in the SSL handshake protocol to secure the connection. Can you let me know the address of the server to debug the issue.

The server is 'jarsky.com'. If there's anything else you need, just let me know. Thanks!

-David

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 23, 2012

6af9fac commented

I figured it out. If I use the servername 'web1314.ixwebhosting.com', it works properly. Thanks for looking into this.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 23, 2012

@dkocher commented

Debugging the SSL exchange it shows that we are trying the same negotiation connecting either to ftps://jarsky.com to or web1314.ixwebhosting.com . For jarsky.com we receive fatal TLSv1 ALERT.

Allow unsafe renegotiation: false
Allow legacy hello messages: true
Is initial handshake: true
Is secure renegotiation: false
Allow unsafe renegotiation: false
Allow legacy hello messages: true
Is initial handshake: true
Is secure renegotiation: false
%% No cached client session
*** ClientHello, TLSv1
RandomCookie:  GMT: 1327277494 bytes = { 204, 169, 66, 141, 88, 2, 122, 224, 177, 72, 10, 235, 150, 135, 109, 217, 203, 77, 129, 44, 200, 232, 197, 73, 112, 128, 236, 164 }
Session ID:  {}
Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV]
Compression Methods:  { 0 }
***
background-3, WRITE: TLSv1 Handshake, length = 81
background-3, READ: TLSv1 Alert, length = 2
background-3, RECV TLSv1 ALERT:  fatal, handshake_failure

I assume this is a server configuration issue.

Loading

@cyberduck cyberduck closed this Jan 23, 2012
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants