[GH-ISSUE #700] Backups failing due to SSL handshake timed out #591

New issue

Open

opened 2026-02-26 01:31:03 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 01:31:03 +03:00

Owner

Originally created by @shomanjk on GitHub (Dec 4, 2016).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/700

I have been getting intermittent errors that backups failed, usually when transitioning between 4G and WiFi. However lately, it will not complete a backup at all (or much less often). I am seeing the following in the logs. It has been a few days since the last successful backup.

12-03 18:37 General error: Unable to connect (exception: com.fsck.k9.mail.MessagingException: Unable to connect, underlying=java.net.SocketTimeoutException: SSL handshake timed out)

Any resolution suggestions?

I'm running SMS Backup+ 1.5.10 on Android 6.0.1 on Galaxy S6 Active

Originally created by @shomanjk on GitHub (Dec 4, 2016). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/700 I have been getting intermittent errors that backups failed, usually when transitioning between 4G and WiFi. However lately, it will not complete a backup at all (or much less often). I am seeing the following in the logs. It has been a few days since the last successful backup. `12-03 18:37 General error: Unable to connect (exception: com.fsck.k9.mail.MessagingException: Unable to connect, underlying=java.net.SocketTimeoutException: SSL handshake timed out)` Any resolution suggestions? I'm running SMS Backup+ 1.5.10 on Android 6.0.1 on Galaxy S6 Active

kerem added the

backup

v1.5.10

labels

2026-02-26 01:31:03 +03:00

kerem commented

2026-02-26 01:31:03 +03:00

Author

Owner

@shomanjk commented on GitHub (Dec 4, 2016):

#626 Seems to be a very similar issue to the above, just a different timeout error though.

I turned on Extra debug information and then ran a manual backup, here is the log...

12-04 04:43 Starting backup (MANUAL) 12-04 04:43 Backing up (4 SMS, 0 MMS, 5 call log) 12-04 04:43 Using config: BackupConfig{imap=BackupImapStore{uri=imap+ssl+://XOAUTH2:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@imap.gmail.com:993}, skip=false, currentTry=0, maxItemsPerSync=-1, groupToBackup=ContactGroup{_id=-1, type=EVERYBODY}, backupType=MANUAL, debug=true, typesToBackup=[SMS, MMS, CALLLOG]} 12-04 04:44 General error: Unable to connect (exception: com.fsck.k9.mail.MessagingException: Unable to connect, underlying=java.net.SocketTimeoutException: SSL handshake timed out) 12-04 04:44 BackupState{currentSyncedItems=0, itemsToSync=0, backupType=MANUAL, exception=com.fsck.k9.mail.MessagingException: Unable to connect, state =ERROR} 12-04 04:44 Backup finished

@shomanjk commented on GitHub (Dec 4, 2016): #626 Seems to be a very similar issue to the above, just a different timeout error though. I turned on Extra debug information and then ran a manual backup, here is the log... `12-04 04:43 Starting backup (MANUAL) 12-04 04:43 Backing up (4 SMS, 0 MMS, 5 call log) 12-04 04:43 Using config: BackupConfig{imap=BackupImapStore{uri=imap+ssl+://XOAUTH2:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@imap.gmail.com:993}, skip=false, currentTry=0, maxItemsPerSync=-1, groupToBackup=ContactGroup{_id=-1, type=EVERYBODY}, backupType=MANUAL, debug=true, typesToBackup=[SMS, MMS, CALLLOG]} 12-04 04:44 General error: Unable to connect (exception: com.fsck.k9.mail.MessagingException: Unable to connect, underlying=java.net.SocketTimeoutException: SSL handshake timed out) 12-04 04:44 BackupState{currentSyncedItems=0, itemsToSync=0, backupType=MANUAL, exception=com.fsck.k9.mail.MessagingException: Unable to connect, state =ERROR} 12-04 04:44 Backup finished`