To list all configuration options, start lora-geo-server with the --help flag. This will display:

LoRa Geo Server provides geolocation services for LoRa Server
        > documentation & support:
        > source & copyright information:

  lora-geo-server [flags]
  lora-geo-server [command]

Available Commands:
  configfile        Print the LoRa Geolocation Server configuration file
  help              Help about any command
  test-resolve-tdoa Runs the given resolve TDOA test-suite file (json)
  version           Print the LoRa Geo Server version

  -c, --config string   path to configuration file (optional)
  -h, --help            help for lora-geo-server
      --log-level int   debug=5, info=4, error=2, fatal=1, panic=0 (default 4)

Use "lora-geo-server [command] --help" for more information about a command.

Configuration file

By default lora-geo-server will look in the following order for a configuration file at the following paths when --config is not set:

  • lora-geo-server.toml (current working directory)
  • $HOME/.config/lora-geo-server/lora-geo-server.toml
  • /etc/lora-geo-server/lora-geo-server.toml

To load configuration from a different location, use the --config flag.

To generate a new configuration file lora-geo-server.toml, execute the following command:

lora-geo-server configfile > lora-geo-server.toml

Note that this configuration file will be pre-filled with the current configuration (either loaded from the paths mentioned above, or by using the --config flag). This makes it possible when new fields get added to upgrade your configuration file while preserving your old configuration. Example:

lora-geo-server configfile --config lora-geo-server-old.toml > lora-geo-server-new.toml

Example configuration file:

# Log level
# debug=5, info=4, warning=3, error=2, fatal=1, panic=0

# Geolocation-server configuration.
  # Geolocation API.
  # This is the geolocation API that can be used by LoRa Server.
  # ip:port to bind the api server

  # CA certificate used by the api server (optional)

  # TLS certificate used by the api server (optional)

  # TLS key used by the api server (optional)

  # Geolocation backend configuration.
  # Name.
  # The name of the geolocation backend to use.

  # Collos subscription key.
  # This key can be retrieved after creating a Collos account at:

  # Request timeout.
  # This defines the request timeout when making calls to the Collos API.

Securing the geolocation API

In order to protect the geolocation API (geo_server.api) against unauthorized access and to encrypt all communication, it is advised to use TLS certificates. Once the ca_cert, tls_cert and tls_key are set, the API will enforce client certificate validation on all incoming connections. This means that when configuring this geolocation-server instance in LoRa Server, you must provide the CA and TLS client certificate. See also LoRa Server configuration.

See for a set of scripts to generate such certificates.