SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
-
Even when you're not using a reverse proxy, you're still going to be streaming to that socket.
So I woild recomend that flag still and retest, because the only time I personally have seen that error is when the socket was closed to streaming and it fails to get returned data.
wrote last edited by [email protected]thanks I have enabled websocket but the issue still exists
when I open http://localhost:3000/ in another browser it works perfectly fine. I think the issue is about the browser I used (firefox with a lot extension installed and setting tweaked)
-
when I open http://localhost:3000/ in another browser it works perfectly fine. I think the issue is about the browser I used (firefox with a lot extension installed and setting tweaked)
fuckin weird that an extension would inject invalid JSON into an API payload. if you’re gonna make a shady plugin at least test it lol
anyway, if that’s truly the issue i’d be worried about what my extensions were doing, personally.
-
fuckin weird that an extension would inject invalid JSON into an API payload. if you’re gonna make a shady plugin at least test it lol
anyway, if that’s truly the issue i’d be worried about what my extensions were doing, personally.
all the extension I installed is from https://addons.mozilla.org/, is there a quick way to check which extension is "inject invalid JSON into an API payload" ?
-
thanks I have enabled websocket but the issue still exists
when I open http://localhost:3000/ in another browser it works perfectly fine. I think the issue is about the browser I used (firefox with a lot extension installed and setting tweaked)
Yeah, trying an incognito window without the extensions would be the best place to start then, if you want to continue to use Firefox for it.
-
Yeah, trying an incognito window without the extensions would be the best place to start then, if you want to continue to use Firefox for it.
The problem is with this plugin https://addons.mozilla.org/en-US/firefox/addon/chameleon-ext/ Everything works fine with it disabled. Don't now why though
-
fuckin weird that an extension would inject invalid JSON into an API payload. if you’re gonna make a shady plugin at least test it lol
anyway, if that’s truly the issue i’d be worried about what my extensions were doing, personally.
The problem is with this plugin https://addons.mozilla.org/en-US/firefox/addon/chameleon-ext/ Everything works fine with it disabled.
The reason my chameleon breaks openwebui is because I changed a setting in it that it blocks all websocket connection
-
Yeah, trying an incognito window without the extensions would be the best place to start then, if you want to continue to use Firefox for it.
The problem is with this plugin https://addons.mozilla.org/en-US/firefox/addon/chameleon-ext/ Everything works fine with it disabled.
The reason my chameleon breaks openwebui is because I changed a setting in it that it blocks all websocket connection
-
The problem is with this plugin https://addons.mozilla.org/en-US/firefox/addon/chameleon-ext/ Everything works fine with it disabled.
The reason my chameleon breaks openwebui is because I changed a setting in it that it blocks all websocket connection
ah that makes sense
-
when I open http://localhost:3000/ in another browser it works perfectly fine. I think the issue is about the browser I used (firefox with a lot extension installed and setting tweaked)
It could be the
acceptsheader then... check if the request includesaccetps: application/json -
Hi how do I check the response?
F12 should open the browser developer tools, one panel will be the network requests.