Troubleshooting

Troubleshooting

At least two responses required

Populate two environments in the mode whose action you select. Compare, Fetch & Compare, and Import cURL & Compare intentionally read different fields.

Invalid JSON

The whole input/response must be JSON. HTML error pages, plain text, comments, trailing commas, or adjacent documents are invalid. Format pasted JSON first to identify syntax errors.

URL rejected or remote request fails

The web proxy accepts public HTTPS hostnames on the standard port. It rejects HTTP, localhost, IP literals, embedded credentials, custom ports, non-public DNS results, and redirects to them. Other failures include expired credentials, non-success responses, DNS/TLS errors, 30-second timeout, body over 1 MB, or response over 50 MB.

For cURL, remove unsupported flags, file bodies (@file), shell operators, or multiple URLs.

Too many differences

Arrays compare by index. Reordering can generate many rows. Normalize or sort upstream data when business identity rather than order should control comparison.

Ignore rule hides too much

Rules match leaf names anywhere, not exact paths. id can remove IDs throughout the document. Prefer distinctive names and review generated suggestions.

Export differs from visible rows

Expected: filters affect the view only. Copy and downloads contain the full result. Clear filters when the visible table should represent the export.

Port 3000 is occupied

npm run dev -- --port 3001

For production, set PORT=3001 in your shell before npm run start.

Extension works differently

Extensions fetch directly from the browser; the web app uses a server proxy. CORS, browser-restricted headers, or permissions can differ. Inspect the popup's developer console and confirm the endpoint is HTTPS.

Build or tests fail

Confirm you are in the application repository, not .wiki; run npm install, then run npm test, npm run lint, and npm run build separately. Include the command, output, Node/npm versions, OS, and a minimal reproduction in a new issue.