Closed Amerlander closed 2 months ago
Have you restarted the vite dev server after you've changed the config file? I know this failure and it usually disappears with a restart: CTRL + C --> npm run dev
Yes, I restarted and tried different terminals (Powershell, wsl/ubuntu, vscode powerwshe;ll). The proxy in vite is applied, otherwise I would not get an error message about it.
Also, while opening the IP in the browser works fine the websocket is not working and a toast appears when opening the demo page:
I just tried opening the proxied url in the browser (which works) and to fetch it using API Dash (which does not work):
Seems like the board ist blocking the requests.
I tested different Browsers and it works in Firefox (HTTP and WS Proxy) In Edge the HTTP Proxy also works, but not the WS Proxy. In Opera it did not worked at all.
WS were also not working in Opera on the device IP without proxy.
I disabled the Browser-Default add-blockers and all add blocking extension, but that did not changed anything.
Interesting. I tested in on Firefox and Chrome and it did work on both. But glad you got it figured out.
I try to use the vite proxy to work on the sveltekit code. The board is available at 192.168.1.190, but the vite proxy does not seem to work:
Vite proxy config:
The Vite Server shows this error:![image](https://github.com/theelims/ESP32-sveltekit/assets/3764089/59225ed3-d60b-448c-a79a-cc9cc9b1be19)
The serial output shows, that there was a request:![image](https://github.com/theelims/ESP32-sveltekit/assets/3764089/985998fb-1fde-4e43-a29c-79a49e366f7b)
The error message seems very general to me, so I do not really have an idea where to expect the issue. Anyone had a similar issue before or an idea what I could check?
I'm using the ESP32_Relay_X8 which is equipet with an ESP32-WROOM-32E.