Settings, Firewall & Network Debugging
Understand RideStream's fixed HTTP streaming port (9191), configure Windows Firewall for LAN streaming, and debug host connection issues.
HTTP Server Port
RideStream host mode always binds to TCP port 9191. This port is fixed — there is no setting to change it. When hosting starts, RideStream shows "Hosting Stream on port 9191".
If port 9191 is occupied by another service, the host will fail to bind. Make sure nothing else on your PC or phone is listening on TCP 9191 before starting host mode.
Windows Firewall Configuration
When running RideStream on Windows for the first time, Windows Defender Firewall will prompt for network permissions. Ensure both Private Networks and Public Networks checkboxes are enabled.
Two inbound rules matter for LAN streaming:
- TCP port
9191— lets receivers stream media from your PC and poll its state. - UDP port
8082— lets receivers discover the host automatically via broadcast.
To add them manually, run PowerShell as Administrator:
netsh advfirewall firewall add rule name="RideStream Host Server" dir=in action=allow protocol=TCP localport=9191
netsh advfirewall firewall add rule name="RideStream Discovery" dir=in action=allow protocol=UDP localport=8082
Also confirm the Windows network profile is Private with Network discovery enabled — see the Network Discovery guide for the exact Windows 11 steps.