It’s been a long and arduous process getting to this point in installing and configuring Chirpstack. The big thing has been the certificates and following out of date advice, and the chirpstack-certificates docker not producing working certs for me.
Somewhere along the way my Web UI no longer starts. It was previously working via Traefik into port 8082. Now, with or without Traefik, I can only get the API to show on port 8090.
Why am I getting no errors or anything appearing to suggest as to why it’s not starting? The Alpine linux container has limited ability, I can’t do journalctl… or dmesg. Is there any way I can see what the issue is to fix it?
Any help very much appreciated 
my chirpstack.toml
[logging]
# Log level.
#
# Options are: trace, debug, info, warn error.
level="trace"
# PostgreSQL configuration.
[postgresql]
# PostgreSQL DSN.
#
# Format example: postgres://<USERNAME>:<PASSWORD>@<HOSTNAME>/<DATABASE>?sslmode=<SSLMODE>.
#
# SSL mode options:
# * 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://chirpstack:chirpstack@$POSTGRESQL_HOST/chirpstack?sslmode=disable"
# Max open connections.
#
# This sets the max. number of open connections that are allowed in the
# PostgreSQL connection pool.
max_open_connections=10
# Min idle connections.
#
# This sets the min. number of idle connections in the PostgreSQL connection
# pool (0 = equal to max_open_connections).
min_idle_connections=0
# Redis configuration.
[redis]
# Server address or addresses.
#
# Set multiple addresses when connecting to a cluster.
servers=[
"redis://$REDIS_HOST/",
]
# TLS enabled.
tls_enabled=false
# Redis Cluster.
#
# Set this to true when the provided URLs are pointing to a Redis Cluster
# instance.
cluster=false
# Network related configuration.
[network]
# Network identifier (NetID, 3 bytes) encoded as HEX (e.g. 010203).
net_id="000000"
# Enabled regions.
#
# Multiple regions can be enabled simultaneously. Each region must match
# the 'name' parameter of the region configuration in '[[regions]]'.
enabled_regions=[
"au915_0",
]
[api]
# interface:port to bind the API interface to.
#bind="0.0.0.0:8080"
bind="0.0.0.0:8090"
# Secret.
#
# This secret is used for generating login and API tokens, make sure this
# is never exposed. Changing this secret will invalidate all login and API
# tokens. The following command can be used to generate a random secret:
# openssl rand -base64 32
secret="HH1tAOR6ZgVnNENpH4dProxhazJY4iVVsz6cP592ixs="
# Global gateway configuration.
# Please note that backend configuration can be found in the per-region
# configuration.
[gateway]
# CA certificate and key file (optional).
#
# If setting the CA certificate and key file options, ChirpStack
# will generate client certificates which can be used by the gateway for
# authentication and authorization. The Common Name of the certificate will
# be set to the Gateway ID.
#
# The ca_key is expected to be in PKCS#8 format (you can use openssl to
# convert to PKCS#8).
#ca_cert="/etc/chirpstack/certs/ca/ca.pem"
#ca_key="/etc/chirpstack/certs/ca/ca-key.pem"
ca_cert="/etc/chirpstack/certs/rootCA.crt"
ca_key="/etc/chirpstack/certs/rootCA-pkcs8.pem"
# -rw------- 1 root root 1675 Feb 19 08:56 ca-key.pem
# -rw-r--r-- 1 root root 895 Feb 19 08:56 ca.csr
# -rw-rw-r-- 1 root root 1103 Feb 19 08:56 ca.pem
# Certificate lifetime.
#
# This defines how long (after generating) the certificate remains valid.
#client_cert_lifetime="50months 30days 3h 50m 24s"
client_cert_lifetime="12months"
# Allow unknown gateways.
#
# If set to true, then uplinks received from gateways not configured in
# ChirpStack will be allowed.
allow_unknown_gateways=false
[integration]
enabled=["mqtt"]
[integration.mqtt]
ca_cert="/etc/chirpstack/certs/rootCA.crt"
ca_key="/etc/chirpstack/certs/rootCA-pkcs8.pem"
#server="tcp://$MQTT_BROKER_HOST:1883/"
server="ssl://$MQTT_BROKER_HOST:8883/"
#server="ssl://chirpstack.firetail.digital:8883/"
json=true
[integration.mqtt.client]
ca_cert="/etc/chirpstack/certs/rootCA.crt"
ca_key="/etc/chirpstack/certs/rootCA-pkcs8.pem"
client_cert_lifetime="12months"
#client_cert_lifetime="50months 30days 3h 50m 24s"
In the container,
/ # ps -A
PID USER TIME COMMAND
1 nobody 0:00 /usr/bin/chirpstack -c /etc/chirpstack
11 root 0:00 sh
17 root 0:00 ps -A
/ # netstat -peanut
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:8090 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.11:43699 0.0.0.0:* LISTEN -
tcp 0 0 172.24.0.12:56630 172.24.0.2:8883 ESTABLISHED -
tcp 0 0 172.24.0.12:56632 172.24.0.2:8883 ESTABLISHED -
tcp 0 0 172.24.0.12:58946 172.24.0.8:5432 ESTABLISHED -
tcp 0 0 172.24.0.12:58944 172.24.0.8:5432 ESTABLISHED -
udp 0 0 127.0.0.11:54220 0.0.0.0:* -
/ # netstat -tuln
in my docker compose I have Chirpstack starting on 8082, which it was previously,
chirpstack:
image: chirpstack/chirpstack:4
command: -c /etc/chirpstack
restart: unless-stopped
volumes:
- /home/ben/dockers/chirpstack/configuration/chirpstack:/etc/chirpstack
- /home/ben/dockers/chirpstack/lorawan-devices:/opt/lorawan-devices
depends_on:
- postgres
- mosquitto
- redis
environment:
- MQTT_BROKER_HOST=mosquitto
- REDIS_HOST=redis
- POSTGRESQL_HOST=postgres
networks:
- traefik_global
labels:
- traefik.docker.network=traefik_global
- traefik.default.protocol=https
- traefik.port=443
- traefik.http.routers.${SERVICE_NAME_HTTPS}.entrypoints=https
- traefik.http.routers.${SERVICE_NAME_HTTPS}.rule=Host(`chirpstack.firetail.digital`)
- traefik.http.routers.${SERVICE_NAME_HTTPS}.tls.certresolver=letsencrypt
- traefik.http.routers.${SERVICE_NAME_HTTPS}.tls=true
- traefik.http.routers.${SERVICE_NAME_HTTPS}.service=${SERVICE_NAME}
- traefik.http.services.${SERVICE_NAME}.loadbalancer.server.port=8080
ports:
- 8082:8080
The api works fine on 8090,
chirpstack-rest-api:
image: chirpstack/chirpstack-rest-api:4
restart: unless-stopped
command: --server chirpstack:8080 --bind 0.0.0.0:8090 --insecure
networks:
- traefik_global
labels:
- traefik.docker.network=traefik_global
ports:
- 8090:8090
depends_on:
- chirpstack
nothing shown in the chirpstack logs that I can see, nothing in postgres logs or any other service logs thats obvious to me,
2025-02-22T04:19:22.381162Z INFO chirpstack::integration::mqtt: Connecting to MQTT broker server_uri=ssl://mosquitto:8883/ client_id=d05c603895f021dc clean_session=false
2025-02-22T04:19:22.381206Z INFO chirpstack::gateway::backend: Setting up gateway backends for the different regions
2025-02-22T04:19:22.381211Z INFO chirpstack::gateway::backend: Setting up gateway backend for region region_id=au915_0 region_common_name=AU915
2025-02-22T04:19:22.381275Z INFO chirpstack::integration::mqtt: Starting MQTT event loop
2025-02-22T04:19:22.389858Z INFO chirpstack::gateway::backend::mqtt: Configuring client with TLS certificate, ca_cert: /etc/chirpstack/certs/rootCA.crt, tls_cert: /etc/chirpstack/certs/rootCA.crt, tls_key: /etc/chirpstack/certs/rootCA-pkcs8.pem
2025-02-22T04:19:22.414429Z INFO chirpstack::gateway::backend::mqtt: Connecting to MQTT broker region_id=au915_0 server_uri=ssl://mosquitto:8883 clean_session=false client_id=4f61b4de22c1c720
2025-02-22T04:19:22.414520Z INFO chirpstack::gateway::backend::mqtt: Starting MQTT event loop
2025-02-22T04:19:22.414636Z INFO chirpstack::downlink: Setting up Class-B/C scheduler loop
2025-02-22T04:19:22.414654Z TRACE chirpstack::downlink::scheduler: Starting class_b_c_scheduler_loop run
2025-02-22T04:19:22.414658Z TRACE chirpstack::downlink::scheduler: Getting devices that have schedulable queue-items
2025-02-22T04:19:22.420937Z TRACE chirpstack::downlink::scheduler: Got this number of devices with schedulable queue-items device_count=0
2025-02-22T04:19:22.420961Z TRACE chirpstack::downlink::scheduler: class_b_c_scheduler_loop completed successfully
2025-02-22T04:19:22.420974Z INFO chirpstack::downlink: Setting up multicast scheduler loop
2025-02-22T04:19:22.420991Z TRACE chirpstack::downlink::scheduler: Starting multicast-group queue scheduler loop run
2025-02-22T04:19:22.420994Z TRACE chirpstack::downlink::scheduler: Getting schedulable multicast-group queue items
2025-02-22T04:19:22.421107Z INFO chirpstack::api: Setting up API interface bind=0.0.0.0:8090
2025-02-22T04:19:22.429686Z TRACE chirpstack::integration::mqtt: MQTT event event=Incoming(ConnAck(ConnAck { session_present: false, code: Success, properties: Some(ConnAckProperties { session_expiry_interval: None, receive_max: Some(20), max_qos: None, retain_available: None, max_packet_size: None, assigned_client_identifier: None, topic_alias_max: Some(10), reason_string: None, user_properties: , wildcard_subscription_available: None, subscription_identifiers_available: None, shared_subscription_available: None, server_keep_alive: None, response_information: None, server_reference: None, authentication_method: None, authentication_data: None }) }))
2025-02-22T04:19:22.429724Z INFO chirpstack::integration::mqtt: Subscribing to command topic command_topic=application/+/device/+/command/+
2025-02-22T04:19:22.429858Z TRACE chirpstack::integration::mqtt: MQTT event event=Outgoing(Subscribe(1))
2025-02-22T04:19:22.429888Z TRACE chirpstack::integration::mqtt: MQTT event event=Incoming(SubAck(SubAck { pkid: 1, return_codes: [Success(AtMostOnce)], properties: None }))
2025-02-22T04:19:22.429931Z TRACE chirpstack::downlink::scheduler: Got this number of multicast-group queue items count=0
2025-02-22T04:19:22.429942Z TRACE chirpstack::downlink::scheduler: Multicast-group queue scheduler run completed successfully
2025-02-22T04:19:22.432698Z INFO chirpstack::api::backend: Backend interfaces API interface is disabled
2025-02-22T04:19:22.469712Z TRACE chirpstack::gateway::backend::mqtt: MQTT event event=Incoming(ConnAck(ConnAck { session_present: false, code: Success, properties: Some(ConnAckProperties { session_expiry_interval: None, receive_max: Some(20), max_qos: None, retain_available: None, max_packet_size: None, assigned_client_identifier: None, topic_alias_max: Some(10), reason_string: None, user_properties: , wildcard_subscription_available: None, subscription_identifiers_available: None, shared_subscription_available: None, server_keep_alive: None, response_information: None, server_reference: None, authentication_method: None, authentication_data: None }) }))
2025-02-22T04:19:22.469737Z INFO chirpstack::gateway::backend::mqtt: Subscribing to gateway event topic region_id=au915_0 event_topic=$share/chirpstack/au915_0/gateway/+/event/+
2025-02-22T04:19:22.469855Z TRACE chirpstack::gateway::backend::mqtt: MQTT event event=Outgoing(Subscribe(1))
2025-02-22T04:19:22.469880Z TRACE chirpstack::gateway::backend::mqtt: MQTT event event=Incoming(SubAck(SubAck { pkid: 1, return_codes: [Success(AtMostOnce)], properties: None }))
2025-02-22T04:19:23.422223Z TRACE chirpstack::downlink::scheduler: Starting class_b_c_scheduler_loop run
2025-02-22T04:19:23.422244Z TRACE chirpstack::downlink::scheduler: Getting devices that have schedulable queue-items
2025-02-22T04:19:23.424160Z TRACE chirpstack::downlink::scheduler: Got this number of devices with schedulable queue-items device_count=0
2025-02-22T04:19:23.424179Z TRACE chirpstack::downlink::scheduler: class_b_c_scheduler_loop completed successfully
2025-02-22T04:19:23.431412Z TRACE chirpstack::downlink::scheduler: Starting multicast-group queue scheduler loop run
2025-02-22T04:19:23.431436Z TRACE chirpstack::downlink::scheduler: Getting schedulable multicast-group queue items
2025-02-22T04:19:23.433134Z TRACE chirpstack::downlink::scheduler: Got this number of multicast-group queue items count=0
2025-02-22T04:19:23.433153Z TRACE chirpstack::downlink::scheduler: Multicast-group queue scheduler run completed successfully