Show better when we'll try to reconnect and when we did last time

[jedwards1211]

Expected behaviour

If the client experiences any of the following errors, I would expect it to retry after awhile:

1. No connection to site
2. Failure to send file (e.g. because max client payload size wasn't set high enough on server)
3. Intermittent connection failures
4. Permissions issues etc.

There's no indication if and when the client will retry; it's a black box. It would be most helpful if:

• the client would show a "Retrying in X minutes..." countdown in the status
• the client would provide a manual retry button

Actual behaviour

I may not remember, I don't think I've ever seen the client retry anything. Even making it log out and log back in does nothing -- it goes on thinking it can't connect, as if the error has been cached. Only removing the account in the client and adding it back from scratch fixes the issue.

Server configuration

Operating system: Ubuntu 14.04

Web server: official owncloud:9 docker container behind nginx-proxy container

Database: official mariadb docker container

PHP version: whatever's in the owncloud:9 docker container

ownCloud version: 9.0.4 (stable)

Storage backend: what is the difference between this and the database?

Client configuration

Client version: 2.2.2

Operating system: OSX 10.11.6

OS language: English

Installation path of client: default

Logs

https://gist.github.com/jedwards1211/0fae5e2b649df82a0fdded94ae27121a

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36513988-os-x-2-2-2-show-better-when-we-ll-try-to-reconnect-and-when-we-did-last-time?utm_campaign=plugin&utm_content=tracker%2F216457&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F216457&utm_medium=issues&utm_source=github).

[guruz]

@jedwards1211 wrote somewhere else

I'm seeing this in general on OSX -- if it says 'no connection to blah.com', and I make it log out and log back in, it still says 'no connection to blah.com'. If the network goes down the client seems to be stuck thinking it's disconnected. Even if some files fail to transfer -- there's no indication if or when the client is ever going to retry anything, and making it log out and log back in doesn't seem to change anything. It's as if the client has cached the failure message and given up.

The only workaround is to completely remove the account from the client and add it back again, which is pretty inconvenient.

[guruz]

I tried reproducing this by unplugging my USB network adapter and waiting until it shows "No connection to [...]". Then I replug it a bit later, after a while it reconnects. So all fine for me with 2.2.3beta1.

We'd need a relevant log file from you to be able to dig into this. The client log you linked from above does not contain anything about connection errors.