mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-27 07:05:59 +03:00
[GH-ISSUE #628] Error E018 #423
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#423
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 @InfamousUser on GitHub (Aug 8, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/628
Describe the bug
Extension displays "Couldn't authenticate with the server" error after finishing bookmark sync.
2020-08-08T18:02:26.007Z { [Error: 1 errors] list: [ { [Error: 1 errors] list: [Object] } ] } 2020-08-08T18:02:26.008Z { [Error: 1 errors] list: [ { [Error: 1 errors] list: [Object] } ] } 2020-08-08T18:02:26.008Z { [Error: 1 errors] list: [ [Error: E018: Couldn't authenticate with the server] ] } 2020-08-08T18:02:26.008Z [Error: E018: Couldn't authenticate with the server] 2020-08-08T18:02:26.009Z Syncing failed with E018: Couldn't authenticate with the serverI've reinstalled Floccus, cleaned all bookmarks on the server, added the account to Floccus and triggered a fresh sync, it went to sync all bookmarks (I assume all got synced, maybe not) and then display the error a few minutes later.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
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
It is often useful to provide a debug log file along with the issue. You can obtain a debug log of the most recent sync runs by clicking 'Debug log' in the bottom right corner of the floccus panel in your browser.
Note: As your debug log usually contains large parts of your bookmark data, instead of attaching it publicly to the issue here, I recommend uploading it privately at the following URL https://klehranlage.net/index.php/s/7nn82NSBsfQKdsJ
Additional context
Add any other context about the problem here.
@marcelklehr commented on GitHub (Aug 10, 2020):
Could you please fill out the template, specifically the software versions you are using?
@InfamousUser commented on GitHub (Aug 10, 2020):
Apologies, filled.
@marcelklehr commented on GitHub (Aug 21, 2020):
Could you try updating the bookmarks app? This might be an incarnation of a server-side bug.
@marcelklehr commented on GitHub (Aug 21, 2020):
If that doesn't help you can try checking the network requests:
Firefox
about:debuggingdebugbutton 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 choice@marcelklehr commented on GitHub (Sep 1, 2020):
An news?
@InfamousUser commented on GitHub (Sep 1, 2020):
Sorry, been busy with something else, will try to retest this soon.
@InfamousUser commented on GitHub (Sep 7, 2020):
Okay, that narrowed it down pretty quickly. It is a firewall blocking it due to the bookmark being a potentially unwanted content site, which is bound to happen to at least one of the bookmarks with thousands of them on the system. There's several of these.
What fascinates me is that, from what I undestand, the firewall managed to pick it up even though the browser wasn't actually accessing that site, but simply sending the URL as a data to another site. It presents a dialogue to continue at own risk, but it is not possible to see the dialogue since the exchange is completely internal, it's visible in that inspector window though. Looks like the sync will never complete due to the error too.
Can this transfer somehow be encapsulated to not trigger this? I don't want to remove all of them since not all are dangerous, but I also don't want to turn off protection, I want to be warned, but a bookmark transfer being blocked is ridiculous when I'm not even accessing the site, merely pointing to it.
@marcelklehr commented on GitHub (Sep 8, 2020):
I'm glad we got it figured out :)
I think handling this is outside the scope of this extension. I recommend to either remove the bookmarks, switch to a different "firewall" or turn it off.
@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.