roNn23
October 6, 2023, 8:53pm
6
@sese Thank you! Thank you so much for your post. The problem has not just been there for a few days, but for about 2 weeks. I first thought it was because of the bad connection on vacation, but now here at home too. And I tried so many things and researched, nothing helped. At some point I found out it was a problem in the client and uploaded everything via web. I already wanted to switch to Dropbox. Really annoying. I didn’t thought about a downgrade. Now it finally works again.
Who also wants to downgrade - here are the old versions (remove the old Nextcloud.app first):
https://download.nextcloud.com/desktop/releases/Mac/Installer/
And who is eager to learn more about the bug:
https://github.com/nextcloud/desktop/pull/4826
opened 06:40AM - 23 Feb 23 UTC
0. Needs triage
### ⚠️ Before submitting, please verify the following: ⚠️
- [X] This is a **bug… **, not a question or a configuration issue.
- [X] This issue is **not** already reported on Github (I've searched it).
- [X] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions.
- [X] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/)
### Bug description
Note: This is not the same as #4278, although the two could be related
For whatever reason, some files fail to upload due to "connection closed" error. Those files then persistently throw that error on subsequent syncs.
The only workaround I've found so far is to alter the file name, usually one character at a time, until the file eventually uploads. If I don't do that, the file will just endlessly sync fail with "connection closed" errors.
As an example, one of dozens of files I have that are currently 'connection closed' bugged is `chatham-standup-2019-sep_48734822492_o.jpg`. If I rename that to `chatham-standup-2019-sep_48734822492_` (removed last char, but any change to the filename would suffice) then nc does at least try and sync it properly thinking it's a new file. However, single name change doesn't always fix the problem - sometimes I have to do several tweaks to filename to get nc to actually upload something.
### Steps to reproduce
IDK what causes triggers a file to encounter "connection closed" error, but once it does that error is permanent for that file and it will keep throwing same error every sync attempt - even though other files are uploading just fine.
It seems to occur mainly for media files (jpg, mp4, etc) - of all sizes. Larger files (eg. over 60MB) seem to encounter it more often than smaller ones, but I've had it occur on files as small as 7MB (that I've seen so far, that isn't necessarily a hard size limit).
### Expected behavior
Sync, the single most important component of nextcloud, should actually.... sync.
I suspect the lack of resume is part of the problem - having to restart a failed upload from scratch is entirely ludicrous in 2023. There is maybe also problem on serverside if it's for some reason thinking the original upload attempt is still in progress or something?
### Which files are affected by this bug
Completely random as far as I can tell
### Operating system
Windows
### Which version of the operating system you are running.
windows-10.0.19045
### Package
Other
### Nextcloud Server version
Latest stable (admin updated it few days ago)
### Nextcloud Desktop Client version
Version 3.7.3 (Windows)
### Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
### Are you using the Nextcloud Server Encryption module?
Encryption is Enabled
### Are you using an external user-backend?
- [X] Default internal user-backend
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other
### Nextcloud Server logs
```shell
I don't have access to server. Even if I did, given what I've seen of the client logs, I doubt I would be able to upload due to infestation of PII.
```
### Additional info
I'd really love to upload logs, btw, but there's just too much PII in them.
Have you ever had death threats and gangs of psychos trying to murder you just because of who you are (for real, I'm not embellishing)? I suspect not, because if you had you'd know the importance of not asking users to upload PII infested log files.
I too am getting “connection closed” errors for 2 specific files (10.5 MB and 31.8 MB) on Ubuntu 23.04 Lunar. Rest of the files (including a 281 MB .tgz file) syncs just fine.
Nextcloud client version is 3.10.50. I’m syncing these files with nch.pl.
QNetworkReply :: RemoteHostClosedError "Connection closed" QVariant (Invalid)
The solution mentioned by @TimLisemer and as described in this GitHub issue, is not working for me.
https://github.com/nextcloud/desktop/issues/4278#issuecomment-109958…