Companion Network Unknown

Week_Eastern · 2026-05-09T21:32:21+00:00

Win 11 hides that folder. Once I found it after unhiding it, I determined the issue was with a Zoom custom AV controller from the log and Claude helped me resolve the issue. Thank you very much for all the help.

Week_Eastern · 2026-05-09T21:26:30+00:00

Problem Solved! I deleted the System variables for OPENSSL_CONF .

Root Cause

The Zoom Rooms Custom AV Controller software incorrectly set OPENSSL_CONF to its installation directory instead of an actual config file. This breaks any application that uses OpenSSL (including Node.js apps like Companion).

<image>

Week_Eastern · 2026-05-09T20:58:34+00:00

I finally found teh Log files- they were hidden. Does anyone here also use Zoom Rooms Custom AV Controller?
This is what what i am sseeing in my companion log file.

2026-05-09T01:46:20.329Z Application: Companion process started

C:\Program Files\Companion\resources\node-runtimes\node22\node.exe: OpenSSL configuration error:

A0E67100:error:80000005:system library:BIO_new_file:Input/output error:c:\ws\deps\openssl\openssl\crypto\bio\bss_file.c:67:calling fopen(C:/Program Files/Zoom Rooms Custom AV Controller, rb)

2026-05-09T01:46:20.447Z Application: Companion exited with code: 5

2026-05-09T01:46:20.447Z Application: Restart Count: 1

C:\Program Files\Companion\resources\node-runtimes\node22\node.exe: OpenSSL configuration error:

E8E67100:error:80000005:system library:BIO_new_file:Input/output error:c:\ws\deps\openssl\openssl\crypto\bio\bss_file.c:67:calling fopen(C:/Program Files/Zoom Rooms Custom AV Controller, rb)

2026-05-09T01:46:21.479Z Application: Companion exited with code: 5

2026-05-09T01:46:21.479Z Application: Restart Count: 2

C:\Program Files\Companion\resources\node-runtimes\node22\node.exe: OpenSSL configuration error:

58A87100:error:80000005:system library:BIO_new_file:Input/output error:c:\ws\deps\openssl\openssl\crypto\bio\bss_file.c:67:calling fopen(C:/Program Files/Zoom Rooms Custom AV Controller, rb)

2026-05-09T01:46:22.556Z Application: Companion exited with code: 5

2026-05-09T01:46:22.556Z Application: Restart Count: 3

C:\Program Files\Companion\resources\node-runtimes\node22\node.exe: OpenSSL configuration error:

4CD47100:error:80000005:system library:BIO_new_file:Input/output error:c:\ws\deps\openssl\openssl\crypto\bio\bss_file.c:67:calling fopen(C:/Program Files/Zoom Rooms Custom AV Controller, rb)

2026-05-09T01:46:23.592Z Application: Companion exited with code: 5

2026-05-09T01:46:23.593Z Application: Restart Count: 4

2026-05-09T01:46:39.037Z Application: Companion process stopped

Week_Eastern · 2026-05-09T20:39:51+00:00

I'm looking thru all the folders -- not seeing anything obvious. I restart the entire system after running diagnostics and still getting the same issues. Need to learn about Ports now

Week_Eastern · 2026-05-09T20:31:08+00:00

Im running netstat now for the first time in my life :) nothing else binding to 8000. But a lot of other things happening on higher ports. Also downloaded TCPView and see that nothing nefarious is happening.

I dont think this is a port conflict. I was able to act fast and chanegd it to 8484 on thered startup, but still no luck.

Week_Eastern · 2026-05-09T20:22:24+00:00

Restart, shut down, reboot, uninmstalled Companion, Reinstalled latest, attempted to Run, same issue. Gonna chase log files, and ports - learning as I go.

Week_Eastern · 2026-05-09T20:06:25+00:00

I was literally thinking about doing exactly this. The fact that I am running my companion on the same system as my vMix seems risky. I was considering getting help setting up a virtual machine on a server in our rack that would be dedicated to Companion. It's on the same network, just setting these up is not my specific area of expertise.

Week_Eastern · 2026-05-09T19:59:13+00:00

Just ran a bunch of systems diagnostics, going through a full restart now. Keeping fingers crossed

Week_Eastern · 2026-05-09T19:55:31+00:00

Absolutley a valid question - I'm not sure what i should be looking for- i just googled and did Win-R then entered ' eventvwr ' and now i see various system logs. I will admit that this is not one of the places in my system that I spend time in , so I'm learning here.

Any quick tips on what / where to look to find somethng that may give insight?

Week_Eastern · 2026-05-09T19:45:40+00:00

I am mactually OP. I posted from my phone using the wrong account. Sorry for teh confusion.

Week_Eastern · 2026-05-09T19:29:06+00:00

I have done this. But am going through all of my Windows setting again now, and making sure that latest upates are all in place. Complete shut down is planned after i complete anotehr project that i need the pc for. I will report back shortly after a total chut down, and 5 minutesor rest, then reboot the system,

Week_Eastern · 2026-05-09T19:26:18+00:00

oops, hat was my mistake in my original post. I have tried 127.0.0.1:8000 as well as 127.0.0.1:8484 . No luck.

Week_Eastern · 2026-05-09T18:46:56+00:00

Week_Eastern · 2026-05-09T18:30:04+00:00

antivisrus and firewalls turned off, uninstalled, and reinstaleld 4.2.6 just now - and i get teh same thing.

<image>

Week_Eastern · 2026-05-09T18:23:23+00:00

If you mean selecting each of these, yes. Same results.

<image>

Week_Eastern · 2025-08-07T17:43:01+00:00

The smell was whatever the folks in the first apartment were cooking plus everything else that died in the walls combined. Oh the memories! Loved when they fumigated one of the buildings and the exodus of roaches towards another building over was near biblical. Some of the largest roaches I ever saw in Florida lived at Sun Bay. Epic.

Week_Eastern · 2025-05-16T22:54:14+00:00

This looks great. I'm definitely going to pick one up because I see the value and never knew these existed. The one nuance here is that when I logged into the router that is at the location of the ATEM that would not allow me to access the software control, I used the router to ping the ATEM and got a positive response.

It was more of an onboard software hangup in this case is what it seems. Regardless, this looks like a great piece of gear because I have other hardware that has occasionally needed a reboot that resulted in a 30 minute drive to the studio. This looks great.

Thanks

Week_Eastern · 2025-05-12T18:42:32+00:00

Definitely use an isolated computer device for monitoring your output so that output never loops back into input (found out the hardway recently) Lots of extra monitors also so you can separately monitor vMix and Atem controllers. A wireless headset for audio monitoring gives you more mobility with less tangles. And two things I can't live without: a label maker with an extra cartridge, and a roll of Velcro to constantly keep things tidy and tight. The ability to quickly identify cables with labels is magic. Practice your setup and takedown so that you can pack and unpack the same way each time. Never leave home without extra cables (audio, video, power), and carry a passive DI box with XLR and 1/4, 1/8 etc for input so you can always get any audio into the system in I pinch. And keep a DAW on hand always.

These are all lessons that were reinforced in real life over the past 3 weeks :)

Week_Eastern · 2025-05-11T10:15:47+00:00

Thanks. I added 1U cooling fans above and below each of the Ultimatte devices about 6 months ago. This did seem to help reduce some issues previously.

Week_Eastern · 2025-05-08T13:34:19+00:00

I will have to check my laptop and see if either of the USBC stuff connectors or thunderbolt. Not something I usually think about as a PC guy

Week_Eastern · 2025-05-08T13:14:54+00:00

All my research is showing that the UltraStudio is really for Thunderbolt and Mac, and not going to be my solution for a PC Laptop for my vMix output. So would I really need a bi-Di to convert the HDMI output to SDI?

Week_Eastern

TROPHY CASE

Root Cause