Skip to content

Sync fails against webdav: JSON parse error #1838

@tom709

Description

@tom709

Which version of floccus are you using?

5.4.2.1

How many bookmarks do you have, roughly?

5000

Are you using other means to sync bookmarks in parallel to floccus?

No

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 Linux

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)

Nginx; config:

server {
listen 80 default_server;
listen 443 ssl default_server;
include snippets/snakeoil.conf;

charset utf-8;

index index.html index.htm index.nginx-debian.html;

root /share;
server_name _;

allow large files

send_timeout 3600;
client_body_timeout 3600;
keepalive_timeout 3600;
lingering_timeout 3600;
client_max_body_size 10G;
[...]
location /webdav/ {
root /var/dav;
dav_methods PUT DELETE MKCOL COPY MOVE;
dav_ext_methods PROPFIND OPTIONS;
create_full_put_path on;
dav_access user:rw group:rw all:rw;
autoindex on;
auth_basic "Administrator’s Area";
auth_basic_user_file /var/dav/htpasswd;
}
}

Describe the Bug

Have been syncing with floccus 5.4.2 for two weeks against the same webdav server; now without changing anything I suddenly get: "JSON.parse: bad control character in string literal at line 1 column 798734 of the JSON data | Last synchronized: 2 hours ago"
Push up once gives the same result, as does moving away the xbel file on the server.
Restarting nginx did not fix it neither.
The xbel file in encrypted, so there is nothing interesting to see in line 1.
I have a second Firefox profile that syncs against a second XBEL file on the same webdav server and that is still working.
The difference between the two files is: the failed one is much bigger and uses nested folder mapping.
Tried to get a log but nothing happens when I press the Logs button in floccus. This problem only occurs in the failed Firefox instance. I am adding the printout from the Firefox extension dev console collected while run one sync attempt.

Expected Behavior

sync sync sync :)

To Reproduce

unknown

Debug log provided

  • I have provided a debug log file

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions