Ahstval

New Member
I tried:
-Deleting the plugin and checking file integrity for fresh install
-Navigating to the config file and changing settings manually, even changing it to read-only
-Disabling authentication altogether
NOTHING fixed it. Every time I restart obs, the settings are reset, the port is set back to 4455 while I wanted it at 4959, the password generated is always the same but when I enter it in Twitchat or Streamerbot it doesn't work.
Generating new credentials works, I manage to connect. But the instant I close obs and open it again, it's all reset.
Also, this only seems to happen with Ws 5.x+, 4.9 works flawlessly but has limitations, and arguably puts additional load on obs.
Please help, I'm desperate
 

Ahstval

New Member
UP:
I noticed there's this connection that's always on by default, even when nothing else is running.
1724263170529.png
 

Ahstval

New Member
Up:
It now seems to sometimes stay fixed on OBS restart, but reset on reboot. I am unable to determine a pattern yet, though it doesn't look like it's following any.
I have no idea what is going on please help
 

Suslik V

Active Member
 

Vubar

New Member
I'm having the same problem. Here're the relevant parts of my last few logs:
08:35:27.379: [obs-websocket] [obs_module_load] you can haz websockets (Version: 5.5.2 | RPC Version: 1)
08:35:27.379: [obs-websocket] [obs_module_load] Qt version (compile-time): 6.6.3 | Qt version (run-time): 6.6.3
08:35:27.379: [obs-websocket] [obs_module_load] Linked ASIO Version: 103002
08:35:27.380: [obs-websocket] [MigrateGlobalConfigData] Some configurations have been migrated from old config
08:35:27.380: [obs-websocket] [Config::Load] (FirstLoad) Not generating new password since one is already configured.
08:35:27.414: [obs-websocket] [obs_module_load] Module loaded.
08:35:28.064: [obs-websocket] [obs_module_post_load] WebSocket server is enabled, starting...
08:35:28.064: [obs-websocket] [WebSocketServer::Start] Not locked to IPv4 bindings
08:35:28.064: [obs-websocket] [WebSocketServer::ServerRunner] IO thread started.
08:35:28.084: [obs-websocket] [WebSocketServer::Start] Server started successfully on port XXXX. Possible connect address: XXX.XXX.XXX.XXX

08:35:30.630: [obs-websocket] [WebSocketServer::onOpen] New WebSocket client has connected from [::ffff:127.0.0.1]:50738

08:35:43.283: [obs-websocket] [WebSocketServer::onOpen] New WebSocket client has connected from [::ffff:127.0.0.1]:50918

08:35:43.317: [obs-websocket] [WebSocketServer::onClose] WebSocket client `[::ffff:127.0.0.1]:50918` has disconnected with code `4009` and reason: Your payload's data is missing an `authentication` string, however authentication is required.
 

Ahstval

New Member
I'm still unable to fix it.. I tried contacting a dev on discord and they read through some of the logs I tried getting but to no avail..
Hopefully OBS 31 fixes it
 

MrGhost

Member
I'm still unable to fix it.. I tried contacting a dev on discord and they read through some of the logs I tried getting but to no avail..
Hopefully OBS 31 fixes it
Yeah I use 2 OBS out of two folders and each has its own websocket password. I didn't try to change the port but that will definitely get you a new instance.
Also wen I recently installed Wndows anew, the OBS was different websocket with the new install (of course it was) but when I imported my OBS folder from APPDATA, I got my old password right back.
 

Ahstval

New Member
I tried something different here, I went to the plugin's config file and changed the port and password there, and then started OBS.
When I checked the websocket settings there, it was reset again, so I'm thinking it's loading settings from somewhere on startup, perhaps the global.ini which I have also included, since it's also modified after each startup
 

Attachments

  • global.ini.txt
    4.3 KB · Views: 35
  • 2024-11-30 21-09-21.txt
    335.9 KB · Views: 35

Ahstval

New Member
Yeah I use 2 OBS out of two folders and each has its own websocket password. I didn't try to change the port but that will definitely get you a new instance.
Also wen I recently installed Wndows anew, the OBS was different websocket with the new install (of course it was) but when I imported my OBS folder from APPDATA, I got my old password right back.
Okay so, I edited the global.ini file with my own password and port, then restarted OBS It DID load from the global.ini, except the password was a little different and characters were added, and when I closed obs and check global.ini again, it, too, had been reset.
What you suggested seems logical, there may be a second OBS folder downloaded somewhere on my pc, I'll post an update if I find anything
 

Ahstval

New Member
I found a solution!!!! Though not quite that, more like a way to ignore the problem and just forget about it
I created a shortcut (right click, new, shortcut) and added this path "C:\Program Files\obs-studio\bin\64bit\obs64.exe"
I followed it up with the following flags --websocket_password=[YourPassword] --websocket_port=[YourPort]
And now anytime I want to run OBS I open this shortcut, and it overrides any configurations with the ones I've set
so the path looks like this:
"C:\Program Files\obs-studio\bin\64bit\obs64.exe" --websocket_password=[YourPassword] --websocket_port=[YourPort]

I hope this helps!
 

Ahstval

New Member
False happiness, it didn't fix anything, it SHOWS that the settings have been applied but they're not, if I start obs and streamer.bot nothing is synchronized.
Here's what I did instead:
I used a macro with an elgato streamdeck (which tracked my mouse and keyboard prior) to automatically and quickly rewrite every important setting
It sucks but at least this one works for real
 

DaveReed

New Member
Got the exact same problem, every time I start OBS the websocket password changes and it is absolutely not possible for me to fix this than to deactivate the authentification.
 
Last edited:

Ahstval

New Member
Got the exact same problem, every time I start OBS the websocket password changes and it is absolutely not possible for me to fix this than to deactivate the authentification.
For me even the deactivated authentication reactivates itself automatically on restart..
 
Top