mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #972] Syncing with Nextcloud Bookmarks stuck without doing anything #631
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#631
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @stoneubi on GitHub (Sep 27, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/972
Windows 10 - Firefox 92.0 64 bit.
Since the update from floccus 4.7.0 to 4.8.0 sync to nextcloud 21.0.4.1 ist not working any more. The bookmarks are not synching any more. Floccus addon tries to sync but the sync cycle is turning with no effect / end.
After deleting the addon and reinstalling floccus 4.7.0 via firefox addon page -> all versions sync is working as expected.
A test with version 4.8.0 leads to the same result = no synching.
I'm now on version 4.7.0 and sync works.
Hope this can be fixed. Till that the auto update on this addon is de-activated.
Beste regards
@github-actions[bot] commented on GitHub (Sep 27, 2021):
Hi @stoneubi! This issue is being automatically closed because it does not follow the issue template.
@marcelklehr commented on GitHub (Sep 27, 2021):
Which version of the bookmarks app is installed on the server?
Does this also happen with v4.8.1?
@imforumman commented on GitHub (Sep 27, 2021):
Bookmark is 10.0.0, but 4.7 worked with this version during the day today.
(Firefox won't let me downgrade because of an unsigned extension from GitHub and the about:config switch doesn't work without some developer version... damn, Mozilla is going Apple on us, I'm starting to be really pissed off with them, but this is off topic).
@marcelklehr commented on GitHub (Sep 28, 2021):
Since bookmarks v10 + floccus v4.8 floccus uses a locking mechanism. It can happen that one client sets the lock without ever releasing it. Floccus should override the lock automaticall after half an hour. Can you try with v4.8.2?
If you want to try manually resetting the lock, you can run the following
@stoneubi commented on GitHub (Sep 28, 2021):
Same here - Bookmarks App in Nextcloud is V 10.0.0 - my floccus is now 4.7 after manually "downgrade" - in fact a new installation. At the moment I only have one laptop with floccus installed. No additional clients. Is there any way / log where I can see if the lock was set?
@marcelklehr commented on GitHub (Sep 28, 2021):
You can only request the lock or release it. A read method doesn't make much sense for locks. If the above command doesn't fix the problem, it's not because of locking.
@stoneubi commented on GitHub (Oct 3, 2021):
Still the same on my setup. V 4.7.0 sync works perfect. All newer version are not working in my setup. Anyhow, at the moment I will stay on V4.7.0. Thanks.
@jcwinkler commented on GitHub (Oct 9, 2021):
I have the same issue on my devices (2x Kiwi-Browser on Android, 2x Firefox on Windows 10) using floccus 4.8.2 and bookmarks 10.0.0. Can I help in any way by providing debug information etc.? (I have nextcloud on a shared hosting so on the server side I am limited, but maybe from the client side I can provide any kind of needed information.)
@gothmog123 commented on GitHub (Oct 11, 2021):
same issue
@marcelklehr commented on GitHub (Oct 13, 2021):
In order to aid in debugging, please provide client-side logs. This is slightly advanced but I'm confident some of you may be technically inclined enough to pull this off (if you've ever debugged JavaScript this will be very easy, if not you may still find your way around the inspector).
Firefox
about:debugginginspectbutton next to floccus entrysync nowfor the account of your choice.Chrome
chrome://extensionsDeveloper modedist/html/background.htmlbutton in floccus' entry next to "Inspect views: "sync nowfor the account of your choiceYou may also have a look at the "Network" tab in the inspector window to see which requests are hanging/problematic.
@gothmog123 commented on GitHub (Oct 13, 2021):
replaced my email address with "myemailaddress"
background-script.js:1 2021-10-13T13:15:15.315Z Starting sync process for account myemailaddress@cloud3.linuxfabrik.io
cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 423 (Locked)
cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 423 (Locked)
cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 423 (Locked)
cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 423 (Locked)
cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 423 (Locked)
cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 423 (Locked)
cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 423 (Locked)
cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 423 (Locked)
cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 423 (Locked)
cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 423 (Locked)
cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 423 (Locked)
cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 423 (Locked)
cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 423 (Locked)
cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 423 (Locked)
background-script.js:11 POST https://cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock 423 (Locked)
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:3
_tryToStartAnother @ background-script.js:3
(anonymous) @ background-script.js:3
add @ background-script.js:3
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
s @ background-script.js:11
e.sendRequestWeb @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
i @ background-script.js:11
Promise.then (async)
u @ background-script.js:11
(anonymous) @ background-script.js:11
s @ background-script.js:11
e.sendRequest @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
s @ background-script.js:11
e.acquireLock @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
i @ background-script.js:11
background-script.js:11 POST https://cloud3.linuxfabrik.io/index.php/apps/bookmarks/public/rest/v2/lock 423 (Locked)
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:3
_tryToStartAnother @ background-script.js:3
(anonymous) @ background-script.js:3
add @ background-script.js:3
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
s @ background-script.js:11
e.sendRequestWeb @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
i @ background-script.js:11
Promise.then (async)
u @ background-script.js:11
(anonymous) @ background-script.js:11
s @ background-script.js:11
e.sendRequest @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
s @ background-script.js:11
e.acquireLock @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
(anonymous) @ background-script.js:11
i @ background-script.js:11
Promise.then (async)
u @ background-script.js:11
i @ background-script.js:11
Promise.then (async)
u @ background-script.js:11
i @ background-script.js:11
@marcelklehr commented on GitHub (Oct 13, 2021):
@gothmog123 Thanks for the quick response! In this case the problem should be resolved after waiting approximately half an hour. Alternatively, you can run the following curl command:
@gothmog123 commented on GitHub (Oct 14, 2021):
thanks for the help! waiting worked. so it seems it does the half hour once and then it'll work normally forever after that? no problem, i can live with that
@marcelklehr commented on GitHub (Oct 14, 2021):
Yes, that's the idea :)
@marcelklehr commented on GitHub (Oct 14, 2021):
Is there anyone for whom waiting does not work?
@Cyberavater commented on GitHub (Oct 14, 2021):
I've waited almost for 2hrs sync not working.
@stfnx commented on GitHub (Oct 17, 2021):
OS: Windows 10 Pro 21H1 x64
Firefox: 93.0 x64
Chrome: 89.0.4389.114 (ungoogled-chromium x64)
Floccus: 4.8.2
For me syncing is working on Chrome but not on Firefox.
Waiting an hour didn't solve the issue on Firefox. Chrome is still working.
I'm not using Nextcloud Bookmarks but a WebDAV share instead.
Circle is spinning forever. After Browser restart I can click a button to see a debug log:
It says I should check network connection.
But I can access and ping the server through IP and FQDN.
@marcelklehr commented on GitHub (Oct 18, 2021):
mmh, it's peculiar that it doesn't just stop and show the error, though :/
@gothmog123 commented on GitHub (Oct 18, 2021):
sorry not working again for me. seems like it looses login credentials or something. using 4.7 instead which works flawlessly
@marcelklehr commented on GitHub (Oct 21, 2021):
What does this mean? Is there an error message? Is it hanging again, longer than half an hour?
@marcelklehr commented on GitHub (Oct 21, 2021):
@stfnx To keep this somewhat organized please open a new issue, since you're using a different sync method.
@marcelklehr commented on GitHub (Oct 21, 2021):
As I cannot replicate this I'd appreciate if someone who experiences this could investigate using the addon inspector:
In order to aid in debugging, please provide client-side logs. This is slightly advanced but I'm confident some of you may be technically inclined enough to pull this off (if you've ever debugged JavaScript this will be very easy, if not you may still find your way around the inspector).
Firefox
about:debugginginspectbutton next to floccus entrysync nowfor the account of your choice.Chrome
chrome://extensionsDeveloper modedist/html/background.htmlbutton in floccus' entry next to "Inspect views: "sync nowfor the account of your choiceYou may also have a look at the "Network" tab in the inspector window to see which requests are hanging/problematic.
@gothmog123 Has done this, but the issue in the logs they sent has been solved.
@gothmog123 commented on GitHub (Oct 22, 2021):
Hi Marcel,
Thanks for looking into this and sorry to give you a hard time.
It seems like floccus loses account credentials for me and goes back to bob@example.org:
initializing account 16348498418460.9656220917837375
background-script.js:1 2021-10-22T06:09:06.867Z Starting sync process for account bob@example.org
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
background-script.js:11 POST https://example.org/index.php/apps/bookmarks/public/rest/v2/lock 404initializing account 16348498418460.9656220917837375
background-script.js:1 2021-10-22T06:09:06.867Z Starting sync process for account bob@example.org
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
example.org/index.php/apps/bookmarks/public/rest/v2/lock:1 Failed to load resource: the server responded with a status of 404 ()
background-script.js:11 POST https://example.org/index.php/apps/bookmarks/public/rest/v2/lock 404
@mnalis commented on GitHub (Oct 23, 2021):
Losing access credentials might perhaps be related to https://github.com/floccusaddon/floccus/issues/987 and https://github.com/floccusaddon/floccus/issues/971 ?
@marcelklehr commented on GitHub (Oct 23, 2021):
Mh, the cause of #971 was just that the UI wouldn't display the accounts anymore due to an error.
And in #987 the OP's log does not mention bob@example.org :/
@marcelklehr commented on GitHub (Oct 23, 2021):
At least I can remediate the endless polling for cases when the URL is wrong, so people get an error.
@mnalis commented on GitHub (Oct 23, 2021):
That should be useful, because if people get the error immediately after the credentials are lost, they might still remember what they were doing just before that happen, which could help in finding root case
@marcelklehr commented on GitHub (Nov 2, 2021):
The update is out and floccus shouldn't get stuck anymore.
@marcelklehr commented on GitHub (Nov 10, 2021):
@gothmog123 @stoneubi @imforumman @Cyberavater Is this fixed for you now?
@gothmog123 commented on GitHub (Nov 10, 2021):
Yes thank you. Actually my second bug report was my fault not floccus's sorry. But the first one is fixed definitely.
@marcelklehr commented on GitHub (Nov 11, 2021):
I've also found a bug that could cause hangs in case of unexpected status codes from the server, which is fixed now.
@stoneubi commented on GitHub (Nov 21, 2021):
Updated to V.4.8.4 and again same issue :-(
Downloaded the log file but this log file seems to be the last working one with V.4.7.0 showing successfully sync.
2021-11-21T13:15:22.963Z Starting sync process for account xxxxxxxx
2021-11-21T13:15:23.028Z Using "default" strategy
2021-11-21T13:15:23.123Z Overriding title of built-in node unfiled_____ Weitere Lesezeichen => Other Bookmarks
2021-11-21T13:15:25.533Z Loading sparse tree as necessary
2021-11-21T13:15:25.663Z { localTreeRoot:
2021-11-21T13:15:25.671Z { localDiff: [], serverDiff: [] }
2021-11-21T13:15:25.675Z { localPlan: [], serverPlan: [] }
2021-11-21T13:15:25.708Z Checking failsafe: 0/77=0
2021-11-21T13:15:25.742Z { reorderings: [] }
2021-11-21T13:15:25.743Z { reorderings: [] }
2021-11-21T13:15:25.813Z Overriding title of built-in node unfiled_____ Weitere Lesezeichen => Other Bookmarks
2021-11-21T13:15:25.866Z Successfully ended sync process for account xxxx
Is there anything I can try to solve this isse on my setup?
Thx
Stoneubi
@stoneubi commented on GitHub (Nov 21, 2021):
here some more details
@marcelklehr commented on GitHub (Nov 21, 2021):
@stoneubi The first two screenshots do not show anything informative or necessarily broken, afaict. Your inspector screenshot indicates that waiting half an hour should solve this problem.
Update: Just noticed there's more below the fold, so please scroll down in the inspector window.
@Cyberavater commented on GitHub (Nov 21, 2021):
Fixed for me in google drive.
@stoneubi commented on GitHub (Nov 21, 2021):
I wanted to show that V4.7.0 works perfect and after updateing to V4.8.4 sync is not working any more.
Also V.4.8.x never worked in my setup. I always get locked. Even waiting for some time still the same.
There is just the same below. It shows the locked information again and again till sync is canceled via the "Abbruch" button.
@marcelklehr commented on GitHub (Nov 21, 2021):
@stoneubi Can you try
a) the floccus account overview for errors
b) the inspector console
This may reveal an error that is hidden by the fact that floccus may try to sync again after a sync failure without giving the opportunity to see the error.
@WST1811 commented on GitHub (Dec 5, 2021):
I want to give Feedback. Using Floccus for a while on Nextcloud/Firefox. It works all the time great, thanks for the Tool. :) Today i found the Android App 4.8.4, working very good. ;)
In the last time i had problems with deleting bookmarks. I delete a bookmark, sync twice or more, but bookmark will not deleted on NC. Today i read the Thread here and try the solution: $ curl -u "username:password" -X DELETE https://your-nextcloud.com/index.php/apps/bookmarks/public/rest/v2/lock
It takes 2-4 seconds for execute, but after this, i sync again from Client with the deleted bookmarks, and the bookmarks where deleted on NC-Server.
Thanks again for this great Tool. ;)
@stale[bot] commented on GitHub (Dec 19, 2021):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@marcelklehr commented on GitHub (Dec 28, 2021):
@stoneubi ?
@stale[bot] commented on GitHub (Jan 11, 2022):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@stoneubi commented on GitHub (Jan 28, 2022):
Updated to floccus firefox addon V4.9.0. No changes on the Nextcloud Server. Sync works now :-)
@github-actions[bot] commented on GitHub (Mar 20, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.