Connection Errors

This page is specifically for troubleshooting connection problems with sys-botbase and SysBot.NET / LiveHeX. USB-Botbase errors should refer to this page instead.

Ensure that your program version matches the game version first. For example, trying to use an earlier version of SysBot.NET on any major game patch will fail. Trying to follow this guide with a program that is for a different version of the game is a waste of your time.

SysBot.NET

• I instantly get a crash every time I try to connect or start a bot.
• I get an error about SysBot.Base.SwitchSocketAsync.Read(Byte[] buffer).
• I get an error about System.Net.Sockets.Socket.Connect(IPAddress[] addresses, Int32 port).**
• A bot's lamp turns green and immediately disconnects with one of the above problems.

LiveHeX

• Clicking "Connect" causes the program to freeze.
• Clicking "Connect" gives an error about a connection attempt failing.
  
• Clicking "Connect" throws no errors but the boxes are blank.

Step-by-Step

The vast majority of connection issues are one of these problems. Please read through each step carefully and make sure you have set everything up correctly.

1. Ping your Switch's IP.

This is a quick way to check if your computer is able to communicate with your Switch.
Open Command Prompt. You can press Ctrl + R and then and enter "cmd", or right-click the Start Menu and select "Command Prompt."

If the ping succeeds, you will see a reply with times. If the ping fails, you will see "Destination host unreachable."

A failure can indicate any of the following problems is present, but generally means you are not on the same network or your IP is incorrect. If you succeed but still cannot connect, this may be a problem with a dual-band router or you are connecting to some other device on your network that is not your Switch.

2. Check that you have sys-botbase installed.

Look in your SD card at the atmosphere/contents/430000000000000B directory.

The current release of sys-botbase should have an exefs.nsp that is 94 kb in size. If you do not see this, ensure that you have installed the latest sys-botbase correctly. You should download the zip file and extract everything inside it to the root of your SD card (where you see atmosphere, bootloader, and Nintendo folders). Make sure you restart your Switch afterwards.

3. Check that your HOME button on the left joycon blinks blue as Wi-Fi establishes.

Dock your joycons and wait while the Switch is turning on. Wait until Wi-Fi connects, and watch for the button to turn blue. If it doesn't turn blue, go back to the previous step; you do not have sys-botbase installed correctly.

4. Check that your IP is correct.

Open the Homebrew Menu and press the Y button.

The IP underlined in red is the one you should be using when you create a new bot or configure LiveHex. Ignore the port you see here.

5. Check that your port is 6000.

Both programs should have 6000 as a default. This should not be changed. This is what it should look like in LiveHex.

This is what it should look like in SysBot.NET.

6. Ensure that you have restarted your Switch and router.

This is a catch-all for fixing numerous issues, such as improper sys-botbase installation or occasional network hiccups after the programs have been working fine.

7. SWSH: Ensure that you are online in-game or have native LAN enabled.

The recommended way to run both of these programs is to connect online with Y-Comm. If you do not have NSO, you may go into the Settings and hold L + R + Left Stick (press) to enable native LAN for offline bots. You can also install ldn_mitm to allow for a connection at any time, but keep in mind that this submodule frequently has errors due to being out-of-date.

8. Check if your router is dual-banded.

Both your Switch and computer need to be on the same band. Look up how to check and change this on your router if you are unsure: CLICK. If they are on the same band but it does not work, try switching both to the other band.

9. Remove all cheats, game mods, and extra sys-modules.

Go into atmosphere/contents and remove everything from contents except for 430000000000000B (sys-botbase) and 4200000000000010 (ldn_mitm, SWSH only) and try again. You can back up the extra folders to your PC and slowly replace them once you get it working.

This is not necessarily a connection error, but can fool users into believing they have one by shifting RAM. Things that might cause this include layeredfs mods, EdiZon cheats, Tesla overlays, and CaptureSight usage. You can temporarily disable all Atmosphère cheats by holding L while booting the game.

I have read all of this, but nothing is working.

• If these still don't resolve your issue, come to the ALM Discord linked on the repository's main page. Please show the results of the above steps when asking for help. This means show photos/screenshots, not only tell us in text that everything is right.
• You can unlock access to the help channels by reading very carefully. Asking for help in any channel is a confirmation that you know what is on this page. Please state what you have already tried from the Wiki.
  • Ask any SysBot.NET questions in #sysbot-net-help. The unlock word for SysBot.NET is on the bottom of the SysBot.NET Troubleshooting page.
  • Ask any PKHeX-Plugins questions in #alm-livehex-help. The unlock word for ALM/LiveHeX is on the bottom of the PKHeX-Plugins FAQ & Troubleshooting page.
• If the problem is that your Wi-fi connection is unstable, consider USB-Botbase.