Streamkit Browser Won't Work in OBS Anymore!!

quillsandspells

New Member
Short version: when I input a browser source from Streamkit or Reactive by FugiTech, nothing happens. Streamkit was working fine for me until Monday and no amount of updates, clearing cashe, uninstalling and reinstalling, or reauthorizing Streamkit and Reactive in Discord has fixed the issue.

Longer version: I stream on Twitch and use Streamkit for my own PNGmodels as well as all my friends. My models were working on Sunday but come Monday, they no longer appear when I or my friends jump into a Discord call. Originally I was getting an error message on Streamkit saying it "couldn't connect to the Discord client, make sure Discord is installed" even as I was actively in a Discord call. I tried testing out Reactive by FugiTech as another option only to be hit with a "The resource is being rate limited" error when I tried to authorize the program in Discord. I stream off two devices: my desktop computer and my laptop and both received the same error. I tried a number of things including uninstalling OBS and Discord and reinstalling, logging out of Discord, making sure everything is updated, clearing cashe, etc. Yesterday though, there was a Discord update and now my laptop can use Streamkit (the models appear in OBS whenever someone enters the Discord call as intended) however the error remains on my desktop computer.

There has to be some sort of issue between connecting to OBS and Discord that I'm not fully understanding. I'm not much of IT support but I was able to look into the log files and noticed that there's an issue with an invalid access token. Is that where this problem is coming from? How do I fix that? Any clue as to why this got resolved on one device and not the other?
 

Attachments

  • 2024-12-20 13-59-32.txt
    140.6 KB · Views: 17

quillsandspells

New Member
It's on the error shown on the log file



Not authenticated.
You need to login in there. Don't know if you have to do it within a browser or in the browser source.
That's the thing, I am logged into Discord which is the only other program involved here. Streamkit is technically an app created by Discord to be used by both Discord and OBS. I've removed Streamkit as an authorized app and reauthorized it but the error still persists. I'm not sure how to authenticate the app in a way that OBS will recognize.
 

PaiSand

Active Member
2024-12-20_191726.jpg


 

quillsandspells

New Member

PaiSand

Active Member
Like I said before, you may need to do it within the browser source itself.

Create a new browser source and point it to https://discord.com/streamkit
Use the interact button you'll see bellow the preview panel.
Now you can interact with the page and login in there. This will set a cookie from the site with your login. If this don't solve the issue, please contact Discord support about the streamkit not working as intended on OBS 31.

You may need to reload the other browser source or restart OBS so it get the cookie with the login.
 

Morinoonna

New Member
Just wanted to confirm/share, I've been struggling with this exact same issue for the past few weeks now and unfortunately logging into Discord via a browser source did not resolve the error either. =( If anyone else happens to have found a fix for this particular issue just yet would definitely love to hear it.
Screenshot 2024-12-29 151625.jpg
 

PaiSand

Active Member
Discord and OBS must be open at the time you do that in a Browser (Chrome, Firefox, Edge)
Check on Discord support for more.
 

BrettUltimus

New Member
Good afternoon.

I've been having the same issue - I think something went wrong on Discord's side with certain users - since this still works for some folks. I'm adding this here so those who are having issues can A) Feel like there isn't something wrong on their side and B) Troubleshoot with users since Discord Support hasn't been super helpful.

Here is everything I've done to show it isn't user error:
  • I've disconnected and reconnected Streamkit through Connected Apps
  • Cache has been cleared on browser side and browser source
  • New browser sources have also been tried.
  • Sometimes Streamkit can't connect (like above) - sometimes it can, shows voice widget in browser (such as chrome), but doesn't show in OBS.
  • Sometimes I get a Rate Limited error.
  • Discord/OBS is the latest version.
  • I've attempted prior versions of OBS, same issue.
  • I'm logged into Discord on Desktop App, Browser (Chrome), and even the OBS Browser Source
  • I've tried multiple computers, same issue.
  • My partner's computer is on the same network, she still has working DiscordKit and Fugi (I only use DiscordKit, and Fugi as a backup if DiscordKit is wonky).
    • My partner's DiscordKit works. When I log into my user name, it does not work
Here is the only time I have been able to get it to work, and even then it only works temporarily for that session before breaking again:
  1. Disconnect Streamkit.
  2. Restart computer
  3. Reconnect Streamkit.
  4. Copy/Paste Voice Widget into Browser itself and start up a new Browser Source in OBS
  5. Nothing shows for a couple of minutes, but then the widget shows both on OBS and Browser Source. If any update is made to Browser Source, if you refresh, or restart OBS, the Browser Source Voice Widget no longer shows in OBS.
I'm currently on round 2 with Discord Support (they thought I needed Fugi's help and dismissed me after talking with me for a couple of weeks - now I'm not even bringing up Fugi as an example, so we can work entirely in Discord Streamkit.)

I'm hoping with holiday break wrapping up that this is something Discord Engineers will recognize happening with a batch of their users. Only time will tell.

Thanks for reading,
Brett
 

Morinoonna

New Member
Thanks for adding to the post, Brett! I've gone through much of the same troubleshooting steps also without success, including full cache/cookie clearing, flushing DNS, ipconfig release & renew, etc.

At this time the only work around I've discovered is that my reactive images appear to work if I copy everything over into StreamLabs, but they still refuse to work within normal OBS. It may at least be a helpful workaround for other too in the interim though.
 
Top