What the message means
LyveFlow serves your OBS overlays on one port. When LyveFlow starts and Windows will not give it that port, LyveFlow moves the overlays to another port and says so. A banner on the Overlays screen reads like this:
"This computer refused port 4126, so the overlays are on port 5126 for now. LyveFlow tries 4126 again each time it starts."
The Overlays item in the sidebar gets a warning mark too.
LyveFlow tries a short list of other ports first, then any free port. The move lasts until LyveFlow closes. Each time it starts, it asks for your port again, so your addresses work again as soon as Windows leaves the port free.
While the overlays are moved, Browser Sources you added with your port show nothing. If you use OBS control, LyveFlow points them at the new port for now, and back again after. To stay on the new port instead, click Keep port on the banner, then copy each overlay's new address into OBS. Overlays in OBS has more.
If the banner says the port "is in use by another program" instead, another program on your PC holds that port. This guide is about Windows refusing it.
Why it happens
Each time Windows starts, it sets aside blocks of ports for features such as Hyper-V and WSL. It takes them from a range it calls the dynamic port range.
On a standard Windows setup that range starts at 49152. LyveFlow's overlay port and the ports it tries next all sit below it, so Windows never takes them. On some PCs the range starts much lower, such as at 1024. Then the blocks can land anywhere, including on the port your overlays use.
Why a restart helps, and why it comes back
Windows picks new blocks every time it starts. After a restart, the old port is often free again.
The next restart can take it again, or take the port LyveFlow moved to. A restart does not change the range, so the problem keeps coming back until the range is fixed.
Check your PC
Open a terminal and run:
netsh int ipv4 show dynamicport tcp
If the start port is 49152, your range is the standard one. If it is lower, such as 1024, the fix below is for you.
To see the blocks Windows has set aside right now, run:
netsh interface ipv4 show excludedportrange protocol=tcp
The fix
This puts the dynamic port range back to the Windows standard. You only do it once.
- Right-click the Start button and choose Terminal (Admin). On Windows 10, choose Windows PowerShell (Admin).
- Click Yes when Windows asks for permission.
- Run these four commands, one at a time:
netsh int ipv4 set dynamicport tcp start=49152 num=16384
netsh int ipv6 set dynamicport tcp start=49152 num=16384
net stop winnat
net start winnat
- Close LyveFlow and open it again.
If net stop winnat fails, restart Windows instead of running the last two commands.
After the fix
Step 4 is all it takes. LyveFlow asks for your port each time it starts, so once Windows leaves it free, your Browser Sources work again with nothing to copy.
To use another port for good instead:
- Click Overlays in the sidebar, then Advanced.
- Type the port in Port.
- Click Move the server.
While the banner is showing, its Pick a port button opens the same place. Then copy each overlay's new address into its Browser Source in OBS. See Overlays in OBS.