Warpinator discovers devices using the mDNS protocol (Multicast DNS), which broadcasts a signal over your local network. If any layer blocks this broadcast — a firewall, a VPN, a wrong network interface, or a router setting — your devices become invisible to each other.
Must Read: Warpinator Stuck on Connecting – How To Solve?
The most common reasons are:
- Firewall blocking UDP/TCP port 42000 or mDNS port 5353
- Group code mismatch between devices
- Devices are on different subnets or networks
- A VPN is interfering with local discovery
- Wrong network interface selected in settings
- Flatpak version missing network permissions
- Windows set to “Public” network profile
Start from the top and work your way down. Most users fix the issue within the first three steps.
Important: Every time you change a setting during troubleshooting, fully restart Warpinator on all devices. Changes do not take effect live.
Quick Checklist (Try These First)
- Warpinator is installed and open on both devices simultaneously
- Both devices are connected to the same Wi-Fi network or router
- Both devices have the same Group Code in Settings
- No VPN is active on either device
- Firewall is not blocking Warpinator
- Both devices can ping each other on the local network
Fix 1 — Confirm Both Devices Are on the Same Network
Warpinator only works within the same local subnet. If one device is on Wi-Fi and the other is on wired Ethernet, your router may be isolating them from each other. Check that both IP addresses start with the same three numbers — for example, both showing 192.168.1.x.
On Linux/Windows: Check the IP shown in the bottom-right corner of the Warpinator window. On Android, go to Manual Connect to see the detected IP.
If your router has “AP isolation” or “client isolation” enabled, devices on Wi-Fi cannot talk to each other — disable it in your router settings.
Quick test: Connect both devices to a mobile hotspot instead of your home router. If Warpinator finds devices on the hotspot, your router configuration is the problem — not Warpinator itself.
Fix 2 — Check the Group Code Matches
The Group Code acts as a shared password for discovery. Devices with a different code will be silently ignored — you will not see any error message.
Go to Settings → Group Code on every device. Make sure the code is character-for-character identical, including capitalization. The default code is Warpinator — if you changed it on one device but forgot to update the others, that is almost certainly your problem.
After changing the Group Code, restart Warpinator on all devices.
Fix 3 — Allow Warpinator Through the Firewall
Firewalls are the most common cause of Warpinator not finding devices. Warpinator needs two ports open on both devices:
| Port | Protocol | Purpose |
|---|---|---|
| 42000 | TCP + UDP | File transfers and device authentication |
| 5353 | UDP | mDNS discovery (finding devices) |
On Linux (UFW firewall)
Open a terminal and run:
sudo ufw allow 42000/tcp sudo ufw allow 42000/udp
Known Linux bug: Some versions of Warpinator on Linux only add a firewall exception for TCP, not UDP. You must add the UDP rule manually as shown above, or device discovery will fail silently.
On Windows (Windows Defender Firewall)
- Open Windows Defender Firewall with Advanced Security
- Click Inbound Rules → New Rule
- Select Port, then enter 42000
- Allow the connection for Domain and Private networks
- Repeat for both TCP and UDP protocols
Alternatively, temporarily disable the firewall on both devices and test. If Warpinator finds devices with the firewall off, the firewall is the cause.
Fix 4 — Disable VPN Temporarily
If you have a VPN running on either device, it will almost certainly prevent Warpinator from discovering other devices. VPNs route traffic through a remote server, bypassing your local network entirely.
Disable the VPN on both devices and try again. If that fixes it, you can either use Warpinator without the VPN, or configure Warpinator to use the correct local network interface (see Fix 5).
Note: Tools like Tailscale do not support multicast traffic, so mDNS auto-discovery will not work through them. You will need to add devices manually by IP address (see Fix 9).
Fix 5 — Set the Correct Network Interface
If your computer has multiple network adapters (Wi-Fi + Ethernet, or a VPN adapter), Warpinator might select the wrong one and show an IP address that does not match your local network.
Check the IP shown in the bottom-right corner of the Warpinator window. It should start with your router’s subnet — typically 192.168.x.x or 10.0.x.x. If it shows a different address, go to Settings → Network Interface and select the correct adapter manually.
Fix 6 — Fix Flatpak Network Permissions (Linux)
If you installed Warpinator via Flatpak, the sandbox may be restricting its access to the local network. Run this command to grant the necessary network permissions:
flatpak override org.x.Warpinator --socket=network --share=network
After running the command, restart Warpinator. To run Warpinator in debug mode via Flatpak:
flatpak run org.x.Warpinator -d
Fix 7 — Windows Network Profile Fix
When Windows connects to a network for the first time, it may label it as “Public.” This profile applies strict firewall rules that block local device discovery — including Warpinator’s mDNS broadcasts.
To fix this:
- Open Settings → Network & Internet → Wi-Fi (or Ethernet)
- Click on your connected network
- Change Network profile type from Public to Private
Restart Warpinator after making this change.
Fix 8 — Android-Specific Fixes
Android introduces additional complications due to battery optimization and background app restrictions.
Check App Permissions
Go to Settings → Apps → Warpinator → Permissions and ensure that network and Wi-Fi access is granted.
Disable Battery Optimization
Go to Settings → Battery → Battery Optimization, find Warpinator, and set it to Don’t optimize. Aggressive battery saving can kill Warpinator’s background processes and prevent it from broadcasting on the network.
Keep the Screen On During Transfers
Some Android phones block multicast traffic when the screen is off. Keep the display active while using Warpinator.
Minimum version requirement: The Linux version of Warpinator must be at least version 1.0.9 to be compatible with the Android app. If you are running an older version on Linux, update it first.
Fix 9 — Add Device Manually by IP Address
If your network blocks multicast traffic and auto-discovery keeps failing, you can still use Warpinator by adding devices manually.
Find the other device’s local IP address — it appears in the bottom-right corner of the Warpinator window on Linux/Windows, or in the Manual Connect screen on Android. Then, in Warpinator, look for the Manual Connect or Add Device by IP option and enter that address. The devices will connect directly without needing mDNS discovery.
Fix 10 — Update Warpinator
Older versions of Warpinator sometimes have discovery bugs that have since been fixed. Make sure all devices are running the latest version.
On Linux (package manager)
sudo apt update && sudo apt upgrade warpinator
On Linux (Flatpak)
flatpak update org.x.Warpinator
On Android
Update via F-Droid or download the latest APK from the official GitHub repository.
On Windows
Download the latest release from the official source and reinstall.
Summary — All Fixes at a Glance
| # | Fix | Platform | Likelihood |
|---|---|---|---|
| 1 | Confirm same network / subnet | All | Very High |
| 2 | Match Group Code on all devices | All | Very High |
| 3 | Open firewall ports 42000 (TCP + UDP) | Linux / Windows | High |
| 4 | Disable VPN | All | High |
| 5 | Select correct network interface | Linux / Windows | Medium |
| 6 | Grant Flatpak network permissions | Linux (Flatpak) | Medium |
| 7 | Switch Windows network profile to Private | Windows | Medium |
| 8 | Disable Android battery optimization | Android | Medium |
| 9 | Add device manually by IP address | All | Always works |
| 10 | Update Warpinator to latest version | All | Low–Medium |
Still not working? Enable debug logging to find the exact cause. On Linux, run warpinator -d from the terminal. On Windows, enable “Write debug log to file” in Settings. On Android, tap Save log from the three-dot menu. The log will show exactly where the discovery process is failing.