Server Troubleshooting - FlagBrew/local-gpss GitHub Wiki

This means that the program ran into a problem and didn't successfully start, to be able to grab the error log, please make sure to run the program within a terminal/command prompt window, this allows us to assist you should you be unable to resolve your issue through the troubleshooting page.

Newer versions of Local GPSS should show you what error occurred and shouldn't automatically exit, you can then copy the error log if getting assistance.

Make sure that your JSON isn't malformed, use https://jsonlint.com/ to validate the JSON, and correct any issues within it.

appsettings.json is no longer used, and instead a new config file local-gpss.json will be created after going through the setup wizard the first time you run it.

Ports from 1-1024 are restricted ports on Unix systems (Linux and Mac), and will likely need to be run using the root account, this is STRONGLY not recommended, and you should just select a higher port (you probably tried to use port 80 but that's a restricted port).

I'm not certain if this occurs on Windows as well, but just to be on the safe side, always use a higher port than the first 1024.

The setup wizard will help you avoid this by checking to see if the port you choose can actually be used. It will also be checked each time it starts up and will prompt you to change it if it cannot be used.

Make sure the appsettings.json's format is similar to this

{
  "Logging": {
    "LogLevel": {
      "Default": "Information",
      "Microsoft.AspNetCore": "Warning"
    }
  },
  "AllowedHosts": "*",
  "Kestrel": {
    "Endpoints": {
      "Http": {
        "Url": "http://0.0.0.0:8080"
      }
    }
  }
}

(Do not put Kestrel under logging, it must be on the root level)

If the format is correct, then make sure it is located within the same directory that you are running the server from, in Linux/Mac, you can use pwd to print your current working directory, if the printed directory does not contain the appsettings.json, then the server will not be able to see it and will use defaults, on windows you can use cd without any arguments and it should show you your current directory.

appsettings.json is no longer used, the setup wizard will help you avoid this issue.

There's a possibility your firewall may be blocking the port, please use Google and look for how to add an allow rule to the firewall based on what your operating system is.

It's also possible you may have entered the wrong IP into PKSM, please verify it before trying to mess with your firewall.

Program will now bind to an actual IP address instead of all IP addresses (0.0.0.0), but the firewall information remains the same

Also, your 3DS and Server must be on the same network, if they are not (say you have two different routers), then it will not work. You're welcome to try however, but good luck with the double NAT

Essentially you want your network to be like this:

However, you can also get away with this:

But it won't work if your network is like this:

If this is your setup, then it won't work without special routing set-up, which is more advanced and complicated than the average user likely is used to and willing to put up with.

When you're configuring the URLs, make sure you use HTTP and not HTTPS. This means both in the appsettings.json and in PKSM.

This will no longer occur.

If you didn't follow the guide, please do so and then come back here if it still doesn't work.

This could be caused by a few things, but the simplest explanation is likely that the gpss.db isn't in the directory that you're running the server from (see the section above about appsettings.json).

Make sure that it is named gpss.db and not something like gpss.db.1 or gpss.db (1)

The setup wizard will have prompted you if you didn't have a gpss.db the first time you ran a version newer than 1.0.0. If you chose not to download it at the time, you will need to follow the manual instructions on the guide

If you weren't able to resolve your issue, please join the FlagBrew discord and ask for assistance in the #gpss-general channel.