[BUG] Companion server loses connection every minute

[simenad]

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

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

Is this a bug in companion itself or a module?

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

Is there an existing issue for this?

• [x] I have searched the existing issues

Describe the bug

I just installed Companion and it will drop connection after about 1 minute. I have no modules or nothing. I've tried the stable and beta version. Seems to be happening between the 2nd to 6th second every minute regardless of when I start the server.

Steps To Reproduce

1. Start Companion
2. Wait 1 minute
3. "Houston, we have a problem"
4. Repeat step 2.

Expected Behavior

No response

Environment (please complete the following information)

- OS: Windows 11
- Browser: Vivaldi 7.4.3684.50 / Chrome 136
- Companion Version: 4.0.2+8076-stable-7bdc01f6d9

Additional context

Logs:

`25.06.17 23:32:03 Registry: constructing core modules 25.06.17 23:32:03 Registry: launching core modules 25.06.17 23:32:03 Service/OscSender: Ready to send OSC commands 25.06.17 23:32:03 UI/Handler: socket J_8rt15C_DXM5Z-sAAAB connected 25.06.17 23:32:03 UI/Handler: socket J_8rt15C_DXM5Z-sAAAB disconnected 25.06.17 23:32:03 UI/Handler: socket pni7u3oFrngLTXcgAAAD connected 25.06.17 23:32:03 UI/Handler: socket pni7u3oFrngLTXcgAAAD connected 25.06.17 23:32:04 UI/Update: fresh update data received {}

25.06.17 23:33:02 Registry: constructing core modules 25.06.17 23:33:02 Registry: launching core modules 25.06.17 23:33:02 Service/OscSender: Ready to send OSC commands 25.06.17 23:33:03 UI/Handler: socket zhvq1_jn3gXf4oV2AAAB connected 25.06.17 23:33:03 UI/Handler: socket zhvq1_jn3gXf4oV2AAAB disconnected 25.06.17 23:33:03 UI/Handler: socket iL0aJXCdyiWICxcmAAAD connected 25.06.17 23:33:03 UI/Handler: socket iL0aJXCdyiWICxcmAAAD connected 25.06.17 23:33:03 UI/Update: fresh update data received {}

25.06.17 23:34:02 Registry: constructing core modules 25.06.17 23:34:02 Registry: launching core modules 25.06.17 23:34:02 Service/OscSender: Ready to send OSC commands 25.06.17 23:34:03 UI/Handler: socket K-j5fmRLX8Wj84ZVAAAB connected 25.06.17 23:34:03 UI/Handler: socket K-j5fmRLX8Wj84ZVAAAB disconnected 25.06.17 23:34:03 UI/Handler: socket _m4KLzvrtNs0bq6YAAAD connected 25.06.17 23:34:03 UI/Handler: socket _m4KLzvrtNs0bq6YAAAD connected 25.06.17 23:34:04 UI/Update: fresh update data received {}

25.06.17 23:35:22 Registry: constructing core modules 25.06.17 23:35:23 Registry: launching core modules 25.06.17 23:35:23 Service/OscSender: Ready to send OSC commands 25.06.17 23:35:23 UI/Handler: socket WaNe9JHCrrcUFHjWAAAB connected 25.06.17 23:35:24 UI/Handler: socket WaNe9JHCrrcUFHjWAAAB disconnected 25.06.17 23:35:24 UI/Handler: socket msKiZLvBbCRG58K-AAAD connected 25.06.17 23:35:24 UI/Update: fresh update data received {}

25.06.17 23:36:06 Registry: constructing core modules 25.06.17 23:36:06 Registry: launching core modules 25.06.17 23:36:06 Service/OscSender: Ready to send OSC commands 25.06.17 23:36:07 UI/Handler: socket 7uB-vbq0U5u3bF1TAAAB connected 25.06.17 23:36:07 UI/Handler: socket 7uB-vbq0U5u3bF1TAAAB disconnected 25.06.17 23:36:07 UI/Handler: socket Y4pKETl5P6N_o29hAAAD connected

25.06.17 23:37:05 Registry: constructing core modules 25.06.17 23:37:05 Registry: launching core modules 25.06.17 23:37:05 Service/OscSender: Ready to send OSC commands 25.06.17 23:37:05 UI/Handler: socket 6k17IJy5v8wBeYQ7AAAB connected 25.06.17 23:37:06 UI/Handler: socket 6k17IJy5v8wBeYQ7AAAB disconnected 25.06.17 23:37:06 UI/Handler: socket xgKDYkTlYN-PUXf4AAAD connected 25.06.17 23:37:06 UI/Update: fresh update data received {} `

[simenad]

I've tried, with no luck:

• Uninstalling and remove all leftover files with BCUninstaller.
• Added firewall exceptions.
• Downgrading to 3.5.5.
• Changed time and date...

[Julusian]

I'm not entirely ignoring this, but I haven't had any ideas on where to start debugging this.

Is that log taken from the log file? Presumably the launcher window remains running during this, and is recovering it. Do you have the developer module path set? If so, maybe something in that is causing it to restart (although that should be visible in the logs)

[KzBoy]

I'm seeing this exact same issue on v4.0.3

I get the 'Houston, we have a problem!' overlay. Often it will reconnect, sometimes it just gets stuck until I refresh.

I have no modules installed yet; this is a fresh install on a new Raspberry Pi. I'm also not able to install modules as the version info isn't loading.

I'll do some troubleshooting and report back.

[KzBoy]

Ok, so the host (RPi) was connected on a separate subnet (Dedicated for A/V Equipment) that is routable from my local subnet (Main building network).

There is also a wireless uplink to this section of the network as it is a standalone test rig. I can ping the unit with average ping times of 6ms, max of 15ms.

I'm guessing it has something to do with timeout, or subnet as once I moved the unit to my local subnet and bypassed the wireless uplink the issues are gone.

EDIT: There are also networked audio protocols in use on that subnet. I have noticed those causing odd issues with some devices in the past. This is Q-LAN/Dante.