When it won't connect.
FL Connect links the two computers directly, so no video ever touches our servers. That is what keeps it fast and private. It also means your network has to let that direct connection through. When it doesn't, this is almost always why.
It is almost always a VPN.
FL Connect is peer to peer. Your computers find each other and talk directly. A lot of VPNs quietly block or reroute that kind of traffic, so the direct link never forms. You either can't connect at all, or you connect but never see any video.
If you or the person you are working with has a VPN running, start there. It is the single most common reason a session fails.
We keep video and audio off our servers on purpose. It is what holds the latency down and keeps your session yours. Switching the VPN off is the real fix, not a workaround.
Turn it off
Switch the VPN off completely, then reconnect. It is the quickest thing to try and it clears this up most of the time.
Or split-tunnel it
If you need the VPN running, add FL Connect to its split tunnelling list so its traffic skips the VPN.
Check both ends
One person on a P2P-blocking VPN is enough to break the link, so both of you should look, not just the host.
No sound in the session
If your DAW plays through an audio interface, the sound leaves through the interface driver and never passes the part of Windows that FL Connect can record. So there is nothing to send. The fix is one step: put the FL Connect Bridge plugin on your master channel in the DAW. Play something and the level meter in FL Connect should move. If it does not, check the plugin is on the master and not on a single track. The Bridge plugin needs Pro. On Free, set your DAW's output to your normal Windows playback device while you stream, so the sound passes through Windows on its way out.
It keeps crashing
Send us the log and we will read it for you. The folder is %AppData%\FL-Connect\logs on Windows and ~/Library/Logs/FL-Connect on a Mac. Drop the files further down this page, single files or a zip, and you get back what went wrong and what to do about it. You need to be signed in, because we check your account and recent sessions at the same time.
Firewall or strict NAT
FL Connect has to open a direct path between both machines. A tight firewall, a school or office network, or a router with strict NAT can block it. Allow FL Connect through Windows Firewall when it asks, and try a normal home network if you are on a managed one.
Run the connection test
Open Settings, Connection, Run test. It checks whether your network will let a direct link through. If it comes back restricted or blocked, your network or a VPN is the cause. Paste the result into Discord and we will read it with you.
Antivirus ate the installer
FL Connect is a small independent build and is not code signed yet, so some antivirus tools flag it just in case rather than for anything real. If the installer disappears or will not open, restore it from quarantine and allow it.
Black screen or frozen video
Usually a graphics driver or encoder hiccup. Update your GPU drivers and rejoin the session. If it sticks around, send the session log from Settings, Report a bug. It attaches everything we need on its own.
Send us the log, get an answer.
Open the folder below, drop everything in it here, and we will read it for you and tell you what to do. It takes single files or a zip.
%AppData%\FL-Connect\logsPaste it into the Explorer address bar and press Enter.
~/Library/Logs/FL-ConnectIn Finder press Cmd+Shift+G, paste it and press Enter.