[BUG] WebSocket closed Emulator Stuck

[ukiews]

Make sure you're on the latest stable or beta build

• I have tested this on the latest stable or beta release

Is this a bug in companion itself or a module?

• I believe this to be a bug in companion and not a specific module

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

This issue seems to have crept in v. 4.1, but has become worse in 4.2.1.

Using an iPad as a wall controller to run a companion emulator (pin lock enabled), after some time a WebSocket closed error appears.
Clicking "Retry" does nothing.
Before this kind of error would rarely appear and the app would try to reconnect automatically.

As a side note: Thank you for the new sleek pin-lock layout! It would be very helpful to be able to change the "Emulator Locked" text to custom text (e.g. "Enter Room Pin").

Steps To Reproduce

No response

Expected Behavior

No response

Environment (please complete the following information)

- OS: Pi5
- Companion Version: 4.2.1 (docker)

Additional context

No response

[ukiews]

Tried this on my iPhone---same behavior.

[Julusian]

Are you accessing companion via a reverse proxy?
As of 4.1 this now requires websockets, so a incorrectly configured reverse proxy could be breaking the connections.

That retry button was not wired to do anything, I suppose it shoudlnt be shown at all..
But it is automatically retrying the connection every few seconds, with an expotential backoff with a max wait of 30s. So it should be managing to reconnect, in my testing where I force the connection to break it reconnects instantly (looking like a quick flash in the ui)

[ukiews]

No reverse proxy. Ipad and rasPi are on same lan. Nothing has changed for 6+ months in terms of basic setup and network.
The only other thing I can think about is iOS updates, which have been run when available (26.2 now).

Regarding expotential backoff, are you saying that once it reaches 30s it will keep retrying indefinitely every 30s?

[Julusian]

Regarding expotential backoff, are you saying that once it reaches 30s it will keep retrying indefinitely every 30s?

yes

[ukiews]

Have you tested this with the latest iOS? Are there any recommended settings to check network side (I am using unifi)?

[Julusian]

I dont have any iphones or ipads, so I can't really test this properly myself.
I have tried with the ios simulator in xcode, and havent been able to reproduce this. I did find that it was bad at detecting network loss, and was showing the emulator for 30s+ with nothing happening, so have tried to fix that

[ukiews]

Looks like it's still not reconnecting.
The reconnect button now does try to reconnect, but it is stuck in the state of reconnecting.
I am using the web app feature of iOS ("Add to Home Screen") to launch the emulator.
I have to force quit and restart the web app several times for the connection to be re-established...