esp32 sample won't connect to the browser

[anpin]

Hello, I'm evaluating this library for a project. When I run the esp32 sample it wouldn't connect to the frontend. It actually connected the first time, but any further attempts failed.

My esp32 and laptop are on the same network, both are right next to a router.

Any thoughts where I should poke?

[sepfy]

hi, i guess you can try to refresh the web page? because web page will send request to device when initialize. you need wait device is connected to server, then open the browser

[anpin]

I tried to restart the browser and also different browsers and devices. Once I saw STUN log message after the line with the link, but that’s it.

I also try to change device / client id to a random MAC address value.

Could this be limitation of public ally accessible services used by the sample?

[sepfy]

looks the signaling server is not working for you. Are you able to change the MQTT broker for testing?
https://github.com/sepfy/libpeer/blob/main/src/peer_signaling.h#L25

[anpin]

I’ve been trying to use local mosquito broker and coturn with custom root CA. Managed to enable logging for coremqtt, but signaling still fails with a TLS error. I think my root CA is not loaded correctly into the bundle by esp-idf. Will be back on it next week. On Thu, Sep 5, 2024 at 9:47 PM, sepfy ***@***.***> wrote: looks the signaling server is not working for you. Are you able to change the MQTT broker for testing? https://github.com/sepfy/libpeer/blob/main/src/peer_signaling.h#L25 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[sepfy]

Hello, i checked your log again and i found your peer signaling task is not running (also camera task). you can try to reduce stack size.

[anpin]

hi @sepfy, thanks for your suggestion, I've tried the updated example from b9ad642 and signaling now works fine.