Virtual Files stopped working Client 3.2.3

[ghost]

As soon as i upgrade to 3.2.3 from 3.2.2 the virtual files stopped downloading get a windows error can download file then the files deletes automatically very very unstable

[claell]

Fortunately, this does not seem to happen for me.

I assume that a log file will be helpful

Ping @FlexW @allexzander as this might be urgent

[ghost]

I do have server side encryption on maybe with that feature there's issues? I will also try it in a different computer and see the results keep you posted

[allexzander]

I do have server side encryption on maybe with that feature there's issues? I will also try it in a different computer and see the results keep you posted

VFS does not work with E2EE at the moment. We are aiming to add support in 3.3.0 or 3.4.0. Work in progress. Which error you are getting? Is it a popup? You can download E2EE files/folders now if you right-click and choose "Always available locally", as a workaround.

[ghost]

Thank you for letting me know @allexzander Just wanted to let you know that on version 3.2.2 I didn't have an issue.

Now if I clicked on a Individual file it would show the windows transfer window and download and then say error downloading and when I mark it as always available offline it would download and get stuck right by the end and program would stop responding.

[allexzander]

@andyxheli You may want to try adding a new local sync folder. Similar to how you did that when connecting an account to the sync client but now, without adding an account, just a folder via the button "Add Folder Sync Connection". This should solve your problem if you do not try to double-click non-hydrated files in encrypted folders until they are hydrated with "Always available locally". Clumsy workaround, but, should help until we have implemented full VFS + E2EE support.

[ghost]

@allexzander Thank you for your suggestion im juts going to keep it off for now but i like turning it on so i can report issues and help anyway i can

Here's the error i get

[LucaOverflow]

It stopped workig for me as well. As soon as the Client wants to sync it just crashes without any error message. It stays visible with the sync icon in the task bar until i hover my mouse over it. Then it disappears. Downgrading to 3.2.2 didnt do the trick for me.

The log File doesnt seem to say something useful. At the end at least. It's very big so i didnt check the whole file.
Is there a separate error log file?

I dont use the server side encryption module.

Edit:
I checked on my laptop. There its working perfectly. Same Windows build and basically the same apps running.

[alex6480]

I have the same issue as @LucaOverflow

It happened back in 3.2.2 as well where it would occasionally crash when syncing. After I updated to 3.2.3 Nextcloud the crashes became so frequent that it cannot sync at all. I had to turn off virtual files for it to become usable again. I can't tell if the issue is due to the update, or if it's just that after updating I was syncing a lot of files, which made it more likely that a crash would occur before completion.

The log had no useful information, but the windows event viewer had logged af CldAPI crash.
Perhaps your problem is the same as this issue: #3349

[claell]

@LucaOverflow @alex6480 I doubt that you experience the same problem as @andyxheli at least your symptoms and setup is rather different. I am not even confident that you both have the same issue. So probably your problem can be better treated in an issue dedicated to your specific problems.

[Githopp192]

just some days ago, i did the upgrade from Nextcloud Desktop-Client 3.2.2 to 3.2.3.
Running Windows 10 with the newest Build (21H1); NC Version: 21.0.1

Getting x80070185 - Error when trying to download/open some (but not all !) documents -->

.

Choosing "make always available locally" make the PDF availabe again on the client.

Tested more files on the Windows Client with the Cloud symbol -->

The strange thing is, that some jpg files with the cloud symbol can be successfully downloaded/opened, others on the same folder and the same permissions not - like this one (IMG_1623088...jpg).

Restarting Nextcloud Desktop-Client did not solve the issue.

(btw - i say similar issues one blogs with Microsoft OneDrive x80070185 - Error - so i'm not sure, if this could also be a Microsoft Issue .. )

[ghost]

@Githopp192 just wanted go see do you also have encryption enabled ?

[stardust342]

I have the same issue, it only affects random files, others work fine. But it's about 50/50 so it's unusable for me.
I believe E2E encryption is disabled (I don't recall enabling it), however it is secured behind a reverse proxy with SSL.

[Githopp192]

@Githopp192 just wanted go see do you also have encryption enabled ?

Oh, sorry forgot to mention - no, no encryption enabled at all

[ghost]

@claell i don't think this is related too encryption.

[lorenzo-w]

Exact same issue here. Random files, but consistently always the same files, return an error when trying to open them and are thus unusable.

Here is an excerpt of my logs from when I tried to open one of these files:

2021-07-04 15:16:35:364 [ debug nextcloud.sync.vfs.cfapi.wrapper ]	[ 'anonymous-namespace'::cfApiFetchDataCallback ]:	Fetch data callback called. File size: 176172

2021-07-04 15:16:35:365 [ info nextcloud.sync.vfs.cfapi ]:	Received request to hydrate "D:\\NC\\NONE_OF_YOUR_BUSINESS.pdf" "1d770d39a0e0101"

2021-07-04 15:16:35:365 [ debug nextcloud.sync.database.sql ]	[ OCC::SqlQuery::bindValue ]:	SQL bind 1 -143314219672656488

2021-07-04 15:16:35:365 [ debug nextcloud.sync.database.sql ]	[ OCC::SqlQuery::exec ]:	SQL exec "SELECT path, inode, modtime, type, md5, fileid, remotePerm, filesize,  ignoredChildrenRemote, contentchecksumtype.name || ':' || contentChecksum, e2eMangledName, isE2eEncrypted  FROM metadata  LEFT JOIN checksumtype as contentchecksumtype ON metadata.contentChecksumTypeId == contentchecksumtype.id WHERE phash=?1"

2021-07-04 15:16:35:365 [ info nextcloud.sync.vfs.cfapi ]:	Couldn't hydrate, the file is not virtual

2021-07-04 15:16:35:366 [ info nextcloud.sync.vfs.cfapi.wrapper ]:	VFS replied for hydration of "D:\\NC\\NONE_OF_YOUR_BUSINESS.pdf" "1d770d39a0e0101" status was: false

Sync Client Version 3.2.3
OS: Windows 10 Home, Build 19041.1081
Nextcloud Version: 21.0.0

I also have E2E in use but none of the affected file are encrypted.

I hope with these infos you are able to track the bug down.

[Githopp192]

@claell i don't think this is related too encryption.

yes, @claell ... i think you're right ... there are many similar issues, where encryption is NOT enabled (like in my case).

[vithusel]

I can confirm the above also happens to me.

I've got 3 different instances on different physical servers. Only one of them are giving me this issue. I though it may be due to the push notify feature that was implements but removing that made no change.

[Githopp192]

tried to completely re-install Nextcloud Desktop-Client 3.2.3 (de-install/restart windows/install/restart windows).

Did not help - same situation.

[allexzander]

@Githopp192 Does it work if you just right-click a file in the Explorer and choose "Make always available locally"? Will the file get downloaded successfully?

[vithusel]

@Githopp192 Does it work if you just right-click a file in the Explorer and choose "Make always available locally"? Will the file get downloaded successfully?

This works for me. Would you like me to send any logs?

[Githopp192]

@vithusel - yes .. as i wrote before "Choosing "make always available locally" make the PDF availabe again on the client." - this is working.

Which logs would you like to see ?

[claell]

@andyxheli Seems to really be unrelated to encryption. Still, I think @LucaOverflow and @alex6480 have a different problem, they describe crashes. This issue seems to be more about not working file retrieval where the client does not crash.

[allexzander]

This should be fixed with #3501 and will be available in 3.2.4

[ghost]

@allexzander Thank you sir.

[Githopp192]

This should be fixed with #3501 and will be available in 3.2.4

Great !

[ghost]

Should i close this ?

[lorenzo-w]

Should i close this ?

I'd say let's wait until it is in the release and confirmed working there...

[ghost]

Copy that. Thanks

[allexzander]

Haven't released it yet, but, will do it soon. You can check if the issue is still happening with this build https://cloud.nextcloud.com/s/MHMYFcCxLjgAJa9

[vithusel]

Haven't released it yet, but, will do it soon. You can check if the issue is still happening with this build https://cloud.nextcloud.com/s/MHMYFcCxLjgAJa9

Im still having the same issue with this new build.

[vithusel]

One last thing to add.

As a last ditch effort i downgraded to 3.2.1 as a test and the issue still happens. Perhaps this is somehow linked to a recent update on server side?

[allexzander]

@vithusel This may be due to 3.2.3 has corrupted local files (not server ones), so, you have to add a new local sync folder, or, sync all broken files with "Make always available locally", and then, try downloading with a double-click.

[brtptrs]

The upcoming 3.2.4 version solves the problem for me. Thank you!

[vithusel]

@vithusel This may be due to 3.2.3 has corrupted local files (not server ones), so, you have to add a new local sync folder, or, sync all broken files with "Make always available locally", and then, try downloading with a double-click.

Awesome!

I have tested it after deleting and recreating the folder sync and all working as expected. Is there anyway of forcing this remotely? I've got a fair few users i will need to do this for.

[grandgeorg]

We have the same issue.
Desktop Client Verion 3.2.3
Windows 10 Version: 21H1

Even the option "make always available locally" for a file only works after forcing synchronisation for the whole share in the desktop client settings.

For us this is a major issue as our complete workflow is havilly disrupted.

Here an error message (in german):

[feutl]

@vithusel This may be due to 3.2.3 has corrupted local files (not server ones), so, you have to add a new local sync folder, or, sync all broken files with "Make always available locally", and then, try downloading with a double-click.

Awesome!

I have tested it after deleting and recreating the folder sync and all working as expected. Is there anyway of forcing this remotely? I've got a fair few users i will need to do this for.

I did the same within the NC app, without losing any data, it is working now again.
Took some time to rescan the files and sync what was necessary and missed.

[congoelmex]

downgrading to 3.2.2 and deleting the .sync.db file in the local nextcloud directory seems to have helped at one installation I maintain. On my personal computer I had the same problem and updated the Client to 3.2.4 - still the same problem. After deleting the sync.db it worked again. Of course the client had to resync everything...

[ghost]

Client 3.2.4 seems to fix this issue.

[congoelmex]

No it doesnt.

At least not by just installing.
If you just install 3.2.4 over 3.2.3 the Problem is still there.
You have to proactively delete the .sync.db on the client (of course with following resync) to make it work again.

[ghost]

@congoelmex I updated to 3.2.4 then i removed the sync folder added a new sync folder and everything looks good. Where's the issue?

[congoelmex]

Exactly that's the way (though you don't have to delete the whole sync folder - the .sync.db file seems to be enough).
I just stumbled over the short "Client 3.2.4 seems to fix this issue." If you just perform the Update of the client, the problem won't go away...

so. no offense - rather an addendum. ;)

[allexzander]

FYI, at the moment, we can only offer a workaround by manually deleting .sync.db. The fix is not something that's happening soon, so, anyone who is blocked by this regression will have to apply this workaround for now.

[congoelmex]

I can live with this solution, but your statement is...interesting... ;) I can imagine that this is kind of a deal breaker for a lot of people.

[isdnfan]

manually deleting the file might be a problem for lot of inexperienced users. would you mind to add menu option "perform full sync" running this steps automatically (delete/clean .sync.db and start fresh sync cycle)?

[allexzander]

@isdnfan Thank you for the suggestion. This could indeed be useful.

[kenvix]

Same problem. This seems to happen very often on unstable networks. In addition, in order to reduce the confusion, I think it is better to pop up a notification to show the reason why the synchronization operation fails.

[ghost]

No longer an issue running 3.3.1

[Josefpi92]

I am an unexperienced user and have this issue still with Nextcloud 3.14.2. I'm afraid and don't know how to manually delete .sync.db. Is this still the solution or is there, meanwhile, another workaround/fix