ChirpStack connect from external

ChirpStack (v4) Setup and configuration
1

Hi all,

I have installed Chirpstack on my Debian instance on AWS Amazon. Chirpstack is listening on 0.0.0.0:8080, as confirmed by the output of netstat -naop:

tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      3065705/chirpstack   off (0.00/0/0)

When attempting to connect using links at localhost:8080 or my private IP address, the connection is successful:

Nov 18 09:02:40 ip-172-31-41-87 chirpstack[3065705]: 2023-11-18T09:02:40.052802Z  INFO http{method="GET" uri=/ version=HTTP/1.1}: chirpstack::api: Finished processing request status="200" latency=54.241µs
Nov 18 09:02:59 ip-172-31-41-87 chirpstack[3065705]: 2023-11-18T09:02:59.262605Z  INFO http{method="GET" uri=/ version=HTTP/1.1}: chirpstack::api: Finished processing request status="200" latency=42.909µs

However, when trying to access it using the external IP address, the server does not respond. I have ensured that all TCP and UDP ports are enabled in the AWS Incoming Rules, and there is no firewall in place. Additionally, the server is also being used with ports 80 and 443 for Apache.

Any suggestions on resolving this issue would be greatly appreciated.

2

I have an update.

Using tcpdump -i ens5 port 8080, I can observe the requests on the Debian server.

3

Hello, I have a further update. If I forward port 8080 via SSH to localhost:8080, I can see the management interface.
Conversely, with the public IP, I cannot access it.
I don’t understand where is the problem.

  • AWS allow all Traffic
  • my firewall is Down
  • the 8080 is listening on 0.0.0.0

Could it depend on the fact that it is not listening on IPv6?

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.