mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 14:45:59 +03:00
[GH-ISSUE #699] Failed PUT Request #447
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#447
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 @GrahamH68 on GitHub (Oct 20, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/699
Describe the bug
Since v4.4.0 (also with v4.4.1) on Firefox (Win10) I am receiving the error "E019: HTTP status 403. Failed PUT request. Check your server configuration and log." and am unable to sync with Nextcloud Bookmarks. Sync is still working on another maching that is using v4.3.x on Firefox (Win 10).
To Reproduce
Steps to reproduce the behavior:
Manual or Auto-Sync causes the error. No sync occurs.
Expected behavior
A clear and concise description of what you expected to happen.
Expected sync to take place.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Server (please complete the following information):
Note: Please write down the actual version numbers instead of writing 'latest'.
Debug log
2020-10-20T23:08:58.075Z Starting sync process for account @
2020-10-20T23:08:58.075Z Starting sync process for account @
2020-10-20T23:08:58.190Z onSyncStart: begin
2020-10-20T23:08:58.192Z https:///remote.php/webdav/.floccus-L1BlcnNvbmFs.lock
2020-10-20T23:08:58.075Z Starting sync process for account @
2020-10-20T23:08:58.190Z onSyncStart: begin
2020-10-20T23:08:58.192Z https:///remote.php/webdav/.floccus-L1BlcnNvbmFs.lock
2020-10-20T23:08:59.734Z https:///remote.php/webdav/.floccus-L1BlcnNvbmFs.lock
2020-10-20T23:08:58.075Z Starting sync process for account @
2020-10-20T23:08:58.190Z onSyncStart: begin
2020-10-20T23:08:58.192Z https:///remote.php/webdav/.floccus-L1BlcnNvbmFs.lock
2020-10-20T23:08:59.734Z https:///remote.php/webdav/.floccus-L1BlcnNvbmFs.lock
2020-10-20T23:08:59.805Z Syncing failed with E019: HTTP status 403. Failed PUT request. Check your server configuration and log.
2020-10-20T23:08:59.812Z onSyncFail
2020-10-20T23:08:58.075Z Starting sync process for account @
2020-10-20T23:08:58.190Z onSyncStart: begin
2020-10-20T23:08:58.192Z https:///remote.php/webdav/.floccus-L1BlcnNvbmFs.lock
2020-10-20T23:08:59.734Z https:///remote.php/webdav/.floccus-L1BlcnNvbmFs.lock
2020-10-20T23:08:59.805Z Syncing failed with E019: HTTP status 403. Failed PUT request. Check your server configuration and log.
2020-10-20T23:08:59.812Z onSyncFail
Additional context
Add any other context about the problem here.
This has been working flawlessly for over a year until the Firefox plugin updated to v4.4.0 from v4.3.x and the issue continues with v4.4.1.
@marcelklehr commented on GitHub (Oct 21, 2020):
Your account settings seem to be broken. Try removing the account and recreating it.
@ghost commented on GitHub (Oct 22, 2020):
Same issue for me since the upgrade to 4.4.1 on Linux, Firefox 81.0.1. Removing and re-adding the account results in the same error:
E019: HTTP status 403. Failed PUT request. Check your server configuration and log.Sync continues to work on Chromium with version 4.3.
@marcelklehr commented on GitHub (Oct 22, 2020):
@banjonerd could you submit your debug log?
@ghost commented on GitHub (Oct 22, 2020):
Yes, of course:
Please let me know if I can provide any more information that might help.
:edited credentials/URL for privacy
@marcelklehr commented on GitHub (Oct 22, 2020):
@banjonerd This indicates that your credentials are wrong
@ghost commented on GitHub (Oct 22, 2020):
I cut and pasted the same credentials into the Firefox and Chromium versions to test. Firefox still fails with the same error and Chromium continues to sync successfully.
@marcelklehr commented on GitHub (Oct 22, 2020):
Mmh, let's try the same thing with a curl command.
This should return a lot of things, but most importantly a line that says
HTTP/2 204(could also say HTTP/1.1 or similar)@ghost commented on GitHub (Oct 22, 2020):
That returns
HTTP/1.1 403 ForbiddenPlease let me know if you'd like the full error. I'll be away from my PC for a bit but will respond ASAP. And thanks for your trouble-shooting efforts.
@GrahamH68 commented on GitHub (Oct 22, 2020):
Some additional info which may help:
If I use my nextcloud username & account password then it works fine, but if I use the application token instead of the password (which has worked for months) then it fails with the error above.
I've just tried creating a new app token (without filesystem access) and I get the same error.
If I then enable File System Access on the Token then it works again, so this seems to have changed since 4.3.0.
It seems like I now have a workaround - enable file system access for the token.
@marcelklehr commented on GitHub (Oct 22, 2020):
Aha. That makes sense. Since v4.4.0 floccus uses a file to coordinate access between different instances. I will update the error message to reflect these insights.
@GrahamH68 commented on GitHub (Oct 22, 2020):
That explains why I'm seeing all these nextcloud log entries "Synced .floccus-xxxxxx.lock"
I've also noticed that sync is take much much longer than with v4.3.0 - minutes rather than seconds.
@marcelklehr commented on GitHub (Oct 22, 2020):
I will deal with that soon.
mmmh. I'll investigate that.
@marcelklehr commented on GitHub (Oct 22, 2020):
Mmmh, apparently the hash endpoint is getting blocked by the browser.
UPDATE: I've found the issue that is causing slow syncs and will publish a new server app release soon.
@GrahamH68 commented on GitHub (Oct 22, 2020):
Thanks Marcel, I love this plugin and really appreciate your work in creating and maintaining it :-)
@ghost commented on GitHub (Oct 22, 2020):
Thanks, @GrahamH68; allowing file system access also worked for me (though I'm not experiencing the slow syncs that you are; my speed seems normal). I should've added earlier that I'm using 2FA on my account, so I use an app password with Floccus.
Also, count me in as being very appreciative of Marcel for making and maintaining this app. I can't contribute code but I do make a monthly donation. ^_^
@errolsancaktar commented on GitHub (Oct 29, 2020):
i cant seem to get mine working again, tried w/ app password and real password:
@marcelklehr commented on GitHub (Oct 29, 2020):
423 means the resource is locked 😱
Depending on which server you are using, try unlocking .floccus-xxx.lock
@errolsancaktar commented on GitHub (Oct 29, 2020):
i tried deleting it. is that what you mean?
@marcelklehr commented on GitHub (Oct 29, 2020):
WebDAV has file locking. If the file is locked, floccus cannot touch it or change it. Floccus doesn't lock files, though. So, a different entity locked the file and now you're stuck
@errolsancaktar commented on GitHub (Oct 29, 2020):
is it more complicated than deleting the file?
@marcelklehr commented on GitHub (Oct 29, 2020):
If you deleted the file and you still get 423, then yes.
@marcelklehr commented on GitHub (Oct 29, 2020):
@errolsancaktar let's continue this in #712
@github-actions[bot] commented on GitHub (Mar 21, 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.