Gateway (Rak 7249) Last seen: Never

21

Ya thats it, and in your docker-compose.yml you changed the region prefixes to us915_1?

22

Yes, I did make that change.

23

Probably should have started here first but if you check the chirpstack docker logs, are there any errors?

sudo docker compose logs -f
24

none that I’m seeing so far.

25

let me disable the other regions not in use so I can clean up these logs a bit and restart docker.

26

chirpstack-gateway-bridge-basicstation-1 | time=“2024-06-25T18:28:17.007706367Z” level=warning msg=“[store] memorystore wiped” module=mqtt

27

I don’t know what that means, but you are using the udp bridge not the basicstation bridge correct? so that shouldn’t matter?

Any other errors when booting up?

28

This is what’s in my chirpstack.toml

enabled_regions=[
“us915_0”,
“us915_1”,
]

29

chirpstack-1 | 2024-06-25T15:48:20.449112Z ERROR chirpstack::gateway::backend::mqtt: MQTT error error=I/O: Connection refused (os error 111)

30

Ya but there is two gateway bridges installed by default, the udp and the basicstation.

chirpstack-gateway-bridge:
image: chirpstack/chirpstack-gateway-bridge:4
restart: unless-stopped
ports:
- 1700:1700/udp
volumes:
- ./configuration/chirpstack-gateway-bridge:/etc/chirpstack-gateway-bridge
environment:
- INTEGRATION__MQTT__EVENT_TOPIC_TEMPLATE=us915/gateway/{{ .GatewayID }}/event/{{ .EventType }}
- INTEGRATION__MQTT__STATE_TOPIC_TEMPLATE=us915/gateway/{{ .GatewayID }}/state/{{ .StateType }}
- INTEGRATION__MQTT__COMMAND_TOPIC_TEMPLATE=us915/gateway/{{ .GatewayID }}/command/#
depends_on:
- mosquitto

chirpstack-gateway-bridge-basicstation:
image: chirpstack/chirpstack-gateway-bridge:4
restart: unless-stopped
command: -c /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge-basicstation-us915_1.toml

You are using the UDP one right, i.e your gateway forwards to 1700 on the server. So the basicstation gateway bridge errors shouldn’t affect you.

31

There it is, your chirpstack is failing to connect

32

Have you made any changes from default chirpstack docker install, like the MQTT TLS configuration?

33

No I’ve not made any changes for MQTT

34

hmm, does this need to be changed to 127.0.0.1

[ec2-user@chirpstack chirpstack-gateway-bridge]$ cat chirpstack-gateway-bridge.toml

configuration example and documentation.

[integration.mqtt.auth.generic]
servers=[“tcp://mosquitto:1883”]

35

By default Chirpstack should connect fine, so if you did nothing to change the connection requirement. There is probably some networking issue, a firewall or someting. That line does not need to be changed.

36

It’s all on the same host though, so I don’t see how it would be a network/firewall issue. Could that error message just be an artifact of when I stopped and started docker?

37

port 1700 is open and receiving data

38

Should I just docker-compose rm and start from scratch again?

39

Well, I’m not sure why, but that seems to have done the trick.

40

Thanks for all of your help Liam it was greatly appreciated.

2 Likes