Hi, I'm running a remote controlled broadcasting linux (Debian Buster) machine. I have an python/gunicorn app that interacts with YouTube and OBS to control broadcasting.
It's been working like a charm for 6 months. When the python script needs to start broadcasting it will "os.system("startx obs") " and control OBS over websockets.
This sunday, it stopped working (no changes, no nothing "Known" mid morning broadcast worked, mid afternoon didn't)
After debugging the problem I finded out that, when I start OBS from the python script, websockets pluging won't start listening on port 4444. If I manually start obs, then it worked.
I cant find OBS logs when I start it from python so I cannot debug any further.
Any help/idea.
By the way, I've setup a brand new Pc with the whole system and I've ended up in the same situation. Desperate. Next live event will be thursday evening :(
Thx on advance for your help!!
EDIT: I'm using OBS 22 (the one installed with apt install obs-studio) and webesockets 4.5.1
It's been working like a charm for 6 months. When the python script needs to start broadcasting it will "os.system("startx obs") " and control OBS over websockets.
This sunday, it stopped working (no changes, no nothing "Known" mid morning broadcast worked, mid afternoon didn't)
After debugging the problem I finded out that, when I start OBS from the python script, websockets pluging won't start listening on port 4444. If I manually start obs, then it worked.
I cant find OBS logs when I start it from python so I cannot debug any further.
Any help/idea.
By the way, I've setup a brand new Pc with the whole system and I've ended up in the same situation. Desperate. Next live event will be thursday evening :(
Thx on advance for your help!!
EDIT: I'm using OBS 22 (the one installed with apt install obs-studio) and webesockets 4.5.1