Sync error: “Server stopped accepting new streams before this stream was established”

[kmorber]

⚠️ Before submitting, please verify the following: ⚠️

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

Nextcloud client has connection losses.

Sync error: “Server stopped accepting new streams before this stream was established”](https://help.nextcloud.com/t/sync-error-server-stopped-accepting-new-streams-before-this-stream-was-established/59209)

Steps to reproduce

1. Right click on the file
2. Click on Share Options
3. The share dialog does not display the option to share by e-mail
   ...

Expected behavior

no connection losses

Which files are affected by this bug

all

Operating system

Windows

Which version of the operating system you are running.

Windows 11

Package

Official Windows MSI

Nextcloud Server version

30.0.0

Nextcloud Desktop Client version

3.14.0

Is this bug present after an update or on a fresh install?

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

No response

Additional info

log.zip

[thalunil]

With a fresh sync, i have the same issue with the version 3.14.0 on Windows.
Version 3.13.4 works as expected.

[PhilippSchlesinger]

@mgallien
Is this issue caused by #6986, always enabling http2?
There is an ancient bug #1503 (comment) on the same issue, at that time solved via a PR #1823 that disabled http2 due to Qt bugs.

[kmorber]

I have disabled http2, but same issues.

[mbentley]

I have disabled http2, but same issues.

Could you share your web server config? If you're having this issue but are not using http2, that would be very surprising from what I understand.

I also noticed that doing an initial sync triggered this for me yesterday on macOS using the 3.14.0 client. I previously had http2 turned on in nginx so I've had to disable it for nextcloud now to allow the sync to work. I re-installed the 3.12.7 macOS nextcloud client and as expected, it works fine whether I have http2 turned off or on. That version appears to be one of the last since #6986 was merged.

[nursoda]

I have enabled http2 (and not http3/quic) in NGINX. I see the issue on Windows 11 23H2v2 and Arch Linux with NC Desktop 3.14.0 on KDE/Plasma (Qt).

[vagner-dias]

I am having the very same issue. Fresh sync using 3.14 throws this error.
V 3.13.4 works smoothly

[EDIT] Repeatedly Forcing new synchronizations causes a crash in the desktop client.

[webneo82]

Same issue here since update the client to V. 3.14.0.

Windows 11 22631.4169
Nextcloud Server 29.0.7 with NGiNX and http/2 enabled. Disabling http/2 will also cause synchronization errors. However, "Server stopped accepting new streams before this stream was established will not appear", but "Connection timeout".

With Nextcloud Client V 3.13.4 all works fine.

[osiktech]

I ran into the same issue on macOS 14.7 with a fresh sync. I downgraded my client back to 3.13.4 and everything is back to normal.

One more finding (maybe related): My nextcloud server was continuesly deactivating my user account although I allowed my ip address through bruteforce settings.

[timirons]

Same issue here with a new install today, using Ionos server.

[mgallien]

we will revert the change and try to find another solution
we did this change because when http1.1 is broken and http2 is working, having to define an env variable is far from obvious as a fix

[charliehoward]

I'm also having this issue running NextCloudCMD on Ubuntu

[Stoony1]

same problem here

[albert-a]

Same problem with Nextcloud AIO 29.0.6 and Desktop client 3.14.0 (Mac)
Subjectively the 3.14.0 client is very very slow and always shows this error.
I removed Desktop client 3.14.0, and installed 3.13.4 and now everything works again, fast and smooth.

[prrar]

Same problem here. Clean macOS Sequoia 15.0 install, Nextclkoud AIO 29.0.6 and Desktop Client 3.14.0 Mac. I've followed @albert-a 's suggestion and downgraded to 3.14.4. So far, so good.

[DDQW]

For people who run an nginx server this can be fixed serverside:

raising the value of keepalive_requests should help with this. default value is 1000 i raised it to 99999 (a debug value you should adjust that to your needs) which seems to be enough for our usecase (no error reported since i made the adjustment) be aware that this increases nginxs ram usage and your system needs to be ready for this.

i also adjusted keepalive timeout in nginx to 600 (10 minutes) from 1 minute. Maybe something for the nginx default config

http {

    ##
    # Basic Settings
    ##

    sendfile on;
    tcp_nopush on;
    types_hash_max_size 2048;
    # server_tokens off;
    client_max_body_size 512G;
    # server_names_hash_bucket_size 64;
    # server_name_in_redirect off;
    keepalive_requests 99999;
    keepalive_timeout 600;
    include /etc/nginx/mime.types;
    default_type application/octet-stream;

So it appears that the client needs a limit to the connections it tries to create and/or not bug out when a connection is refused and just use the ones it got.

[eurovisionfanatic]

Same issues here, everything works fine on 3.13 but 3.14 won't sync. Disabling HTTP2 causes the Connection Timeout issue. Has anyone found any mitigations for this?

[charliehoward]

I unfortunately do not have access to the server side, as I pay for it to be hosted

[GarmischWg]

I am having the very same issue. Fresh sync using 3.14 throws this error. V 3.13.4 works smoothly

[EDIT] Repeatedly Forcing new synchronizations causes a crash in the desktop client.

encoutering the same issue, the solution provided did not solve the issue unfortunately

[Xenthys]

Same problem here, I almost blamed my hosting provider. Downgrading to 3.13.4 fixed my stream issue.

[Thomas6013]

I've the same issue with the same configuration

[GitTimeraider]

Started receiving notifications that large files could not be uploaded.. tried fixes, nothing helped. Downgraded the client from 3.14 to a lower version (in this case 3.13 to be sure) and that one works perfectly fine

Desktop client installed on Windows 11 home

[Belledonne0]

same error. One Fix is in way ?!

[charliehoward]

How can I downgrade the client on linux with no GUI? Seems apt only has the current version and 3.11

[jamesstanw]

Same as reported above

[osiktech]

How can I downgrade the client on linux with no GUI? Seems apt only has the current version and 3.11

@charliehoward you could use the appimage package from here https://github.com/nextcloud-releases/desktop/releases/tag/v3.13.3 depending on the distro you could also download an older version directly from a mirror and do an apt-pinning.

[charliehoward]

For people who run an nginx server this can be fixed serverside:
raising the value of keepalive_requests should help with this. default value is 1000 i raised it to 99999 (a debug value you should adjust that to your needs) which seems to be enough for our usecase (no error reported since i made the adjustment) be aware that this increases nginxs ram usage and your system needs to be ready for this.
i also adjusted keepalive timeout in nginx to 600 (10 minutes) from 1 minute. Maybe something for the nginx default config
http {

    ##
    # Basic Settings
    ##

    sendfile on;
    tcp_nopush on;
    types_hash_max_size 2048;
    # server_tokens off;
    client_max_body_size 512G;
    # server_names_hash_bucket_size 64;
    # server_name_in_redirect off;
    keepalive_requests 99999;
    keepalive_timeout 600;
    include /etc/nginx/mime.types;
    default_type application/octet-stream;

So it appears that the client needs a limit to the connections it tries to create and/or not bug out when a connection is refused and just use the ones it got.

Works for me, for a new installation I pass keepalive_requests from 100 to 1000 and keepalive_timeout from 15 to 60

Thanks - this was also mentioned above as a potential solution. However it was voted down. I'm not sure why?

Because it's not a fix that works for everyone, if you don't have access to the server then you can't do it

[paradonym]

Is there any way to remove the default auto-recognized update to 3.14 in the 3.13.4 client version?
I don't know if it auto-updates during usual PC reboots when the new version already shown in the settings screen. Despite having the option to check for updates disabled

[Belledonne0]

Is there any way to remove the default auto-recognized update to 3.14 in the 3.13.4 client version? I don't know if it auto-updates during usual PC reboots when the new version already shown in the settings screen. Despite having the option to check for updates disabled

On windows i can disable on this version 3.13.4.
so which os ?

[SavasTheodoropoulos]

I am having the same problem using Desktop Client 3.14.0 for Windows

[stefan2904]

rollback to the last release is not easily possible via apt, as
apparently, the 3.13 release is only uploaded for mantic

[charliehoward]

Do you know of a way to do it via apt?
Or of course, someone at NC could have used the past week to actually fix it

[osiktech]

for apt users, please have look here: https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-apt-get this might help you, with downgrading.

[charliehoward]

for apt users, please have look here: https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-apt-get this might help you, with downgrading.

I ran apt list -a nextcloud-desktop but I only get two options - nextcloud-desktop/noble,now 3.14.0-20240916.085658.d8fcb9273-1.0~noble1 amd64 [residual-config] nextcloud-desktop/noble 3.11.0-1.1build4 amd64 [residual-config]

Unless you can suggest a source with older versions? Specifically 3.13.x

[stefan2904]

for apt users, please have look here: https://askubuntu.com/questions/138284/how-to-downgrade-a-package-via-apt-get this might help you, with downgrading.

@osiktech This does not help if no package version is available to downgrade to. ;-)
See output of sudo apt-cache policy nextcloud-desktop

Unless you can suggest a source with older versions? Specifically 3.13.x

It seems the xtradeb PPA hat some versions available. E.g., for jammy, nextcloud-desktop 3.12 (from April 2024).

[charliehoward]

Yep that does work
sudo add-apt-repository ppa:xtradeb/apps
sudo apt update

Then you have to specify the version you want
sudo apt install nextcloud-desktop=3.13.4-1xtradeb1.2404.1

I also had to install libnextcloudsync0, doc and cmd
sudo apt install libnextcloudsync0=3.13.4-1xtradeb1.2404.1
sudo apt install nextcloud-desktop-doc=3.13.4-1xtradeb1.2404.1
sudo apt install nextcloud-desktop-cmd=3.13.4-1xtradeb1.2404.1

[charliehoward]

I wouldn't say it's completed, this is a workaround, it still needs fixing lol

[nursoda]

@xataz wrote:

Works for me, for a new installation
I pass keepalive_requests from 100 to 1000
and keepalive_timeout from 15 to 60

That's strange since the defaults are

keepalive_requests 1000;
keepalive_timeout 75s;

So, if you stuck to defaults, this should work. I use defaults, but it didn't wfm.

I tried the fixed AppImage, and it no longer yielded the OP error, yet some other strange behavior.

[nursoda]

I'm on arch and was struck by this issue using repo package nextcloud-client 3.14.0-1. So I temporarily downgraded all my machines to 3.13.4-1. After confirming that the fixed AppImage works for me (see above), I tried the current repo version 3.14.0-5. This also seems to work for me! Now I'm a bit baffled what the difference is. Probably a look on the arch package mantainer's change log gives ideas to devs here?

However, if it were a Linux/Qt library issue, this does not explain why I had the same issue on my Win11 machine.

[GerritLionMountain]

I have the same problem, but i'm using a Mac

[egge96]

Yes, I have the problem as well - also using a Mac - problem exists with MAC version of Nextcloud Client but also on Windows run in Parallels VM

[egge96]

Yes, I have the problem as well - also using a Mac - problem exists with MAC version of Nextcloud Client but also on Windows run in Parallels VM

My solution is currently a downgrade to 3.13.4

[GerritLionMountain]

Is it possible to use an older version of the desktop client in the hope that it will then work?

[egge96]

Is it possible to use an older version of the desktop client in the hope that it will then work?

Yes, that seems to be the only solution at the moment.

[GerritLionMountain]

Is it possible to use an older version of the desktop client in the hope that it will then work?

Yes, that seems to be the only solution at the moment.

okay, do you know where to get the earlier ones? I couldn't find anything on nextcloud itself from the earlier versions

[brunobeeee]

okay, do you know where to get the earlier ones? I couldn't find anything on nextcloud itself from the earlier versions

If you don't want to figure your package manager out on how to install the older version and stuff:
Here ist the directory with all Nextcloud builds online: https://download.nextcloud.com/desktop/releases/

I just downloaded the Mac installer from there and when I know that this bug is fixed I will uninstall it and use Homebrew to get the latest version as usual.
In theory I think you can do the same on other OSs.

[GerritLionMountain]

If you don't want to figure your package manager out on how to install the older version and stuff: Here ist the directory with all Nextcloud builds online: https://download.nextcloud.com/desktop/releases/

I just downloaded the Mac installer from there and when I know that this bug is fixed I will uninstall it and use Homebrew to get the latest version as usual. In theory I think you can do the same on other OSs.

okay i will try it also

[GerritLionMountain]

okay, do you know where to get the earlier ones? I couldn't find anything on nextcloud itself from the earlier versions

If you don't want to figure your package manager out on how to install the older version and stuff: Here ist the directory with all Nextcloud builds online: https://download.nextcloud.com/desktop/releases/

I just downloaded the Mac installer from there and when I know that this bug is fixed I will uninstall it and use Homebrew to get the latest version as usual. In theory I think you can do the same on other OSs.

Which version worked for you? I have now downloaded several and it still does not synchronize

[brunobeeee]

Which version worked for you? I have now downloaded several and it still does not synchronize

Sorry to hear that. Version 3.13.4 works just fine for me and it seems to work for many others in this thread.

[vagner-dias]

@mgallien – It seems that a fix for this issue has already been merged. It might be a good idea to make a "beta 3.14.1" release available so that the people in this thread can test it before the production release?

[Bluejanis]

@mgallien Could you please reopen this issue? It is still not working, using the latest version.

[Electrenator]

@xataz wrote:

Works for me, for a new installation
I pass keepalive_requests from 100 to 1000
and keepalive_timeout from 15 to 60

That's strange since the defaults are

keepalive_requests 1000;
keepalive_timeout 75s;

So, if you stuck to defaults, this should work. I use defaults, but it didn't wfm.

I tried the fixed AppImage, and it no longer yielded the OP error, yet some other strange behavior.

May be related to #7171. Got the errors shown there when I increased the timeout values back to the defaults within my proxy. Except in the case of syncing large new folders, getting the error shown here again then

[tootbrute]

This issue is closed but it seems many people still have this problem. Can we reopen the issue? I don't like messing around with nginx because I don't understand it that well.

I have this issue on one of my systems.

All my Bluefin (Silverblue spin) machines are all fine but my Bazzite machine has a problem syncing a large 11 GB folder that has many litle files in it.

$ flatpak list | grep nextcloud
Nextcloud Desktop	com.nextcloud.desktopclient.nextcloud	3.14.0	stable	system

$ rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:b72a876be97a559b1783cac2a708d0d488f50ca2bcbda37e0653dcc31ddb927b
                  Version: 40.20240922.0 (2024-09-23T05:00:35Z)
          LayeredPackages: ibus-chewing
            LocalPackages: lact-libadwaita-0.5.6-0.x86_64

It doesn't show the progress very well either.

Then it fails with the stream error that many others are experiencing.

[kmorber]

solved with desktop client 3.14.1