desktop
desktop copied to clipboard
nextcloud
[Bug]: Error updating metadata: Couldn't set pin state | Windows 11
⚠️ 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 and Desktop Releases for supported versions.
- [X] I agree to follow Nextcloud's Code of Conduct
Bug description
When I try to sync my files from Nextcloud to my Windows 11 dev pre release I had some issues and was meet with the error: Error updating metadata: Couldn't set pin state. I had OwnCloud installed and was working perfectly before but i decided to migrate over to Nextcloud but then I received these issues.
It was working fine on my other PC (Windows 10) so I decided to reinstall my system and im now not on Windows 11 dev release.
It was working fine for a couple of days but then all of a sudden it stopped working again.
Steps to reproduce
- Install Nextcloud app on Windows 11
- Start autosync
- Error recieved ...
Expected behavior
No errors when syncing.
Which files are affected by this bug
Temp Files (Free to remove)
Operating system
Windows
Which version of the operating system you are running.
Windows 11
Package
Appimage
Nextcloud Server version
23.0.3
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
{"reqId":"q7CXHFOb82F9BGHjW7Ft","level":2,"time":"2022-03-12T18:18:58+00:00","remoteAddr":"92.34.48.196","user":"--","app":"no app in context","method":"GET","url":"/","message":"Could not detect any host in https:///data/htaccesstest.txt","user>{"reqId":"q7CXHFOb82F9BGHjW7Ft","level":2,"time":"2022-03-12T18:18:58+00:00","remoteAddr":"92.34.48.196","user":"--","app":"no app in context","method":"GET","url":"/","message":"Could not detect any host in http:///data/htaccesstest.txt","userA>{"reqId":"NNvjNvFXsTON7XKy2HpW","level":2,"time":"2022-03-12T18:19:20+00:00","remoteAddr":"92.34.48.196","user":"--","app":"no app in context","method":"GET","url":"/","message":"Could not detect any host in https:///data/htaccesstest.txt","user>{"reqId":"NNvjNvFXsTON7XKy2HpW","level":2,"time":"2022-03-12T18:19:20+00:00","remoteAddr":"92.34.48.196","user":"--","app":"no app in context","method":"GET","url":"/","message":"Could not detect any host in http:///data/htaccesstest.txt","userA>{"reqId":"CkfFsp5dH80NgSMJAqua","level":2,"time":"2022-03-12T18:19:45+00:00","remoteAddr":"74.207.228.249","user":"--","app":"no app in context","method":"GET","url":"/","message":"Could not detect any host in https:///data/htaccesstest.txt","us>{"reqId":"CkfFsp5dH80NgSMJAqua","level":2,"time":"2022-03-12T18:19:45+00:00","remoteAddr":"74.207.228.249","user":"--","app":"no app in context","method":"GET","url":"/","message":"Could not detect any host in http:///data/htaccesstest.txt","use>{"reqId":"qOOR0XK8VgWTMOgXanPz","level":2,"time":"2022-03-12T18:19:47+00:00","remoteAddr":"172.105.206.169","user":"--","app":"no app in context","method":"GET","url":"/","message":"Could not detect any host in https:///data/htaccesstest.txt","u>{"reqId":"qOOR0XK8VgWTMOgXanPz","level":2,"time":"2022-03-12T18:19:47+00:00","remoteAddr":"172.105.206.169","user":"--","app":"no app in context","method":"GET","url":"/","message":"Could not detect any host in http:///data/htaccesstest.txt","us>{"reqId":"1kgBA7BxtllxR4NtMSVh","level":2,"time":"2022-03-12T18:19:48+00:00","remoteAddr":"168.119.96.54","user":"--","app":"no app in context","method":"GET","url":"/","message":"Could not detect any host in https:///data/htaccesstest.txt","use>{"reqId":"1kgBA7BxtllxR4NtMSVh","level":2,"time":"2022-03-12T18:19:48+00:00","remoteAddr":"168.119.96.54","user":"--","app":"no app in context","method":"GET","url":"/","message":"Could not detect any host in http:///data/htaccesstest.txt","user>{"reqId":"1nxa9lvcAytBlVzcbD6i","level":2,"time":"2022-03-12T18:19:48+00:00","remoteAddr":"172.105.190.118","user":"--","app":"no app in context","method":"GET","url":"/","message":"Could not detect any host in https:///data/htaccesstest.txt","u>{"reqId":"1nxa9lvcAytBlVzcbD6i","level":2,"time":"2022-03-12T18:19:48+00:00","remoteAddr":"172.105.190.118","user":"--","app":"no app in context","method":"GET","url":"/","message":"Could not detect any host in http:///data/htaccesstest.txt","us>{"reqId":"r6aiJhLMIWwDyEbsqlLb","level":2,"time":"2022-03-12T18:22:16+00:00","remoteAddr":"92.34.48.196","user":"--","app":"no app in context","method":"POST","url":"/index.php","message":"Could not detect any host in https:///data/htaccesstest.>{"reqId":"r6aiJhLMIWwDyEbsqlLb","level":2,"time":"2022-03-12T18:22:16+00:00","remoteAddr":"92.34.48.196","user":"--","app":"no app in context","method":"POST","url":"/index.php","message":"Could not detect any host in http:///data/htaccesstest.t>
Additional info
No response
I have been getting the same problem for a week or so now as well.
It started with files changing upload dates to future or 1970 dates. Figured that out and manually reuploaded files or used command to change them, and now this happens all the time. Doesn't seem to be server sided. It only happens with VFS.
Lemme know if anybody needs logs or something, quite new to bug reports, so I may need some help.
Windows 11 - Insider dev 22H2 22598
Got here the same problem. Every time you restart the app, sync goes a bit further in files but crashes anyway. Didn't tried on Windows 10 for now. I think I'll look for a WebDav sync app for now, until this bug is fixed.
Issue persists after Server updated to 23.0.4 and Client version is at 3.4.4.
Issue persists after Server updated to 23.0.4 and Client version is at 3.4.4.
Checked today, same issue.
Same issue, Windows 11 x64 Client version 3.5.0 Server version 23.0.4 - 23.0.4.1
I do think it's a problem about system version. You can run your program with the compatibility option (run as Windows 8).
New server version released today and I updated (24.0.0) but problem persisted. I tried running the app with compatibility option (run as Windows 8) but same problem.
Updated to the last version of the Nextcloud App today, same issue. I'm updating Windows 11, maybe it'll help. I registered for beta too, maybe a fix will come faster this way...
I'll try the compatibility wizard too. I think this issue is related to a change in Windows' way to handle remote files (like with OneDrive, Nextcloud, ...). Indeed, when I try to open Nextcloud's folder, explorer crashes.
Yeah I'm experiencing the same problem. I'm using the OwnCloud client instead as a hot fix, it doesn't have this problem on Windows 11 with virtual file system.
Yeah I'm experiencing the same problem. I'm using the OwnCloud client instead as a hot fix, it doesn't have this problem on Windows 11 with virtual file system.
Very good tip, it works for me. Guess I'm gonna uninstall Nextcloud app until a patch is published.
Also been having this issue for some time now. It especially occurs when the client is trying to syncrhonize hidden files created by Synology DSM. Namely the @eaDir-folders. It turns out, Nextcloud only hides folders beginning with punctuation.
Turning of synchronization for folders and files named @eaDir in the Nextcloud Client at most fixed the problem. Although it keeps occuring now and then when trying to sync new folders from the server to the client.
I only have been able to resolve this by turning off virtual files and manually selecting the folders I need synced. They have to be offline however which is annoying.
You can still use Owncloud Desktop. It works flawlessly for me.
Find the client on the Owncloud website.
On Wed, 3 Aug 2022, 15:19 Marcus Liljebergh, @.***> wrote:
3.5.4 today, no solution yet...
— Reply to this email directly, view it on GitHub https://github.com/nextcloud/desktop/issues/4410#issuecomment-1203941307, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJCPTBAPR4N7JTN2LVS744LVXJWXVANCNFSM5SO5VCAQ . You are receiving this because you commented.Message ID: @.***>
could any of affected people test this build with a fix that is in the next stable version due soon https://cloud.nextcloud.com/s/K4ynRkJJMFDw4xx
@mgallien
It has been stable so far, It never passed 3000 files before this update so it seems to be fixed, but I'll update you when it's finished 👍
could any of affected people test this build with a fix that is in the next stable version due soon https://cloud.nextcloud.com/s/K4ynRkJJMFDw4xx
@mgallien
This issue seems to be fixed for me, sync finished successfully for virtual file support. 98000+ files from internal server and external storage (samba)
I am closing it people do not hesitate to ping me in case you still have issues after migrating to 3.6.0 release https://github.com/nextcloud/desktop/releases/tag/v3.6.0
I am closing it people do not hesitate to ping me in case you still have issues after migrating to 3.6.0 release https://github.com/nextcloud/desktop/releases/tag/v3.6.0
I'm seeing this error message right now, with version 3.13.0 of the client, on Windows 10
