Common network errors

Due to some ISPs hijacking requests made by Slinky, you may see errors such as:

• TypeError: Failed to fetch
• tls: first record does not look like a TLS handshake
• slinky error 9003
• SSL Connect Error
• or other update/network related errors

A few common solutions for these types of errors are listed below.

Try switching to Cloudflare DNS

You can do so by downloading the Cloudflare app or by following their instructions (you may need to scroll down a bit) on how to configure it in Windows directly.

Try using a VPN

If you have any VPN software installed, try to connect to it before running Slinky. If Slinky launches successfully, you can disconnect from the VPN afterwards.

If neither of the above work

Try running the following command in Windows command prompt (cmd):

curl -v http://api.slinky.gg/

If you see a line that look like this:

Location: https://example.com/warn.html?url=http://slinky.gg/&token=...

then that confirms that something is still hijacking your connection (ISP, router firewall).

In this case, please send us an email including the output from the previous command.