Router unplugged and plugged back in, suddenly OBS is the only program that doesn't work anymore

[superspyro3000]

For the past month, my internet has been working pretty well! However, the walls in my house are being painted this week, and everything needed to be unplugged, including the router.

Ever since that thing was unplugged, everything has been running normally except for OBS! I had a stream last a few hours but then it just kept disconnecting. Right now it doesn't work. I get around 200kb/s, then 0, and it fluctuates between that until it disconnects. And the most frustrating part is the internet works fine for everything else! It's just OBS that has this problem. I ran a speedtest, and it's giving me the same numbers as always.

I am connect via an ethernet powerline adapter since I am too far away from the router. I don't want to believe any of my hardware is broken because everything has been working just fine before today! I posted a log, and all I got out of it was it telling me 66% of the frames dropped. I'm at a loss.

 

[superspyro3000]

Just a quick update. I am troubleshooting the internet, and so far, I moved to another streaming program, which is working with no issues. So it's just OBS that is refusing to work.

 

[AaronD]

I am connect via an ethernet powerline adapter since I am too far away from the router.

We had a landline phone version of that when I was growing up. It was almost unusable. Maybe things have improved since then, but I'm always skeptical of using power lines for anything other than bulk power.

 

[Lawrence_SoCal]

Basic TCP/UDP networking means that OBS Studio is basically unaware of your router, in a default setup. If your setup isn't 'normal' default, then it is incumbent on you to explain anything non-standard

Simply unplugging rebooting a router shouldn't make any difference
- presuming any specific router config wasn't lost/corrupted/reverted in the process
-[after typing this whole response, another thought occurred to me] did your router or PC config have anything IP address specific, and in reconnecting your LAN, did your OBS PC get a new IP address? and that is causing unexpected impacts?
- I get using PowerLine, but I sure don't like it. Fortunately, I'm in a position to run Ethernet cable(s) wherever I want (and have, to every room, etc)
- one possibility is the the PowerLine devices when auto-pairing after paint job, chose a setting subject to more interference? or maybe when other electrical cords put back, things not put back EXACTLY as they were before, and what was ok, now isn't.
Though, with other streaming software supposedly working, that wouldn't minimize the likelihood of this (but even then, I wouldn't rule out that PowerLine connection isn't operating same as before. And unless you did real-time monitoring and bandwidth throughput metric collection before and after, you can't know either.

Have you followed the powerline device mfg troubleshooting step to ensure to adequate (to optimal) performance on the powerline link?​

Asa test only, have you run a temporary ethernet cable from OBS PC to router? move the PC if need be...this is just a test​

- any new network traffic/devices? have you checked your router for any unexpected new traffic? why do I ask? 1 basic operation environment awareness, and 2 some (ex smart/IoT) devices may have updated firmware/changed behavior with power cycle...

Just out of curiosity, are you using that PoS streamelements plugin? if yes, I'd recommend creating a portable OBS Studio install, no plugins at all, and test from that. Assuming a plain OBS Studio setup works, then either an issue with a plugin, or a combination of the plugin and something changed on your LAN (presumably)... could be coincidental and be WAN, but you'd need to eliminate all LAN possibilities first, as they are far more common/likely.

Once you done that basic network troubleshooting, and if you haven't found a culprit, then follow the instructions in the pinned post in this forum regarding posting your OBS log when asking for assistance. I'd advise running your Log(s) through the automated OBS Studio Log Analyzer first, ignoring any warning about running OBS as Admin. and address any major issues. Then if still having an issue, posting you log here (from a Recording/Streaming session).
Side question - a 2000kbps bitrate is pretty low. was that you attempt to get something to work, or is that all the upload bandwidth you had available to use previously?

Anyway, I'm in a bit of a mental fog, due to illness (so apologies in advance), hopefully one of these ideas with spark some research assisting in resolution (or at least elimination of certain potential causes)