Not connected to Websocket api without Proxy

[bob]

When I click “Live Lorawan Frame”, i got am error massage say “not connected to websocket”. Below is logs:

root@ecs-de1e-0001:~# journalctl -u lora-app-server -f -n 50
-- Logs begin at Sun 2018-12-23 09:15:01 CST. --
Mar 16 06:04:09 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:04:09+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"GET / HTTP/1.1\\r\\nHost: 11\"""
Mar 16 06:04:37 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:04:37+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams failed to receive the preface from client: EOF""
Mar 16 06:04:37 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:04:37+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"GET / HTTP/1.1\\r\\nHost: 11\"""
Mar 16 06:04:40 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:04:40+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"GET / HTTP/1.1\\r\\nHost: 11\"""
Mar 16 06:04:41 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:04:41+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"GET / HTTP/1.1\\r\\nHost: 11\"""
Mar 16 06:04:42 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:04:42+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"GET / HTTP/1.1\\r\\nHost: 11\"""
Mar 16 06:04:42 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:04:42+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"GET / HTTP/1.1\\r\\nHost: 11\"""
Mar 16 06:04:42 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:04:42+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"GET / HTTP/1.1\\r\\nHost: 11\"""
Mar 16 06:04:42 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:04:42+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"GET / HTTP/1.1\\r\\nHost: 11\"""
Mar 16 06:04:43 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:04:43+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"GET / HTTP/1.1\\r\\nHost: 11\"""
Mar 16 06:04:43 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:04:43+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"GET / HTTP/1.1\\r\\nHost: 11\"""
Mar 16 06:05:04 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:05:04+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams failed to receive the preface from client: EOF""
Mar 16 06:05:44 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:05:44+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams received bogus greeting from client: \"GET / HTTP/1.1\\r\\nHost: 11\"""
Mar 16 06:05:55 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:05:55+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams failed to receive the preface from client: EOF""
Mar 16 06:05:55 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:05:55+08:00" level=warning msg="grpc: Server.Serve failed to create ServerTransport: connection error: desc = "transport: http2Server.HandleStreams failed to receive the preface from client: EOF""
Mar 16 06:09:31 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:31+08:00" level=info msg="finished streaming call with code Canceled" error="rpc error: code = Canceled desc = context canceled" grpc.code=Canceled grpc.method=StreamFrameLogs grpc.service=api.GatewayService grpc.start_time="2019-03-16T06:02:13+08:00" grpc.time_ms=438314.66 peer.address="[::1]:57206" span.kind=server system=grpc
Mar 16 06:09:32 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:32+08:00" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=List grpc.service=api.ApplicationService grpc.start_time="2019-03-16T06:09:32+08:00" grpc.time_ms=3.5 peer.address="[::1]:57190" span.kind=server system=grpc
Mar 16 06:09:37 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:37+08:00" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=Get grpc.service=api.ApplicationService grpc.start_time="2019-03-16T06:09:37+08:00" grpc.time_ms=2.377 peer.address="[::1]:57190" span.kind=server system=grpc
Mar 16 06:09:37 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:37+08:00" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=List grpc.service=api.DeviceService grpc.start_time="2019-03-16T06:09:37+08:00" grpc.time_ms=4.68 peer.address="[::1]:57196" span.kind=server system=grpc
Mar 16 06:09:43 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:43+08:00" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=Get grpc.service=api.ApplicationService grpc.start_time="2019-03-16T06:09:43+08:00" grpc.time_ms=2.349 peer.address="[::1]:57190" span.kind=server system=grpc
Mar 16 06:09:44 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:44+08:00" level=info msg="finished client unary call" grpc.code=OK grpc.method=GetDevice grpc.service=ns.NetworkServerService grpc.time_ms=0.772 span.kind=client system=grpc
Mar 16 06:09:44 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:44+08:00" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=Get grpc.service=api.DeviceService grpc.start_time="2019-03-16T06:09:44+08:00" grpc.time_ms=3.694 peer.address="[::1]:57196" span.kind=server system=grpc
Mar 16 06:09:44 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:44+08:00" level=info msg="finished client unary call" grpc.code=OK grpc.method=GetDeviceProfile grpc.service=ns.NetworkServerService grpc.time_ms=0.964 span.kind=client system=grpc
Mar 16 06:09:44 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:44+08:00" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=Get grpc.service=api.DeviceProfileService grpc.start_time="2019-03-16T06:09:44+08:00" grpc.time_ms=3.525 peer.address="[::1]:57212" span.kind=server system=grpc
Mar 16 06:09:44 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:44+08:00" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=List grpc.service=api.DeviceProfileService grpc.start_time="2019-03-16T06:09:44+08:00" grpc.time_ms=4.089 peer.address="[::1]:57212" span.kind=server system=grpc
Mar 16 06:09:45 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:45+08:00" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=List grpc.service=api.DeviceProfileService grpc.start_time="2019-03-16T06:09:45+08:00" grpc.time_ms=3.95 peer.address="[::1]:57212" span.kind=server system=grpc
Mar 16 06:09:45 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:45+08:00" level=info msg="finished client unary call" grpc.code=OK grpc.method=GetDeviceProfile grpc.service=ns.NetworkServerService grpc.time_ms=0.803 span.kind=client system=grpc
Mar 16 06:09:45 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:45+08:00" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=Get grpc.service=api.DeviceProfileService grpc.start_time="2019-03-16T06:09:45+08:00" grpc.time_ms=3.375 peer.address="[::1]:57212" span.kind=server system=grpc
Mar 16 06:09:50 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:50+08:00" level=info msg="finished client streaming call" grpc.code=OK grpc.method=StreamFrameLogsForDevice grpc.service=ns.NetworkServerService grpc.time_ms=0.024 span.kind=client system=grpc
Mar 16 06:09:53 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:53+08:00" level=info msg="finished streaming call with code Canceled" error="rpc error: code = Canceled desc = context canceled" grpc.code=Canceled grpc.method=StreamFrameLogs grpc.service=api.DeviceService grpc.start_time="2019-03-16T06:09:50+08:00" grpc.time_ms=3564.991 peer.address="[::1]:57196" span.kind=server system=grpc
Mar 16 06:09:59 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:59+08:00" level=info msg="finished streaming call with code OK" grpc.code=OK grpc.method=StreamEventLogs grpc.service=api.DeviceService grpc.start_time="2019-03-16T06:09:53+08:00" grpc.time_ms=5364.512 peer.address="[::1]:57196" span.kind=server system=grpc
Mar 16 06:09:59 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:09:59+08:00" level=info msg="finished client streaming call" grpc.code=OK grpc.method=StreamFrameLogsForDevice grpc.service=ns.NetworkServerService grpc.time_ms=0.021 span.kind=client system=grpc
Mar 16 06:10:01 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:10:01+08:00" level=info msg="finished streaming call with code Canceled" error="rpc error: code = Canceled desc = context canceled" grpc.code=Canceled grpc.method=StreamFrameLogs grpc.service=api.DeviceService grpc.start_time="2019-03-16T06:09:59+08:00" grpc.time_ms=1589.056 peer.address="[::1]:57196" span.kind=server system=grpc
Mar 16 06:10:02 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:10:02+08:00" level=info msg="finished streaming call with code OK" grpc.code=OK grpc.method=StreamEventLogs grpc.service=api.DeviceService grpc.start_time="2019-03-16T06:10:01+08:00" grpc.time_ms=1342.11 peer.address="[::1]:57196" span.kind=server system=grpc
Mar 16 06:10:03 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:10:03+08:00" level=info msg="finished client streaming call" grpc.code=OK grpc.method=StreamFrameLogsForDevice grpc.service=ns.NetworkServerService grpc.time_ms=0.026 span.kind=client system=grpc
Mar 16 06:10:04 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:10:04+08:00" level=info msg="finished streaming call with code Canceled" error="rpc error: code = Canceled desc = context canceled" grpc.code=Canceled grpc.method=StreamFrameLogs grpc.service=api.DeviceService grpc.start_time="2019-03-16T06:10:03+08:00" grpc.time_ms=1209.11 peer.address="[::1]:57196" span.kind=server system=grpc
Mar 16 06:21:17 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:21:17+08:00" level=info msg="finished streaming call with code OK" grpc.code=OK grpc.method=StreamEventLogs grpc.service=api.DeviceService grpc.start_time="2019-03-16T06:10:04+08:00" grpc.time_ms=672841.56 peer.address="[::1]:57196" span.kind=server system=grpc
Mar 16 06:21:17 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:21:17+08:00" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=List grpc.service=api.GatewayService grpc.start_time="2019-03-16T06:21:17+08:00" grpc.time_ms=2.801 peer.address="[::1]:57206" span.kind=server system=grpc
Mar 16 06:21:18 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:21:18+08:00" level=info msg="finished client unary call" grpc.code=OK grpc.method=GetGatewayStats grpc.service=ns.NetworkServerService grpc.time_ms=1.426 span.kind=client system=grpc
Mar 16 06:21:18 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:21:18+08:00" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=GetStats grpc.service=api.GatewayService grpc.start_time="2019-03-16T06:21:18+08:00" grpc.time_ms=4.122 peer.address="[::1]:57206" span.kind=server system=grpc
Mar 16 06:21:18 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:21:18+08:00" level=info msg="finished client unary call" grpc.code=OK grpc.method=GetGatewayStats grpc.service=ns.NetworkServerService grpc.time_ms=1.276 span.kind=client system=grpc
Mar 16 06:21:18 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:21:18+08:00" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=GetStats grpc.service=api.GatewayService grpc.start_time="2019-03-16T06:21:18+08:00" grpc.time_ms=3.736 peer.address="[::1]:57206" span.kind=server system=grpc
Mar 16 06:21:20 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:21:20+08:00" level=info msg="finished client unary call" grpc.code=OK grpc.method=GetGateway grpc.service=ns.NetworkServerService grpc.time_ms=1.107 span.kind=client system=grpc
Mar 16 06:21:20 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:21:20+08:00" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=Get grpc.service=api.GatewayService grpc.start_time="2019-03-16T06:21:20+08:00" grpc.time_ms=3.951 peer.address="[::1]:57206" span.kind=server system=grpc
Mar 16 06:21:21 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:21:21+08:00" level=info msg="finished client unary call" grpc.code=OK grpc.method=GetGatewayStats grpc.service=ns.NetworkServerService grpc.time_ms=1.438 span.kind=client system=grpc
Mar 16 06:21:21 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:21:21+08:00" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=GetStats grpc.service=api.GatewayService grpc.start_time="2019-03-16T06:21:21+08:00" grpc.time_ms=4.218 peer.address="[::1]:57206" span.kind=server system=grpc
Mar 16 06:21:25 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:21:25+08:00" level=info msg="finished client streaming call" grpc.code=OK grpc.method=StreamFrameLogsForGateway grpc.service=ns.NetworkServerService grpc.time_ms=0.022 span.kind=client system=grpc
Mar 16 06:21:30 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:21:30+08:00" level=info msg="finished streaming call with code Canceled" error="rpc error: code = Canceled desc = context canceled" grpc.code=Canceled grpc.method=StreamFrameLogs grpc.service=api.GatewayService grpc.start_time="2019-03-16T06:21:25+08:00" grpc.time_ms=5348.395 peer.address="[::1]:57206" span.kind=server system=grpc
Mar 16 06:21:30 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:21:30+08:00" level=info msg="finished unary call with code NotFound" error="rpc error: code = NotFound desc = object does not exist" grpc.code=NotFound grpc.method=GetLastPing grpc.service=api.GatewayService grpc.start_time="2019-03-16T06:21:30+08:00" grpc.time_ms=2.473 peer.address="[::1]:57206" span.kind=server system=grpc
Mar 16 06:21:31 ecs-de1e-0001 lora-app-server[25717]: time="2019-03-16T06:21:31+08:00" level=info msg="finished client streaming call" grpc.code=OK grpc.method=StreamFrameLogsForGateway grpc.service=ns.NetworkServerService grpc.time_ms=0.023 span.kind=client system=grpc

After 2 servers running for a while, I found some errors through “systemctl status loraserver” and “lora-app-server”

[BondarchukAO]

show yours lora-app-server.toml and loraserver.toml

[bob]

LoraServer.toml:

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


# PostgreSQL settings.
#
# Please note that PostgreSQL 9.5+ is required.
[postgresql]
# PostgreSQL dsn (e.g.: postgres://user:password@hostname/database?sslmode=disable).
#
# Besides using an URL (e.g. 'postgres://user:password@hostname/database?sslmode=disable')
# it is also possible to use the following format:
# 'user=loraserver dbname=loraserver sslmode=disable'.
#
# The following connection parameters are supported:
#
# * dbname - The name of the database to connect to
# * user - The user to sign in as
# * password - The user's password
#
# Besides using an URL (e.g. 'postgres://user:password@hostname/database?sslmode=disable')
# it is also possible to use the following format:
# 'user=loraserver dbname=loraserver sslmode=disable'.
#
# The following connection parameters are supported:
#
# * dbname - The name of the database to connect to
# * user - The user to sign in as
# * password - The user's password
# * host - The host to connect to. Values that start with / are for unix domain sockets. (default is localhost)
# * port - The port to bind to. (default is 5432)
# * sslmode - Whether or not to use SSL (default is require, this is not the default for libpq)
# * fallback_application_name - An application_name to fall back to if one isn't provided.
# * connect_timeout - Maximum wait for connection, in seconds. Zero or not specified means wait indefinitely.
# * sslcert - Cert file location. The file must contain PEM encoded data.
# * sslkey - Key file location. The file must contain PEM encoded data.
# * sslrootcert - The location of the root certificate file. The file must contain PEM encoded data.
#
# Valid values for sslmode are:
#
# * disable - No SSL
# * require - Always SSL (skip verification)
# * verify-ca - Always SSL (verify that the certificate presented by the server was signed by a trusted CA)
# * verify-full - Always SSL (verify that the certification presented by the server was signed by a trusted CA and the server host name matches the one in the certificate)
# * dsn="postgres://localhost/loraserver_ns?sslmode=disable"
dsn="postgres://loraserver_ns:dbpassword@localhost/loraserver_ns?sslmode=disable"
# Automatically apply database migrations.
#
# It is possible to apply the database-migrations by hand
# (see https://github.com/brocaar/loraserver/tree/master/migrations)
# or let LoRa App Server migrate to the latest state automatically, by using
# this setting. Make sure that you always make a backup when upgrading Lora
# App Server and / or applying migrations.
automigrate=true


# Redis settings
#
# Please note that Redis 2.6.0+ is required.
[redis]
# Redis url (e.g. redis://user:password@hostname/0)
#
# For more information about the Redis URL format, see:
# https://www.iana.org/assignments/uri-schemes/prov/redis
url="redis://localhost:6379"

# Max idle connections in the pool.
max_idle=10

# Idle timeout.
#
# Close connections after remaining idle for this duration. If the value
# is zero, then idle connections are not closed. You should set
# the timeout to a value less than the server's timeout.
idle_timeout="5m0s"
# Network-server settings.
[network_server]
# Network identifier (NetID, 3 bytes) encoded as HEX (e.g. 010203)
net_id="000000"

# Time to wait for uplink de-duplication.
#
# This is the time that LoRa Server will wait for other gateways to receive
# the same uplink frame. Valid units are 'ms' or 's'.
# Please note that this value has influence on the uplink / downlink
# roundtrip time. Setting this value too high means LoRa Server will be
# unable to respond to the device within its receive-window.
deduplication_delay="200ms"

# Device session expiration.
#
# The TTL value defines the time after which a device-session expires
# after no activity. Valid units are 'ms', 's', 'm', 'h'. Note that these
# values can be combined, e.g. '24h30m15s'.
device_session_ttl="744h0m0s"

# Get downlink data delay.
#
# This is the time that LoRa Server waits between forwarding data to the
# application-server and reading data from the queue. A higher value
# means that the application-server has more time to schedule a downlink
# queue item which can be processed within the same uplink / downlink
# transaction.
# Please note that this value has influence on the uplink / downlink
# roundtrip time. Setting this value too high means LoRa Server will be
# unable to respond to the device within its receive-window.
get_downlink_data_delay="100ms"


  # LoRaWAN regional band configuration.
  #
# Note that you might want to consult the LoRaWAN Regional Parameters
  # specification for valid values that apply to your region.
  # See: https://www.lora-alliance.org/lorawan-for-developers
  [network_server.band]
  # LoRaWAN band to use.
  #
  # Valid values are:
  # * AS_923
  # * AU_915_928
  # * CN_470_510
  # * CN_779_787
  # * EU_433
  # * EU_863_870
  # * IN_865_867
  # * KR_920_923
  # * RU_864_870
  # * US_902_928
  name="CN_470_510"
 # Enforce 400ms dwell time
  #
  # Some band configurations define the max payload size for both dwell-time
  # limitation enabled as disabled (e.g. AS 923). In this case the
  # dwell time setting must be set to enforce the max payload size
  # given the dwell-time limitation. For band configuration where the dwell-time is
  # always enforced, setting this flag is not required.
  dwell_time_400ms=false

  # Enforce repeater compatibility
  #
  # Most band configurations define the max payload size for both an optional
  # repeater encapsulation layer as for setups where a repeater will never
  # be used. The latter case increases the max payload size for some data-rates.
  # In case a repeater might used, set this flag to true.
  repeater_compatible=false
# LoRaWAN network related settings.
  [network_server.network_settings]
  # Installation margin (dB) used by the ADR engine.
  #
  # A higher number means that the network-server will keep more margin,
  # resulting in a lower data-rate but decreasing the chance that the
  # device gets disconnected because it is unable to reach one of the
  # surrounded gateways.
  installation_margin=10

  # RX window (Class-A).
  #
  # Set this to:
  # 0: RX1, fallback to RX2 (on RX1 scheduling error)
  # 1: RX1 only
  # 2: RX2 only
  rx_window=0
# Class A RX1 delay
  #
  # 0=1sec, 1=1sec, ... 15=15sec. A higher value means LoRa Server has more
  # time to respond to the device as the delay between the uplink and the
  # first receive-window will be increased.
  rx1_delay=1

  # RX1 data-rate offset
  #
  # Please consult the LoRaWAN Regional Parameters specification for valid
  # options of the configured network_server.band.name.
  rx1_dr_offset=0

  # RX2 data-rate
  #
  # When set to -1, the default RX2 data-rate will be used for the configured
  # LoRaWAN band.
# Please consult the LoRaWAN Regional Parameters specification for valid
  # options of the configured network_server.band.name.
  rx2_dr=-1

  # RX2 frequency
  #
  # When set to -1, the default RX2 frequency will be used.
  #
  # Please consult the LoRaWAN Regional Parameters specification for valid
  # options of the configured network_server.band.name.
  rx2_frequency=-1

  # Downlink TX Power (dBm)
  #
  # When set to -1, the downlink TX Power from the configured band will
  # be used.
  #
  #
  # Please consult the LoRaWAN Regional Parameters and local regulations
  # for valid and legal options. Note that the configured TX Power must be
  # supported by your gateway(s).
  downlink_tx_power=-1

  # Disable mac-commands
  #
  # When set, uplink mac-commands are ignored and the network-server will not
  # send mac-commands to the devices. This is intended for testing only.
  disable_mac_commands=false

  # Disable ADR
  #
  # When set, this globally disables ADR.
  disable_adr=false

  # Enable only a given sub-set of channels
  #
  # Use this when ony a sub-set of the by default enabled channels are being
  # used. For example when only using the first 8 channels of the US band.
  # Note: when left blank, all channels will be enabled.
  #
  # Example:
  # enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]
  enabled_uplink_channels=[]


  # Extra channel configuration.
  #
  # Use this for LoRaWAN regions where it is possible to extend the by default
  # available channels with additional channels (e.g. the EU band).
  # The first 5 channels will be configured as part of the OTAA join-response
  # (using the CFList field).
  # The other channels (or channel / data-rate changes) will be (re)configured
  # using the NewChannelReq mac-command.
  #
# Example:
  # [[network_server.network_settings.extra_channels]]
  # frequency=867100000
  # min_dr=0
  # max_dr=5

  # [[network_server.network_settings.extra_channels]]
  # frequency=867300000
  # min_dr=0
  # max_dr=5

  # [[network_server.network_settings.extra_channels]]
  # frequency=867500000
  # min_dr=0
  # max_dr=5

  # [[network_server.network_settings.extra_channels]]
  # frequency=867700000
  # min_dr=0
  # max_dr=5

  # [[network_server.network_settings.extra_channels]]
  # frequency=867900000
  # min_dr=0
  # max_dr=5


  # Class B settings
  [network_server.network_settings.class_b]
  # Ping-slot data-rate.
  ping_slot_dr=0

  # Ping-slot frequency (Hz)
  #
  # Set this to 0 to use the default frequency plan for the configured region
  # (which could be frequency hopping).
  ping_slot_frequency=0


  # Rejoin-request settings
  #
  # When enabled, LoRa Server will request the device to send a rejoin-request
  # every time when one of the 2 conditions below is met (frame count or time).
  [network_server.network_settings.rejoin_request]
  # Request device to periodically send rejoin-requests
  enabled=false

  # The device must send a rejoin-request type 0 at least every 2^(max_count_n + 4)
  # uplink messages. Valid values are 0 to 15.
  max_count_n=0

  # The device must send a rejoin-request type 0 at least every 2^(max_time_n + 10)
  # seconds. Valid values are 0 to 15.
  #
  # 0  = roughly 17 minutes
  # 15 = about 1 year
  max_time_n=0


  # Scheduler settings
  #
  # These settings affect the multicast, Class-B and Class-C downlink queue
  # scheduler.
  [network_server.scheduler]
  # Scheduler interval
  #
  # The interval in which the downlink scheduler for multicast, Class-B and
  # Class-C runs.
  scheduler_interval="1s"

    # Class-C settings.
    [network_server.scheduler.class_c]
    # Downlink lock duration
    #
    # Contains the duration to lock the downlink Class-C transmissions
    # after a preceeding downlink tx (per device).
    downlink_lock_duration="2s"


  # Network-server API
  #
  # This is the network-server API that is used by LoRa App Server or other
  # custom components interacting with LoRa Server.
  [network_server.api]
  # ip:port to bind the api server
  bind="0.0.0.0:8000"

  # ca certificate used by the api server (optional)
  ca_cert=""
 # tls certificate used by the api server (optional)
  tls_cert=""

  # tls key used by the api server (optional)
  tls_key=""


  # Gateway statistics settings.
  [network_server.gateway.stats]
  # Create non-existing gateways on receiving of stats
  #
  # When set to true, LoRa Server will create the gateway when it receives
  # statistics for a gateway that does not yet exist.
  create_gateway_on_stats=true

  # Aggregation timezone
  #
  # This timezone is used for correctly aggregating the statistics (for example
  # 'Europe/Amsterdam').
  # To get the list of supported timezones by your PostgreSQL database,
  # execute the following SQL query:
  #   select * from pg_timezone_names;
  # When left blank, the default timezone of your database will be used.
  timezone=""

  # Aggregation intervals to use for aggregating the gateway stats
  #
  # Valid options: second, minute, hour, day, week, month, quarter, year.
  # When left empty, no statistics will be stored in the database.
  # Note, LoRa App Server expects at least "minute", "day", "hour"!
  aggregation_intervals=["minute", "hour", "day"]


  # Backend defines the gateway backend settings.
  #
  # The gateway backend handles the communication with the gateway(s) part of
 # the LoRaWAN network.
  [network_server.gateway.backend]
    # Backend
    #
    # This defines the backend to use for the communication with the gateways.
    # Use the section name of one of the following gateway backends.
    # E.g. "mqtt" or "gcp_pub_sub".
    type="mqtt"


    # MQTT gateway backend settings.
    #
    # This is the backend communicating with the LoRa gateways over a MQTT broker.
    [network_server.gateway.backend.mqtt]
    # MQTT topic templates for the different MQTT topics.
    #
    # The meaning of these topics are documented at:
    # https://www.loraserver.io/lora-gateway-bridge/use/data/
   #
    # The default values match the default expected configuration of the
    # LoRa Gateway Bridge MQTT backend. Therefore only change these values when
    # absolutely needed.
    # Use "{{ .MAC }}" as an substitution for the LoRa gateway MAC.
    uplink_topic_template="gateway/+/rx"
    downlink_topic_template="gateway/{{ .MAC }}/tx"
    stats_topic_template="gateway/+/stats"
    ack_topic_template="gateway/+/ack"
    config_topic_template="gateway/{{ .MAC }}/config"

    # MQTT server (e.g. scheme://host:port where scheme is tcp, ssl or ws)
    server="tcp://localhost:1883"

    # Connect with the given username (optional)
    username=""

    # Connect with the given password (optional)
password=""

    # Quality of service level
    #
    # 0: at most once
    # 1: at least once
    # 2: exactly once
    #
    # Note: an increase of this value will decrease the performance.
    # For more information: https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels
    qos=0

    # Clean session
    #
    # Set the "clean session" flag in the connect message when this client
    # connects to an MQTT broker. By setting this flag you are indicating
    # that no messages saved by the broker for this client should be delivered.
    clean_session=true
    # Client ID
    #
    # Set the client id to be used by this client when connecting to the MQTT
    # broker. A client id must be no longer than 23 characters. When left blank,
    # a random id will be generated. This requires clean_session=true.
    client_id=""

    # CA certificate file (optional)
    #
    # Use this when setting up a secure connection (when server uses ssl://...)
    # but the certificate used by the server is not trusted by any CA certificate
    # on the server (e.g. when self generated).
    ca_cert=""

    # TLS certificate file (optional)
    tls_cert=""
  # TLS key file (optional)
    tls_key=""


    # Google Cloud Pub/Sub backend.
    #
    # Use this backend when the LoRa Gateway Bridge is configured to connect
    # to the Google Cloud IoT Core MQTT broker (which integrates with Pub/Sub).
    [network_server.gateway.backend.gcp_pub_sub]
    # Path to the IAM service-account credentials file.
    #
    # Note: this service-account must have the following Pub/Sub roles:
    #  * Pub/Sub Editor
    credentials_file=""

    # Google Cloud project id.
    project_id=""
   # Uplink Pub/Sub topic name (to which Cloud IoT Core publishes).
    uplink_topic_name=""

    # Downlink Pub/Sub topic name (for publishing downlink frames).
    downlink_topic_name=""

    # Uplink retention duration.
    #
    # The retention duration that LoRa Server will set on the uplink subscription.
    uplink_retention_duration="24h0m0s"


  # Geolocation settings.
  #
  # When set, LoRa Server will use the configured geolocation server to
  # resolve the location of the devices.
  [geolocation_server]
  # Server.
 # The hostname:ip of the geolocation service (optional).
  server=""

  # CA certificate used by the API client (optional).
  ca_cert=""

  # TLS certificate used by the API client (optional).
  tls_cert=""

  # TLS key used by the API client (optional).
  tls_key=""


# Default join-server settings.
[join_server.default]
# hostname:port of the default join-server
#
# This API is provided by LoRa App Server.
server="http://localhost:8003"

# ca certificate used by the default join-server client (optional)
ca_cert=""

# tls certificate used by the default join-server client (optional)
tls_cert=""

# tls key used by the default join-server client (optional)
tls_key=""


# Join-server KEK set.
#
# These KEKs (Key Encryption Keys) are used to decrypt the network related
# session-keys received from the join-server on a (re)join-accept.
# Please refer to the LoRaWAN Backend Interface specification
# 'Key Transport Security' section for more information.
#
# Example (the [[join_server.kek.set]] can be repeated):
# [[join_server.kek.set]]
# # KEK label.
# label="000000"

# # Key Encryption Key.
# kek="01020304050607080102030405060708"


# Network-controller configuration.
[network_controller]
# hostname:port of the network-controller api server (optional)
server=""

# ca certificate used by the network-controller client (optional)
ca_cert=""

# tls certificate used by the network-controller client (optional)
tls_cert=""

# tls key used by the network-controller client (optional)
tls_key=""


----------------------------------------------------------------------------------------------

Lora-app-server.toml

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

# The number of times passwords must be hashed. A higher number is safer as
# an attack takes more time to perform.
password_hash_iterations=100000


# PostgreSQL settings.
#
# Please note that PostgreSQL 9.5+ is required.
[postgresql]
# PostgreSQL dsn (e.g.: postgres://user:password@hostname/database?sslmode=disable).
#
# Besides using an URL (e.g. 'postgres://user:password@hostname/database?sslmode=disable')
# it is also possible to use the following format:
# 'user=loraserver dbname=loraserver sslmode=disable'.
#
# The following connection parameters are supported:
#
# * dbname - The name of the database to connect to
# * user - The user to sign in as
# * password - The user's password
# * host - The host to connect to. Values that start with / are for unix domain sockets. (default is localhost)
# * port - The port to bind to. (default is 5432)
# * sslmode - Whether or not to use SSL (default is require, this is not the default for libpq)
# * fallback_application_name - An application_name to fall back to if one isn't provided.
# * connect_timeout - Maximum wait for connection, in seconds. Zero or not specified means wait indefinitely.
# * sslcert - Cert file location. The file must contain PEM encoded data.
# * sslkey - Key file location. The file must contain PEM encoded data.
# * sslrootcert - The location of the root certificate file. The file must contain PEM encoded data.
#
# Valid values for sslmode are:
#
# * disable - No SSL
# * require - Always SSL (skip verification)
# * verify-ca - Always SSL (verify that the certificate presented by the server was signed by a trusted CA)
# * verify-full - Always SSL (verify that the certification presented by the server was signed by a trusted CA and the server host name matches the one in the certificate)
# dsn="postgres://localhost/loraserver_as?sslmode=disable"
#  dsn="postgres://loraserver_as:dbpassword@localhost/loraserver_as?sslmode=disable"
  dsn="postgres://loraserver_as:dbpassword@localhost/loraserver_as?sslmode=disable"

# Automatically apply database migrations.
#
# It is possible to apply the database-migrations by hand
# (see https://github.com/brocaar/lora-app-server/tree/master/migrations)
# or let LoRa App Server migrate to the latest state automatically, by using
# this setting. Make sure that you always make a backup when upgrading Lora
# App Server and / or applying migrations.
automigrate=true


# Redis settings
#
# Please note that Redis 2.6.0+ is required.
[redis]
# Redis url (e.g. redis://user:password@hostname/0)
#
# For more information about the Redis URL format, see:
# https://www.iana.org/assignments/uri-schemes/prov/redis
url="redis://localhost:6379"

# Max idle connections in the pool.
max_idle=10

# Idle timeout.
## Close connections after remaining idle for this duration. If the value
# is zero, then idle connections are not closed. You should set
# the timeout to a value less than the server's timeout.
idle_timeout="5m0s"


# Application-server settings.
[application_server]
# Application-server identifier.
#
# Random UUID defining the id of the application-server installation (used by
# LoRa Server as routing-profile id).
# For now it is recommended to not change this id.
id="6d5db27e-4ce2-4b2b-b5d7-91f069397978"


  # Integration configures the data integration.
  #
  # This is the data integration which is available for all applications,
  # besides the extra integrations that can be added on a per-application
  # basis.
  [application_server.integration]
  # The integration backend.
  #
  # This defines the backend to use for the data integration. Use the section
  # name of one of the following integration backend.
  # E.g. "mqtt" or "gcp_pub_sub".
  backend="mqtt"


  # MQTT integration backend.
  [application_server.integration.mqtt]
  # MQTT topic templates for the different MQTT topics.
  #
  # The meaning of these topics are documented at:
  # https://www.loraserver.io/lora-app-server/integrate/data/
  # The following substitutions can be used:
  # * "{{ .ApplicationID }}" for the application id.
  # * "{{ .DevEUI }}" for the DevEUI of the device.
  #
  # Note: the downlink_topic_template must contain both the application id and
  # DevEUI substitution!
  uplink_topic_template="application/{{ .ApplicationID }}/device/{{ .DevEUI }}/rx"
  downlink_topic_template="application/{{ .ApplicationID }}/device/{{ .DevEUI }}/tx"
  join_topic_template="application/{{ .ApplicationID }}/device/{{ .DevEUI }}/join"
  ack_topic_template="application/{{ .ApplicationID }}/device/{{ .DevEUI }}/ack"
  error_topic_template="application/{{ .ApplicationID }}/device/{{ .DevEUI }}/error"
  status_topic_template="application/{{ .ApplicationID }}/device/{{ .DevEUI }}/status"
  location_topic_template="application/{{ .ApplicationID }}/device/{{ .DevEUI }}/location"

  # MQTT server (e.g. scheme://host:port where scheme is tcp, ssl or ws)
  server="tcp://localhost:1883"
# Connect with the given username (optional)
  username=""

  # Connect with the given password (optional)
  password=""

  # Quality of service level
  #
  # 0: at most once
  # 1: at least once
  # 2: exactly once
  #
  # Note: an increase of this value will decrease the performance.
  # For more information: https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels
  qos=0

  # Clean session
  # #
  # Set the "clean session" flag in the connect message when this client
  # connects to an MQTT broker. By setting this flag you are indicating
  # that no messages saved by the broker for this client should be delivered.
  clean_session=true

  # Client ID
  #
  # Set the client id to be used by this client when connecting to the MQTT
  # broker. A client id must be no longer than 23 characters. When left blank,
  # a random id will be generated. This requires clean_session=true.
  client_id=""

  # CA certificate file (optional)
  #
  # Use this when setting up a secure connection (when server uses ssl://...)
  # but the certificate used by the server is not trusted by any CA certificate
  # on the server (e.g. when self generated).
  ca_cert=""

  # TLS certificate file (optional)
  tls_cert=""

  # TLS key file (optional)
  tls_key=""


  # Google Cloud Pub/Sub backend.
  [application_server.integration.gcp_pub_sub]
  # Path to the IAM service-account credentials file.
  #
  # Note: this service-account must have the following Pub/Sub roles:
  #  * Pub/Sub Editor
  credentials_file=""

  # Google Cloud project id.
  project_id=""
  # Pub/Sub topic name.
  topic_name=""


  # Settings for the "internal api"
  #
  # This is the API used by LoRa Server to communicate with LoRa App Server
  # and should not be exposed to the end-user.
  [application_server.api]
  # ip:port to bind the api server
  bind="0.0.0.0:8001"

  # ca certificate used by the api server (optional)
  ca_cert=""

  # tls certificate used by the api server (optional)
  tls_cert=""
 # tls key used by the api server (optional)
  tls_key=""

  # Public ip:port of the application-server API.
  # 
  # This is used by LoRa Server to connect to LoRa App Server. When running
  # LoRa App Server on a different host than LoRa Server, make sure to set
  # this to the host:ip on which LoRa Server can reach LoRa App Server.
  # The port must be equal to the port configured by the 'bind' flag
  # above.
  public_host="localhost:8001"


  # Settings for the "external api"
  #
  # This is the API and web-interface exposed to the end-user.
  [application_server.external_api]
 # ip:port to bind the (user facing) http server to (web-interface and REST / gRPC api)
  bind="0.0.0.0:8080"

  # http server TLS certificate (optional)
  tls_cert=""

  # http server TLS key (optional)
  tls_key=""

  # JWT secret used for api authentication / authorization
  # You could generate this by executing 'openssl rand -base64 32' for example
  jwt_secret="verysecret"

  # when set, existing users can't be re-assigned (to avoid exposure of all users to an organization admin)"
  disable_assign_existing_users=false


# Join-server configuration.
#
# LoRa App Server implements a (subset) of the join-api specified by the
# LoRaWAN Backend Interfaces specification. This API is used by LoRa Server
# to handle join-requests.
[join_server]
# ip:port to bind the join-server api interface to
bind="0.0.0.0:8003"

# CA certificate (optional).
#
# When set, the server requires a client-certificate and will validate this
# certificate on incoming requests.
ca_cert=""

# TLS server-certificate (optional).
#
# Set this to enable TLS.
tls_cert=""

# TLS server-certificate key (optional).
#
# Set this to enable TLS.
tls_key=""


# Key Encryption Key (KEK) configuration.
#
# The KEK meganism is used to encrypt the session-keys sent from the
# join-server to the network-server.
#
# The LoRa App Server join-server will use the NetID of the requesting
# network-server as the KEK label. When no such label exists in the set,
# the session-keys will be sent unencrypted (which can be fine for
# private networks).
#
# Please refer to the LoRaWAN Backend Interface specification
# 'Key Transport Security' section for more information.
[join_server.kek]

  # Application-server KEK label.
  #
  # This defines the KEK label used to encrypt the AppSKey (note that the
  # AppSKey is signaled to the NS and on the first received uplink from the
  # NS to the AS).
  #
  # When left blank, the AppSKey will be sent unencrypted (which can be fine
  # for private networks).
  as_kek_label=""

  # KEK set.
  #
  # Example (the [[join_server.kek.set]] can be repeated):
  # [[join_server.kek.set]]
 # # KEK label.
  # label="000000"

  # # Key Encryption Key.
  # kek="01020304050607080102030405060708"

[BondarchukAO]

@bob

server=“http://localhost:8003”

everything looks good, did you add loraeaserver in network servers (web interface):

[brocaar]

Please format your message the next time

` ` `
content in here
` ` `

(without the spaces between the ```)

[bob]

I did by http://localhost:8000, correct? Or I need server IP address to replace localhost?

What do you mean by above http://localhost:8003? Something wrong?

[BondarchukAO]

Correct, but without http://