mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-27 15:15:57 +03:00
[GH-ISSUE #727] Syncing failed with E018 #467
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#467
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 @stfnx on GitHub (Nov 11, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/727
Describe the bug
I do get
Syncing failed with E018: Authentifizierung fehlgeschlagenerror when I try to sync Floccus with an WebDAV URL.I am able to access this WebDAV URL through the browser and I am able to login successfully.
The WebDAV is shared from TrueNAS and I've set the port to 8081.
I've entered the URL in this format:
https://truenas.local.domain.tld:8081/ShareIt uses a Let's Encrypt certificate. No self-signed certificates are involved.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should work.
Desktop
Server
Debug log
It just repeats the following lines:
@stfnx commented on GitHub (Nov 12, 2020):
Actually I've set the authentication to "digest authentication" instead of "plain authentication" in the FreeNAS WebDAV settings.
That was the issue. I've set it to "plain" now and it works.
This was in no way related to Floccus.
Sorry for posting this here.
I really thought I did enough troubleshooting, but I guess I've missed that option.
@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.