Error -1 Troubleshooting

[lynxaradev]

Select Topic Area

Question

Body

So, to illustrate the issue:
We (me and my friend) played through the whole split Fiction on it's release using Sunshine. No issues (Mar 2025). Recently we tried to play together again, on latest version of the Sunshine a newer game. My friend is kicked after 1 to 2 minutes of gameplay with an error "-1". I am hosting, he is using Moonlight client, he is kicked. I checked, my ports are open, I opened in my router settings and on my ISP side, same configuration as we had with Split Fiction.

I think we tried everything obvious (port forwarding, no VPNs on or Cloudflare WARP), I tried turning on UPnP. Nothing helps, same issue.

Maybe someone can help in the right direction

[yudin-s]

-1 after one or two minutes sounds more like an established stream/session being dropped than a basic port-forwarding failure.

Since the connection starts, I would narrow it down in this order:

1. Test host and client on the same LAN, no internet path, no relay, no VPN. If LAN is stable, the problem is likely routing/NAT/ISP path rather than Sunshine itself.
2. In Sunshine, open the logs around the disconnect and look for whether the session ends because of video encoder failure, control timeout, RTSP/UDP timeout, or client disconnect.
3. In Moonlight, temporarily lower bitrate and resolution and force a simpler codec, for example H.264 instead of HEVC/AV1 if those are enabled.
4. Make sure Sunshine and Moonlight are both current, then test one older Sunshine version if the issue started only after upgrading.
5. If the newer game uses a different display mode, test with desktop streaming or a lightweight game for 5-10 minutes. That separates game capture/encoder issues from network issues.

UPnP and port forwarding usually matter before the stream starts. A timed kick after the stream starts is more likely logs + codec/bitrate + network stability.

The Sunshine log lines at the disconnect point are probably the fastest way to tell whether this is encoder, timeout, client, or network path.

[lynxaradev]

1. LAN works it seems like. Tested on mobile via the same wifi. when I used mobile on the mobile network (so it is out of my LAN) - it crashed with code -1 too after some time
2. [2026-06-11 15:08:40.283]: Warning: WSASendMsg() failed: 10022. Spam of this error happens before disconnect
3. Didn't help
4. Latest, have no idea which version was before, several updates ago
5. The game is from 2013

[yudin-s]

That new WSASendMsg() failed: 10022 line is a much better lead than the generic -1.

Since LAN works but mobile network drops, I would treat this as the UDP send path first. There is a recent Sunshine issue with the same Windows socket error where the reporter worked around it by adding this to sunshine.conf and restarting Sunshine:

udp_batch_send=0

That does not prove it is the same root cause, but it is a quick A/B test for exactly this log signature.

If that stops the WSASendMsg spam but the WAN session still drops, the next useful evidence is the Moonlight client log/stat line around the disconnect, especially packet loss, Waiting for IDR frame, or control-stream errors, plus the Sunshine lines immediately after the first WSASendMsg. I would also test IPv4-only vs IPv6-only if your WAN path uses IPv6, because this error often points at socket send parameters/address-family behavior rather than the 2013 game itself.