starred/sms-backup-plus-jberkel

Fork 0

mirror of https://github.com/jberkel/sms-backup-plus.git synced 2026-04-25 17:05:59 +03:00

[GH-ISSUE #1008] Need to log more information about connection failures in the debug log #804

New issue

Open

opened 2026-02-26 01:31:56 +03:00 by kerem · 6 comments

kerem commented

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

Owner

Originally created by @dinojr on GitHub (Dec 29, 2019).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1008

Originally assigned to: @jberkel, @kurahaupo on GitHub.

Expected behaviour

Recover SMS stored by sms-backup-plus on a non-Gmail imap server in Android 7 (Samsung Galaxy 7)

Actual behaviour

sms-backup-plus in Android 10 (pixel 3a) issues a can't connect error

Steps to reproduce the behaviour

Click the Restore button

Please specify the following:

Android version
Android 10
Phone model / brand
Google Pixel 3a
SMS Backup+ version installed
1.6.0-BETA2
Messaging app
Google Messages

Please find the log file attached.
sms_backup_plus.log

Originally created by @dinojr on GitHub (Dec 29, 2019). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1008 Originally assigned to: @jberkel, @kurahaupo on GitHub. ### Expected behaviour Recover SMS stored by sms-backup-plus on a non-Gmail imap server in Android 7 (Samsung Galaxy 7) ### Actual behaviour sms-backup-plus in Android 10 (pixel 3a) issues a can't connect error ### Steps to reproduce the behaviour Click the Restore button ### Please specify the following: * Android version Android 10 * Phone model / brand Google Pixel 3a * SMS Backup+ version installed 1.6.0-BETA2 * Messaging app Google Messages Please find the log file attached. [sms_backup_plus.log](https://github.com/jberkel/sms-backup-plus/files/4007956/sms_backup_plus.log)

kerem added the

helpful

v1.5.11

v1.6β

labels

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

kerem commented

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

Author

Owner

@nikkopt commented on GitHub (Dec 30, 2019):

Maybe it's related to #1006
I haven't tried the beta myself

@nikkopt commented on GitHub (Dec 30, 2019): Maybe it's related to #1006 I haven't tried the beta myself

kerem commented

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

Author

Owner

@dinojr commented on GitHub (Jan 3, 2020):

I don't thinks it's related

I have the same problem with the non-beta 1.5.11 version
the error message is different: I get "unable to connect"

Also, the slide button/switch labelled "Connect" is greyed out and I can't switch it on even though the account parameters are set in the "Advanced parameters" menu.

@dinojr commented on GitHub (Jan 3, 2020): I don't thinks it's related + I have the same problem with the non-beta 1.5.11 version + the error message is different: I get "unable to connect" Also, the slide button/switch labelled "Connect" is greyed out and I can't switch it on even though the account parameters are set in the "Advanced parameters" menu.

kerem commented

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

Author

Owner

@kurahaupo commented on GitHub (Jan 4, 2020):

@nikkopt this appears to be an Android permissions problem; have you granted all the requested permissions, or have some of them been withheld?

@jberkel patch #1009 would help by including the missing permission(s) in the log. Let me know if it's suitable or needs amendment (for example, would you prefer to set the error text in the constructor?)

@kurahaupo commented on GitHub (Jan 4, 2020): @nikkopt this appears to be an Android permissions problem; have you granted all the requested permissions, or have some of them been withheld? @jberkel patch #1009 would help by including the missing permission(s) in the log. Let me know if it's suitable or needs amendment (for example, would you prefer to set the error text in the constructor?)

kerem commented

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

Author

Owner

@edgewood commented on GitHub (Sep 16, 2020):

I had the same issue with 1.5.11, with the "Unable to connect" error and the grayed-out "Connect" switch.

Despite having "Sync log" and "Extra debug information" checked, I get no log entries from attempts to restore.

I was able to enable restoring by watching the IMAP server logs when I made a connection attempt, and saw it complained "imap-login: Maximum number of connections from user+IP exceeded (mail_max_userip_connections=10)". I noted that I had a bunch of stuck logins for the server, so stopped and restarted it.

Once I did that, I was able to restore (well, it's currently still in progress, but has done about 6000 items so I presume it will complete).

Note that I was only able to do this because I use a server under my control. Assuming the server responds to SMS Backup+ with a similar error message, having that in the log would have helped me find this much earlier.

@edgewood commented on GitHub (Sep 16, 2020): I had the same issue with 1.5.11, with the "Unable to connect" error and the grayed-out "Connect" switch. Despite having "Sync log" and "Extra debug information" checked, I get no log entries from attempts to restore. I was able to enable restoring by watching the IMAP server logs when I made a connection attempt, and saw it complained "imap-login: Maximum number of connections from user+IP exceeded (mail_max_userip_connections=10)". I noted that I had a bunch of stuck logins for the server, so stopped and restarted it. Once I did that, I was able to restore (well, it's currently still in progress, but has done about 6000 items so I presume it will complete). Note that I was only able to do this because I use a server under my control. Assuming the server responds to SMS Backup+ with a similar error message, having that in the log would have helped me find this much earlier.

kerem commented

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

Author

Owner

@dinojr commented on GitHub (Sep 17, 2020):

edgewood notifications@github.com writes:

I had the same issue with 1.5.11, with the "Unable to connect" error
and the grayed-out "Connect" switch.

Despite having "Sync log" and "Extra debug information" checked, I get
no log entries from attempts to restore.

I was able to enable restoring by watching the IMAP server logs when I
made a connection attempt, and saw it complained "imap-login: Maximum
number of connections from user+IP exceeded
(mail_max_userip_connections=10)". I noted that I had a bunch of
stuck logins for the server, so stopped and restarted it.

Once I did that, I was able to restore (well, it's currently still in
progress, but has done about 6000 items so I presume it will
complete).

Note that I was only able to do this because I use a server under my
control. Assuming the server responds to SMS Backup+ with a similar
error message, having that in the log would have helped me find this
much earlier.

Thanks for the input. In my case, the problem doesn't occur anymore. I
can now backup up as I used to. I don't really know what changed, except
that between the last failed attempt (a few months ago) and the first
successfull one (a few weeks ago) I broke my Pixel 3a broke and bought a
new identical one...

Julien Cubizolles

@dinojr commented on GitHub (Sep 17, 2020): edgewood <notifications@github.com> writes: > I had the same issue with 1.5.11, with the "Unable to connect" error > and the grayed-out "Connect" switch. > > Despite having "Sync log" and "Extra debug information" checked, I get > no log entries from attempts to restore. > > I was able to enable restoring by watching the IMAP server logs when I > made a connection attempt, and saw it complained "imap-login: Maximum > number of connections from user+IP exceeded > (mail_max_userip_connections=10)". I noted that I had a bunch of > stuck logins for the server, so stopped and restarted it. > > Once I did that, I was able to restore (well, it's currently still in > progress, but has done about 6000 items so I presume it will > complete). > > Note that I was only able to do this because I use a server under my > control. Assuming the server responds to SMS Backup+ with a similar > error message, having that in the log would have helped me find this > much earlier. Thanks for the input. In my case, the problem doesn't occur anymore. I can now backup up as I used to. I don't really know what changed, except that between the last failed attempt (a few months ago) and the first successfull one (a few weeks ago) I broke my Pixel 3a broke and bought a new identical one... -- Julien Cubizolles

kerem commented

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

Author

Owner

@kurahaupo commented on GitHub (Sep 27, 2020):

@edgewood thanks, that's a very useful observation.

I'll add "unstable network connection" to the list of things to check in this case, as that's the most likely reason for stacking up concurrent IMAP sessions.

@kurahaupo commented on GitHub (Sep 27, 2020): @edgewood thanks, that's a very useful observation. I'll add "unstable network connection" to the list of things to check in this case, as that's the most likely reason for stacking up concurrent IMAP sessions.