If OBS cannot connect to a streaming server, Windows Firewall may be blocking its network access. The safer first check is to allow OBS Studio through the firewall for the network profile you use, rather than opening a port or turning the firewall off.
You can do this in Windows Security on Windows 10 or Windows 11. If OBS is missing from the list, add its executable from the installation folder; then retry the task that failed and check other security software only if the problem remains.
Recognise a possible firewall block
A firewall is one possible cause when OBS reports that it failed to connect to a server, or says the connection was blocked and asks you to check firewall or antivirus settings. Similar symptoms can come from an incorrect stream key, a server address or service setting, a network interruption, or security software other than Windows Firewall. Treat the message as a clue, not proof that the firewall is responsible.
Notice what is and is not failing. If OBS opens and you can work with scenes and sources but cannot start a stream, investigate connectivity. If only a particular feature, such as capture, is affected, the cause may be different from an outbound streaming connection. OBS Project notes that security products can affect both connectivity and capture behaviour in some cases; its known application conflicts guidance is a useful reference when the firewall exception alone changes nothing.
Before changing Windows settings, check that the computer is online and that the stream destination and credentials are the ones you intend to use. If you recently changed networks, moved OBS, or reinstalled it, mention that in your troubleshooting notes: it can help explain why a formerly working setup now behaves differently. Avoid changing several settings at once, since you will not know which change affected the result.
For a continuous channel, a connection fault can interrupt a long broadcast rather than just a short test. If your stream is built from a looping playlist, keep its playback setup separate from network troubleshooting; the steps for making a YouTube livestream playlist loop continuously address playback, not Windows permission to communicate. First establish whether OBS can connect, then check the content loop independently.
Open Windows Firewall app settings
Open the Windows Security app from the Start menu. Choose Firewall & network protection, then select Allow an app through firewall. The setting opens the list of apps and features that Windows allows to communicate through the firewall.
Select Change settings before editing the list. Windows may ask for administrator approval. If you do not have permission, or the option is unavailable on a work- or school-managed computer, do not try to work around your organisation's controls; contact its IT support process instead. Microsoft explains the firewall and network protection controls in its Windows Security overview.
The wording and layout can vary slightly by Windows release, but the route is the app-allowance screen rather than a port configuration page. Microsoft’s guidance favours allowing an app through the firewall over opening a port manually. An app exception lets Windows permit the app’s required communication when needed, whereas a port rule can leave a particular opening in place until you remove it. See Microsoft's explanation of the risks of allowing apps through Windows Firewall before making a change if you want more detail on that trade-off.
Select the network profile in use
The app list has separate checkboxes for network profiles, commonly Private and Public. Choose based on the network to which this computer is connected and where you need OBS to work. In Microsoft's terminology, a private network is trusted; a public network is untrusted. A home network you have designated as private is different from an airport, hotel, or café network that Windows treats as public.
Use the narrowest profile that meets your need. If you stream only from a trusted home connection, there may be no reason to enable OBS for public networks. If you need to use OBS on a public network as well, decide whether that is appropriate for the device and network before checking that profile. Do not enable both automatically just because both boxes are visible.
| Profile choice | What it means in Windows | Practical decision |
|---|---|---|
| Private | A network Windows treats as trusted | Consider this for a trusted home network when OBS needs to connect there |
| Public | A network Windows treats as untrusted | Enable only if OBS must communicate on that kind of network and you accept the broader exposure |
The profile currently in use matters. If you are unsure whether your connection is marked private or public, look at the active network in Windows network settings before editing the exception. The purpose is not to label every network correctly in theory; it is to avoid giving OBS permission on profiles where you do not need it. Microsoft warns that turning off the firewall can leave the device more vulnerable, so use the smallest useful allowance rather than disabling protection.
Allow OBS Studio through the firewall
In the allowed apps list, look for OBS Studio. If it is present, tick the box for the profile you selected and leave other profile boxes unchanged unless you have a specific reason to allow OBS there too. Select OK to save the change.
The exception is for OBS communicating through Windows Firewall. It does not verify your stream key, make an incorrect server address correct, or repair an internet connection. After saving, return to OBS and retry the same action that failed. If the error changes, record the new message; if nothing changes, continue through the checks below rather than broadening permissions at random.
For a channel that runs for long periods, you may be troubleshooting an encoder session that is expected to keep sending after you leave the computer. An app allowance does not itself keep OBS running or restart a failed broadcast. If you are comparing approaches for an always-on channel, this guide to running FFmpeg as a background process concerns a different streaming setup; it is not a Windows Firewall fix, but it can help you separate the software-running question from the network-permission question.
Add the OBS executable if it is not listed
If OBS Studio does not appear in the list, use Allow another app on the same settings screen. Choose Browse, navigate to the folder where OBS is installed, select its executable, and add it. The exact folder depends on how and where you installed OBS, so browse to the actual installation rather than assuming a path from someone else's computer.
The executable is the OBS application file, not a shortcut on the desktop and not a video file you are streaming. If you are uncertain which file is correct, use the installed OBS shortcut to locate its target or check the installation folder. OBS Project provides its own download page, which can help you distinguish the OBS application from unrelated files, but the firewall needs the executable already installed on your machine.
Once it has been added, enable only the profile you need and save. If you moved OBS or reinstalled it, check whether an existing entry points to the current installation. The firewall procedure associates the allowance with an app path, so an entry for an older location may not be the one you intend to use. Remove or replace a stale entry only if you can identify it confidently; avoid deleting unrelated allowances.
Do not create a port rule simply because OBS was absent from the list. Adding the app is the intended route for this task, and it keeps the change tied to the program rather than creating a manual opening that you must remember to close later. If the computer is managed, an administrator may need to add or approve the app.
Retry OBS and check the connection
Reopen or return to OBS and repeat the connection attempt under the same conditions as before. If it connects, keep the exception limited to the profile that worked. If the same connection-blocked message appears, confirm that the correct OBS executable was allowed and that the active network matches the selected profile.
Then check the OBS streaming settings that are independent of the firewall: the selected service or destination, server setting where applicable, and stream key. Do not paste a stream key into support posts or screenshots; treat it as a credential. If you recently changed encoder settings and the failure followed that change, investigate that branch separately. For example, the checklist for YouTube RTMP drops after encoder setting changes is relevant when the timing points to an encoder change rather than a firewall edit.
A short controlled retry is more useful than repeatedly changing settings. Note the time, network, exact error, and whether the failure happens before OBS begins sending or after a stream has started. These observations help distinguish a persistent block from a connection that drops later. They also make it easier for an administrator or OBS support community to understand what you already tested.
If the stream connects but later drops, a firewall exception may not address the cause. Network stability, destination-side behaviour, and encoder configuration are separate possibilities. Keep the firewall change in place only if OBS needs it, and do not infer that one successful attempt guarantees uninterrupted operation overnight.
Review other security software if needed
If the Windows exception is correct and OBS still cannot connect, check whether antivirus or another firewall product manages network access. Some security products include their own application controls, so an allowance in Windows Security may not override a separate block. OBS Project's stream connection troubleshooting guide discusses security software as one possible cause and recommends checking whether it is preventing OBS from reaching the service.
If you need to test whether security software is involved, follow the product maker's current instructions and keep any diagnostic change brief. OBS's troubleshooting guidance describes a temporary disablement as a way to test the cause; if the connection succeeds only during that test, restore protection and create an OBS-specific exception in the relevant product. Do not leave security software disabled as the working configuration.
Also check whether a recently moved or updated OBS installation has an exception that refers to an old executable. This is a practical verification, not a guarantee that stale entries explain the fault. If changing a rule is outside your permissions, take the OBS error and the details of the profile you checked to the device administrator rather than trying to bypass policy.
At this point, keep the diagnosis proportionate. You do not need to buy a router, firewall utility, or security product to complete the Windows app-allowance steps. If a separate product is already installed, use its vendor's own documentation for its controls; avoid applying generic instructions that may not match its version or policy.
For creators who would rather not keep a personal computer awake to run a file-based channel, StreamNeo removes that particular burden by turning an uploaded video into a YouTube live stream that can run while your computer is off. It does not change Windows Firewall on the computer, and it is YouTube-only, so it is relevant to a different operating choice rather than a cure for an OBS connection error.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Should I open a port for OBS?
Not as the default fix. Microsoft recommends an allowed-app entry as the safer approach in general, because Windows can allow the app's required communication when needed rather than leaving a manually opened port in place. Start by allowing OBS through the firewall for the profile you use.
Which network profile should I select?
Select the profile that matches the network on which you need OBS to communicate. Private means trusted in Windows' terminology, while public means untrusted; limit the exception to the profile you actually need rather than ticking both by default.
What if Windows asks for an administrator password?
You may not have permission to change firewall settings on that device. On a work- or school-managed computer, ask the organisation's support team to review the OBS allowance instead of trying to get around its policy.
The exception is saved, but OBS still cannot connect. What next?
Verify the current OBS executable and network profile, then check the stream destination, credentials, internet connection, and any separate antivirus or firewall controls. If testing security software briefly indicates that it is involved, restore protection and add a specific OBS exception rather than leaving it off.