mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #1291] Cannot authenticate to pCloud's webDAV #855
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#855
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 @kuxv on GitHub (Nov 20, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1291
Which version of floccus are you using?
4.17.1
Sync method
WebDAV
Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.
firefox 107.0 (64-bit)
Which version of Nextcloud Bookmarks are you using? (if relevant)
No response
Which version of Nextcloud? (if relevant)
No response
What kind of WebDAV server are you using? (if relevant)
https://ewebdav.pcloud.com
Describe the Bug
I'm getting E018: Couldn't authenticate with the server. Here is full log:
I can login into the https://ewebdav.pcloud.com from the Firefox or Total Commander's webDAV plugin so it looks like there is something going on in the Floccus plugin. Btw it might be a good idea to add something like a "Test connection" button to the settings.
Expected Behavior
The Floccus connects to the webDAV share.
To Reproduce
Connect to the pCloud webDAV share (https://ewebdav.pcloud.com) from Floccus Firefox extension.
Debug log provided
@kuxv commented on GitHub (Nov 23, 2022):
suddenly it started to work again...
@github-actions[bot] commented on GitHub (Nov 24, 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.