invalid json response body at http://127.0.0.1/:null/json/version reason: Unexpected token < in JSON at position 0
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 692
- Forks
- 103
- Avg merge
- 3m
- Merged PRs (30d)
- 4
Description
invalid json response body at http://127.0.0.1/:null/json/version reason: Unexpected token < in JSON at position 0
when I try to start from Ubuntu 20 64bit I run from terminal with sudo the AppImage
at processTicksAndRejections (internal/process/task_queues.js:85:5)
at async Object.exports.connect (/tmp/.mount_SimpleX7zND4/resources/app.asar/node_modules/puppeteer-in-electron/bin/index.js:36:18) {
message: 'invalid json response body at http://127.0.0.1/:null/json/version reason: Unexpected token < in JSON at position 0',
type: 'invalid-json'
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure on Ubuntu 20 64-bit by launching the AppImage with the reported command. Inspect resources/app.asar/node_modules/puppeteer-in-electron/bin/index.js around connect and investigate why the /json/version URL contains :null and returns non-JSON content. Done means the AppImage starts without the invalid JSON error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, typescript, ubuntu
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100