[BUG] Companion on Intel Sequoia 15.1

[Lukeb873]

Is this a bug in companion itself or a module?

• I believe this to be a bug in companion

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I'm setting up a machine that will only run companion. We heavily use companion and are needing to have everything point to this one installation with satellite. I'm using a older 2018 Intel mac mini for the "server." It's a intel i7 with 16gb of DDR4 ram. More than enough for companion. The mac is on mac OS Sequoia 15.1. Currently the mac mini has wifi turned off and has a static IP assigned to the ethernet port. Currently every module is spitting out errors. If I export the config and load it onto my M2 Air, everything works fine. In my head this rules out Sequoia being the issue and it being an intel mac is now the issue. I then tried the same config on an Intel iMac running Sonoma 14.7. It also worked fine on that. So now I'm not sure if it's a companion thing, an intel thing, or a software version thing. I also tried another mac mini running Sequoia 15.1 with the same config on a wired connection with wifi off and a static IP and ran into the same issue. This mac mini was a intel i5 16gb DDR4 from 2018.

Everything was running a freshly downloaded version of 3.4.3 from the website

Steps To Reproduce

No response

Expected Behavior

No response

Environment (please complete the following information)

- OS: Sequoia 15.1
- Browser: FireFox
- Companion Version: V3.4.3

Additional context

No response

[Julusian]

Those errors are all suggesting that companion isn't able to reach various hosts on your network.
Make sure that they are reachable and that the macos firewall isn't blocking the connections.

We are not doing any differently in how these connect for intel macos, we build each module once and use that same build on every os

[Lukeb873]

I am able to successfully ping every connection from the mac os terminal. The firewall is also turned off on this mac... I've never ran into this before and it's happenning to two freshly factory rest mac minis running Sequoia 15.1. Like I said, it's not happening to my M2 air or the intel iMac on Sonoma. With being able to ping devices from it, the firewall being off, and all the other testing I did, this is what lead me to post here.

[Lukeb873]

So by turning off the local network connection and re enabling it, companion seems to be happy. I'm going to role the computer back to 14.7 and see what happens. We'll likely disable all updates on this computer to not go to 15 until something is figured out on Apples end.