1. Check the basics
Open agniwar in a current browser on both devices and check that the connection indicator says Connected. Keep both pages open. Turn off VPNs only if your security policy permits, and confirm both devices can reach the signaling service.
2. Check discovery
Both devices must reach the same signaling service. Local development discovers directly attached private IPv4 subnets; public deployments group by the public IP seen by the server. IPv6-only networks, separate subnets, proxies and VPNs may prevent discovery. There is no code fallback.
3. Check network and storage
Guest networks, firewalls and client isolation can prevent peer connections. A relay, if configured by the operator, may provide a fallback. Make sure the receiver has enough free browser storage. If private file storage is unavailable, the browser uses IndexedDB segments; available quota and download memory still limit file size.
4. Restart after interruption
Keep both devices awake, retry with a smaller file, and check that completed files reached your chosen folder or Downloads. Interrupted transfers cannot yet resume. If the problem persists, record browser versions and the error message without sharing private file contents.
Separate discovery from transfer
If the page says Reconnecting, first check the signaling service, the allowed website origin and firewall access. A Connected label means that browser can reach signaling; it does not prove that another browser is in the same discovery scope or that a WebRTC path is available.
If a device appears but the transfer fails, check the receiver’s approval, free space, browser support and network restrictions. Try one small file while keeping both screens awake. A failure after leaving the page cannot be resumed in this version.