HTTP-Transmission Error

dacoex · November 20, 2018, 11:02pm

I would welcome some help.

For one of my remote folder shares, the synch does not work.

I am using client version 2.5git on a Ubuntu based system.

Here is the message:

“A HTTP transmission error happened. The server file discovery reply is missing data.
/path/to/local/folder”

or in German:
“Es hat such ein HTTP-Übertragunsfehler ereignet. Bei der Server-Dateierkennungsantwort fehlen Daten.
/path/to/local/folder”

Sorry I do not understand the message.

Please help, how can I fix this?

tflidd · November 21, 2018, 5:58am

Please check your server logfiles as well. The answer the server was giving you was perhaps incomplete or triggered an error. You can as well try to connect to a test setup (https://help.nextcloud.com/t/demo-instances-of-9-10-11-and-12-now-live) to make sure it’s not related to a client bug.

Alexander_Orlowski · November 28, 2018, 9:15am

Hello,

with the 2.5.1 client i get the same error.
With the 2.4.1 client everything works quite fine

tflidd · November 28, 2018, 11:27am

If a client update breaks something clearly, please create a bug report on Issues · nextcloud/desktop · GitHub

Alexander_Orlowski · November 28, 2018, 1:39pm

I checked the client log via the --logwindow switch

what i found was:

11-28 13:52:27:054 [ warning sync.discovery ]:	Missing properties: “Servicetechnik_ST1” 2 0 1543409545 “M” “” “-0000001oc3jkbyldutc”
11-28 13:52:27:054 [ warning sync.csync.updater ]:	opendir failed for - errno 10011
11-28 13:52:27:055 [ warning sync.engine ]:	ERROR during csync_update : “Es hat sich ein HTTP-Übertragungsfehler ereignet. Es fehlen Daten der Server-Antwort zur Dateisuche”

so i checked it via web.
i disabled the share and after then the 2.5 Client works as usual.

It seems that “Missing properties:” Causes the Error.

dacoex · November 28, 2018, 11:57pm

It’s definitely a result of the upgrade to 2.5

I just cannot tell from the log which error it is throwing.
The log seems to mix the two different shares.

elferink · December 2, 2018, 8:49am

Got 2.5 on new box form repository. Tried to find an previous version. Did not succeed.

dacoex · December 2, 2018, 8:48pm

I also tried to find version 2.4 for debian / ubuntu based systems. Nowhere in sight.
A downgrade does not seem to be foreseen.

msberends · December 3, 2018, 7:35pm

I managed to downgrade on Ubuntu 18.04.
I removed the current version, changed the PPA to ‘artful’ (= Ubuntu 17.10) and then installed nextcloud-client again.

Works flawlessly! This is not the first time I think of NC14 and this desktop client that they weren’t tested well enough…

dacoex · December 3, 2018, 9:13pm

Here the issue for reference:

If you know what logs we need to post, please tell me.

dacoex · December 3, 2018, 9:27pm

I removed the current version, changed the PPA to ‘artful’ (= Ubuntu 17.10) and then installed nextcloud-client again.

How did you do that? I can only downgrade to 2.3.3. which does not let me login to the accounts…

I can not see 2.4 on the repository:
http://ppa.launchpad.net/nextcloud-devs/client/ubuntu/pool/main/n/nextcloud-client/

This is not the first time I think of NC14 and this desktop client that they weren’t tested well enough…

I agree.

This seems to be a trend in software development. I spent some time yesterday fighting with Thunderbird. Some update in NC or Thunderbird crashed also the Sogo Connector based address book synchronisation

dacoex · December 3, 2018, 9:54pm

I just tested with the owncloud client which is in teh Ubuntu repos:

sudo apt install owncloud-client

Works like a charm. No issues!

What can is wrong with the Nextcloud client?
Does it actually need a dedicated client for Nextcloud or can both not be used?
What is the special features the Nextcloud client offers over the owncloud client?

msberends · December 3, 2018, 10:05pm

You’re right, I installed the 2.3.3 version, which works really well with my NC 14.0.4 instance!

Alexander_Orlowski · December 6, 2018, 9:47am

In my Scenario it doesnt matter which Client I used (Nextcloud or Owncloud), the error was the same.
with the 2.5 Clients I could fix the HTTP Transmission Error only by removing the shares via Web which had the “Missing properties” Error.

In some cases some Users could even see there files via the Webbrowser in the default view.

We downgraded our whole company back to the 2.4.3 Client (Owncloud). And its working fine again.
But this is a really strange.

dacoex · December 7, 2018, 1:01am

Yes, I confirm that 2.3.3 works.

But I had to configure the accounts & (local) folders again.

Can you please all upvote on:

github.com/nextcloud/desktop

Nextcloud community HTTP-Transmission Error

opened 10:40PM - 29 Nov 18 UTC

closed 08:46AM - 20 May 21 UTC

dacoex

bug stale

### Expected behaviour Normal synching ### Actual behaviour Client throws an error: "HTTP-Transmission Error" See also: https://help.nextcloud.com/t/http-transmission-error/41620 ### Steps to reproduce 1. Install client 2.5 2. Synch 3. ### Client configuration Client version: 2.5.0git Operating system: 4.15.0-39-generic / Linux Mint 19 Tara / Ubuntu bionic OS language: german Qt version used by client package (Linux only, see also Settings dialog): ? Client package (From Nextcloud or distro) (Linux only): Installation path of client: ### Server configuration  Operating system: ? Web server: ? Database: ? PHP version: 5 Nextcloud version: 14.02 Storage backend (external storage): ### Logs Please use Gist (https://gist.github.com/) or a similar code paster for longer logs. ```Template for output < 10 lines``` 1. Client logfile: Output of `nextcloud --logwindow` or `nextcloud --logfile log.txt` (On Windows using `cmd.exe`, you might need to first `cd` into the Nextcloud directory) (See also https://docs.nextcloud.com/desktop/2.3/troubleshooting.html#log-files) 2. Web server error log: 3. Server logfile: nextcloud log (data/nextcloud.log):

I really do not understand that they keep releasing new versions to the repository albeit this issue persists.

le_top · December 25, 2018, 10:02pm

Same issue here with NC 13.0.8 and Win10 Client 2.5.1 on a new PC.

I got https://download.nextcloud.com/desktop/releases/Windows/Nextcloud-2.3.3.1-setup.exe and installed that instead.

[My server is still running on V13 as it did not propose to upgrade to V14 yet]

Wesley_Wiertz · January 8, 2019, 8:51pm

I ran across this http transmission error (and managed to resolve it) in the following situation. Not sure if this helps to resolve the issue, but i’ll share it anyway.

What happened:

I shared a folder with a client
Client uploaded files to his root (instead of to the shared folder)
Nextcloud apparently put his upload in the Nextcloud root
I tried to move or copy the folder
–> error message appeared in my Windows client (2.5.1).

What i tried:

Uncheck shares in the desktop client (root folder, shared folder) -> did not resolve the error
Try to move the files in the web client -> operation forbidden
‘Unshare’ through the web client -> this resolved the error.

Other then this i haven’t had this error before with 2.5.1.

Gotzon · January 9, 2019, 9:36am

This workaround works for me.

After unshare through the web client, desktop client starts syncing. There was one shared folder that causes the error, unfortunately I missed what folder was and I can’t imagine why it causes the error.

It’s a little wired, because those folders are shared with other users and they don’t have this issue…

Thanks a lot Wesley

P.D. I found the error. I do not know how, but some files that were shared by a user, mysteriously disappears (I cant find them, not in the logs, not in the users folder or trash),but the users who have those files shared by this first user can see like the files were there. The strange thing is that those files have the folder icon instead of the excell file icon. This causes the http error in the sync program. I unshare those files an it works again.

bitpatroon · October 23, 2019, 7:21pm

I found a solution. Please check this:

j4mb4l4j4 · May 18, 2020, 9:04am

Hi, in my case it was because of the nginx Header Option:

add_header X-Frame-Options “SAMEORIGIN”;

after removing it, my users didn’t get the error again.

But could someone explain why ?
I mean it’s a useful security feature, which is working fine on my apache servers.

But as soon as i put it in my nginx environment it’s producing the “HTTP Trans Error”