"error connecting to server" when attempting to install via docker compose

Viewed 8

Hi,
I'm attempting to install the latest version of Chirpstack so I can do some basic station testing with my US915 (band 2 - aka us915_1) devices.

I have a freshly installed Ubuntu 22.04 machine which I'm trying to use for the server.
I have the latest released docker installed, and I have made the following cofiguration file changes from the default eu868:

docker-compose.yml:

I changed the eu868 topic prefixes to us915_1

and I changed this:
"command: -c /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge-basicstation-eu868.toml"

to
"command: -c /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge-basicstation-us915_1.toml"

I copied region_us915_1.toml to chirpstack.toml

biff@dell:/chirpstack-docker/configuration/chirpstack$ diff chirpstack.toml region_us915_1.toml
biff@dell:
/chirpstack-docker/configuration/chirpstack$
(no differences)

I left this file alone, since I saw we're explicitly sourcing the correct file in the docker-compose.yml file:

Left this file alone, since we're explicitly sourcing it in the docker file

biff@dell:/chirpstack-docker/configuration/chirpstack-gateway-bridge$ git diff chirpstack-gateway-bridge.toml
biff@dell:
/chirpstack-docker/configuration/chirpstack-gateway-bridge$
(no changes)

During the install, I get an error connecting to server - and that's it.
Hopefully I am missing something simple.

biff@dell:~/chirpstack-docker$ sudo docker compose up
[+] up 53/54
 ✔ Image eclipse-mosquitto:2                                            Pulled                            3.5s
 ✔ Image chirpstack/chirpstack:4                                        Pulled                            3.7s
 ✔ Image chirpstack/chirpstack-rest-api:4                               Pulled                            3.6s
 ✔ Image chirpstack/chirpstack-gateway-bridge:4                         Pulled                            3.2s
 ✔ Image postgres:14-alpine                                             Pulled                            7.2s
 ✔ Image redis:7-alpine                                                 Pulled                            3.6s
 ✔ Network chirpstack-docker_default                                    Created                           0.0s
 ✔ Volume chirpstack-docker_postgresqldata                              Created                           0.0s
 ✔ Volume chirpstack-docker_redisdata                                   Created                           0.0s
 ✔ Container chirpstack-docker-mosquitto-1                              Created                           1.9s
 ✔ Container chirpstack-docker-postgres-1                               Created                           1.8s
 ✔ Container chirpstack-docker-redis-1                                  Created                           1.9s
 ✔ Container chirpstack-docker-chirpstack-gateway-bridge-basicstation-1 Created                           0.1s
 ✔ Container chirpstack-docker-chirpstack-1                             Created                           0.1s
 ✔ Container chirpstack-docker-chirpstack-gateway-bridge-1              Created                           0.1s
 ✔ Container chirpstack-docker-chirpstack-rest-api-1                    Created                           0.1s
Attaching to chirpstack-1, chirpstack-gateway-bridge-1, chirpstack-gateway-bridge-basicstation-1, chirpstack-rest-api-1, mosquitto-1, postgres-1, redis-1
mosquitto-1  | 1771016379: Info: running mosquitto as user: mosquitto.
mosquitto-1  | 1771016379: mosquitto version 2.1.2 starting
mosquitto-1  | 1771016379: Config loaded from /mosquitto/config/mosquitto.conf.
mosquitto-1  | 1771016379: Bridge support available.
mosquitto-1  | 1771016379: Persistence support available.
mosquitto-1  | 1771016379: TLS support available.
mosquitto-1  | 1771016379: TLS-PSK support available.
mosquitto-1  | 1771016379: Websockets support available.
mosquitto-1  | 1771016379: Opening ipv4 listen socket on port 1883.
mosquitto-1  | 1771016379: Opening ipv6 listen socket on port 1883.
mosquitto-1  | 1771016379: mosquitto version 2.1.2 running
redis-1      | 1:C 13 Feb 2026 20:59:39.276 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis-1      | 1:C 13 Feb 2026 20:59:39.278 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis-1      | 1:C 13 Feb 2026 20:59:39.278 * Redis version=7.4.7, bits=64, commit=00000000, modified=0, pid=1, just started
redis-1      | 1:C 13 Feb 2026 20:59:39.278 * Configuration loaded
redis-1      | 1:M 13 Feb 2026 20:59:39.278 * Increased maximum number of open files to 10032 (it was originally set to 1024).
redis-1      | 1:M 13 Feb 2026 20:59:39.278 * monotonic clock: POSIX clock_gettime
redis-1      | 1:M 13 Feb 2026 20:59:39.279 * Running mode=standalone, port=6379.
redis-1      | 1:M 13 Feb 2026 20:59:39.279 * Server initialized
redis-1      | 1:M 13 Feb 2026 20:59:39.280 * Ready to accept connections tcp
postgres-1   | The files belonging to this database system will be owned by user "postgres".
postgres-1   | This user must also own the server process.
postgres-1   | 
postgres-1   | The database cluster will be initialized with locale "en_US.utf8".
postgres-1   | The default database encoding has accordingly been set to "UTF8".
postgres-1   | The default text search configuration will be set to "english".
postgres-1   | 
postgres-1   | Data page checksums are disabled.
postgres-1   | 
postgres-1   | fixing permissions on existing directory /var/lib/postgresql/data ... ok
postgres-1   | creating subdirectories ... ok
postgres-1   | selecting dynamic shared memory implementation ... posix
postgres-1   | selecting default max_connections ... 100
postgres-1   | selecting default shared_buffers ... 128MB
postgres-1   | selecting default time zone ... UTC
postgres-1   | creating configuration files ... ok
chirpstack-gateway-bridge-1  | time="2026-02-13T20:59:39.547695434Z" level=info msg="starting ChirpStack Gateway Bridge" docs="https://www.chirpstack.io/gateway-bridge/" version=
chirpstack-gateway-bridge-1  | time="2026-02-13T20:59:39.547902607Z" level=info msg="backend/semtechudp: starting gateway udp listener" addr="0.0.0.0:1700"
mosquitto-1                  | 1771016379: New connection from 172.18.0.5:56796 on port 1883.
mosquitto-1                  | 1771016379: New client connected from 172.18.0.5:56796 as auto-6F21FF58-AE5C-DF96-2131-74FF8F21B0C0 (p4, c1, k30).
chirpstack-gateway-bridge-1  | time="2026-02-13T20:59:39.552863204Z" level=info msg="integration/mqtt: connected to mqtt broker"
chirpstack-gateway-bridge-1  | time="2026-02-13T20:59:39.552890612Z" level=warning msg="[store]    memorystore wiped" module=mqtt
chirpstack-gateway-bridge-basicstation-1  | time="2026-02-13T20:59:39.577816869Z" level=info msg="starting ChirpStack Gateway Bridge" docs="https://www.chirpstack.io/gateway-bridge/" version=
mosquitto-1                               | 1771016379: New connection from 172.18.0.6:37268 on port 1883.
mosquitto-1                               | 1771016379: New client connected from 172.18.0.6:37268 as auto-E97C9F88-65B0-CF3C-0B97-906E13AD1368 (p4, c1, k30).
chirpstack-gateway-bridge-basicstation-1  | time="2026-02-13T20:59:39.580101722Z" level=info msg="integration/mqtt: connected to mqtt broker"
chirpstack-gateway-bridge-basicstation-1  | time="2026-02-13T20:59:39.580231652Z" level=warning msg="[store]    memorystore wiped" module=mqtt
chirpstack-gateway-bridge-basicstation-1  | time="2026-02-13T20:59:39.580461723Z" level=info msg="backend/basicstation: starting websocket listener" bind="[::]:3001" ca_cert= tls_cert= tls_key= tls_support_proxy=false
postgres-1                                | running bootstrap script ... ok
chirpstack-1                              | 2026-02-13T20:59:39.611332Z  INFO chirpstack::cmd::root: Starting ChirpStack LoRaWAN Network Server version="4.16.2" docs="https://www.chirpstack.io/"
chirpstack-1                              | 2026-02-13T20:59:39.611418Z  INFO chirpstack::storage::postgres: Setting up PostgreSQL connection pool
chirpstack-1                              | 2026-02-13T20:59:39.611447Z  INFO chirpstack::storage::postgres: Using Verified connection recycling method (SELECT 1 validation query)
chirpstack-1                              | 2026-02-13T20:59:39.611688Z  INFO chirpstack::storage: Applying schema migrations
chirpstack-1                              | Error: Error occurred while creating a new object: error connecting to server
chirpstack-1                              | 
chirpstack-1                              | Caused by:
chirpstack-1                              |     error connecting to server
chirpstack-rest-api-1                     | Starting ChirpStack REST API server
postgres-1                                | sh: locale: not found
postgres-1                                | 2026-02-13 20:59:40.045 UTC [35] WARNING:  no usable system locales were found
chirpstack-1 exited with code 1 (restarting)
chirpstack-1                              | 2026-02-13T20:59:40.079610Z  INFO chirpstack::cmd::root: Starting ChirpStack LoRaWAN Network Server version="4.16.2" docs="https://www.chirpstack.io/"
chirpstack-1                              | 2026-02-13T20:59:40.079650Z  INFO chirpstack::storage::postgres: Setting up PostgreSQL connection pool
chirpstack-1                              | 2026-02-13T20:59:40.079656Z  INFO chirpstack::storage::postgres: Using Verified connection recycling method (SELECT 1 validation query)
chirpstack-1                              | 2026-02-13T20:59:40.079885Z  INFO chirpstack::storage: Applying schema migrations
chirpstack-1                              | Error: Error occurred while creating a new object: error connecting to server
chirpstack-1                              | 
chirpstack-1                              | Caused by:
chirpstack-1                              |     error connecting to server
chirpstack-1 exited with code 1 (restarting)
chirpstack-1                              | 2026-02-13T20:59:40.523337Z  INFO chirpstack::cmd::root: Starting ChirpStack LoRaWAN Network Server version="4.16.2" docs="https://www.chirpstack.io/"
chirpstack-1                              | 2026-02-13T20:59:40.523367Z  INFO chirpstack::storage::postgres: Setting up PostgreSQL connection pool
chirpstack-1                              | 2026-02-13T20:59:40.523373Z  INFO chirpstack::storage::postgres: Using Verified connection recycling method (SELECT 1 validation query)
chirpstack-1                              | 2026-02-13T20:59:40.523617Z  INFO chirpstack::storage: Applying schema migrations
chirpstack-1                              | Error: Error occurred while creating a new object: error connecting to server
chirpstack-1                              | 
chirpstack-1                              | Caused by:
chirpstack-1                              |     error connecting to server
chirpstack-1 exited with code 1 (restarting)
postgres-1                                | performing post-bootstrap initialization ... ok
postgres-1                                | syncing data to disk ... ok
postgres-1                                | 
postgres-1                                | 
postgres-1                                | Success. You can now start the database server using:
postgres-1                                | 
postgres-1                                |     pg_ctl -D /var/lib/postgresql/data -l logfile start
postgres-1                                | 
postgres-1                                | initdb: warning: enabling "trust" authentication for local connections
postgres-1                                | You can change this by editing pg_hba.conf or using the option -A, or
postgres-1                                | --auth-local and --auth-host, the next time you run initdb.
postgres-1                                | waiting for server to start....2026-02-13 20:59:41.003 UTC [41] LOG:  starting PostgreSQL 14.21 on x86_64-pc-linux-musl, compiled by gcc (Alpine 15.2.0) 15.2.0, 64-bit
postgres-1                                | 2026-02-13 20:59:41.006 UTC [41] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres-1                                | 2026-02-13 20:59:41.013 UTC [42] LOG:  database system was shut down at 2026-02-13 20:59:40 UTC
postgres-1                                | 2026-02-13 20:59:41.018 UTC [41] LOG:  database system is ready to accept connections
postgres-1                                |  done
postgres-1                                | server started
chirpstack-1                              | 2026-02-13T20:59:41.151217Z  INFO chirpstack::cmd::root: Starting ChirpStack LoRaWAN Network Server version="4.16.2" docs="https://www.chirpstack.io/"
chirpstack-1                              | 2026-02-13T20:59:41.151257Z  INFO chirpstack::storage::postgres: Setting up PostgreSQL connection pool
chirpstack-1                              | 2026-02-13T20:59:41.151264Z  INFO chirpstack::storage::postgres: Using Verified connection recycling method (SELECT 1 validation query)
chirpstack-1                              | 2026-02-13T20:59:41.151478Z  INFO chirpstack::storage: Applying schema migrations
chirpstack-1                              | Error: Error occurred while creating a new object: error connecting to server
chirpstack-1                              | 
chirpstack-1                              | Caused by:
chirpstack-1                              |     error connecting to server
postgres-1                                | CREATE DATABASE
postgres-1                                | 
postgres-1                                | 
postgres-1                                | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/001-chirpstack_extensions.sh
postgres-1                                | CREATE EXTENSION
postgres-1                                | CREATE EXTENSION
postgres-1                                | 
postgres-1                                | waiting for server to shut down....2026-02-13 20:59:41.317 UTC [41] LOG:  received fast shutdown request
postgres-1                                | 2026-02-13 20:59:41.322 UTC [41] LOG:  aborting any active transactions
postgres-1                                | 2026-02-13 20:59:41.325 UTC [41] LOG:  background worker "logical replication launcher" (PID 48) exited with exit code 1
postgres-1                                | 2026-02-13 20:59:41.325 UTC [43] LOG:  shutting down
chirpstack-1 exited with code 1 (restarting)
postgres-1                                | 2026-02-13 20:59:41.361 UTC [41] LOG:  database system is shut down
postgres-1                                |  done
postgres-1                                | server stopped
postgres-1                                | 
postgres-1                                | PostgreSQL init process complete; ready for start up.
postgres-1                                | 
postgres-1                                | 2026-02-13 20:59:41.445 UTC [1] LOG:  starting PostgreSQL 14.21 on x86_64-pc-linux-musl, compiled by gcc (Alpine 15.2.0) 15.2.0, 64-bit
postgres-1                                | 2026-02-13 20:59:41.445 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres-1                                | 2026-02-13 20:59:41.445 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres-1                                | 2026-02-13 20:59:41.449 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres-1                                | 2026-02-13 20:59:41.455 UTC [59] LOG:  database system was shut down at 2026-02-13 20:59:41 UTC
postgres-1                                | 2026-02-13 20:59:41.461 UTC [1] LOG:  database system is ready to accept connections
chirpstack-1                              | 2026-02-13T20:59:42.174462Z  INFO chirpstack::cmd::root: Starting ChirpStack LoRaWAN Network Server version="4.16.2" docs="https://www.chirpstack.io/"
chirpstack-1                              | 2026-02-13T20:59:42.174492Z  INFO chirpstack::storage::postgres: Setting up PostgreSQL connection pool
chirpstack-1                              | 2026-02-13T20:59:42.174498Z  INFO chirpstack::storage::postgres: Using Verified connection recycling method (SELECT 1 validation query)
chirpstack-1                              | 2026-02-13T20:59:42.174731Z  INFO chirpstack::storage: Applying schema migrations
chirpstack-1                              | Error: Error occurred while creating a new object: error connecting to server
chirpstack-1                              | 
chirpstack-1                              | Caused by:
chirpstack-1                              |     error connecting to server
chirpstack-1 exited with code 1 (restarting)
chirpstack-1                              | 2026-02-13T20:59:43.992672Z  INFO chirpstack::cmd::root: Starting ChirpStack LoRaWAN Network Server version="4.16.2" docs="https://www.chirpstack.io/"
chirpstack-1                              | 2026-02-13T20:59:43.992700Z  INFO chirpstack::storage::postgres: Setting up PostgreSQL connection pool
chirpstack-1                              | 2026-02-13T20:59:43.992706Z  INFO chirpstack::storage::postgres: Using Verified connection recycling method (SELECT 1 validation query)
chirpstack-1                              | 2026-02-13T20:59:43.992960Z  INFO chirpstack::storage: Applying schema migrations
chirpstack-1                              | Error: Error occurred while creating a new object: error connecting to server
chirpstack-1                              | 
chirpstack-1                              | Caused by:
chirpstack-1                              |     error connecting to server
chirpstack-1 exited with code 1 (restarting)
1 Answers

I copied region_us915_1.toml to chirpstack.toml

Please note that these are separate configurations. chirpstack.toml is for the "main" configuration, where region_XXXXX.toml is for each region configuration. They should both exist. In chirpstack.toml you will find a config option enabled_regions where you can enable each region config (by adding the region id to this list).