Note that using a persistent stream key is a bad security approach.
Our Sunday service standard is to schedule live video using a non-persistent key
- the day of the service, we boot up streaming computer 1-2 hours before the service, and download service bulletin
- we log into fb/live/producer, copy stream key into OBS, and test streaming (once confirmed we stop streaming)
- go through Service Bulletin and correct errors, and adjust for visuals (sometimes adjust line width, etc)
- train new folks on OBS and PTZ camera controls during service, and various OBS scenes I've configured
- Then (re-)start stream 15 minutes before schedule start
- We leave the /Live/Producer page up the entire time and monitor comments during livestream (acting as digital usher, and looking for tech comments like lost audio, or what have you)
As such, connecting to FB/live/producer to get a stream key is a non-issue as we go there anyway to monitor livestream
The above works using a dual monitor setup, with keyboard, monitor and mouse up in choir/pipe organ loft, and streaming PC in sound closet with mixer (closet in only large enough for mixer, not a person). we don't have/need a sound booth for our style of worship. I use a single 50ft fiber optic DisplayPort cable to drive both monitors, and a 50ft high quality active USB cable for the keyboard and mouse.
The streaming PC is behind its own router, separate from the rest of the local network. have my own dedicated WiFi in case we want to use a portable device (phone/tablet) using NDI to stream video from outside (ex Palm Sunday procession). The office PCs are all turned off and any office laptops are put in airplane mode during livestream service. Depending on exactly what a device is doing (and most people don't know), a single device can easily interfere with a livestream (and then again dozens of devices, not doing anything with upstream traffic could have no impact [assuming TCP reply traffic manageable]