json.parse: unexpected character at line 1 column 1 of the JSON data

[dsrtusr88]

Error box that persists and can't be cleared. Comes with every clean set up.

[jlesage]

Could you provide the output of: docker exec <container name> cat /tmp/.web_data.json

[dsrtusr88]

{ "applicationName": "Firefox", "applicationVersion": "101.0.1-r0", "dockerImageVersion": "22.10.4", "darkMode": false }

[jlesage]

Thanks, could you also provide the output of these commands (you can save it in text file):

docker logs <container name>

docker inspect <container name>

[jlesage]

Also, can you try to run:

docker run --rm -p 5801:5800 jlesage/firefox

Then access the container over port 5801 and verify if you get the problem. Ctrl+c will terminate the above command.

[jlesage]

Btw, which browser are you using to access the container ? Did you try another one?

[rjgould]

Btw, which browser are you using to access the container ? Did you try another one?

I've seen this when trying your Czkawka container using Firefox. When accessing the same instance using Edge it doesn't appear. Hope that helps.

[jlesage]

What version of Firefox and for which OS ? Do you have the same issue when using a private window ?

[rjgould]

What version of Firefox and for which OS ? Do you have the same issue when using a private window ?

Firefox is version 107.0.1 (64-bit) on Windows 11. It does it on both regular and private windows. Doesn't happen in Edge.

The HTML for the message displayed appears to be: `

Unexpected error encountered:

JSON.parse: unexpected character at line 1 column 1 of the JSON data

`

Feels like Firefox is just displaying something it should not as everything else works.

[jlesage]

What is the version of the image you are currently using ? You can see the image version from docker logs <container name>.

[jlesage]

(or by opening the left menu in the UI)

[rjgould]

(or by opening the left menu in the UI)

Czkawka v5.0.2 Docker Image v22.12.1

[jlesage]

Do you have any plugin running that might interfere with the page ? Do you still have the issue with the latest version ? If yes, could you open the developper tools in Firefox and report the errors under the Console tab ?

[dsrtusr88]

it was a plug-in, disabled it for that instance page and good to go!

[jlesage]

Thanks for the update ! Do you mind sharing the plugin that caused the issue ?