No Events or Frames

Ben1983 · March 20, 2024, 8:20am

Hello, in my Chirpstack docker container there works everthing fine, just the events or frames did not load.

Has anyone the same problem, or solved this?

fainlaip · March 20, 2024, 8:28am

Hi @Ben,

I can see frames from my uplink messages, but did not manage to send any downlink messages.

What about Your gateway status, is it online or?

Best regards,
Filip

Ben1983 · March 20, 2024, 9:17am

Yes the Gateway is online.

fainlaip · March 20, 2024, 9:31am

And what devices are You using for gateway and end nodes?
What was the process of registering Your gateway?

I have a problem with gateway connection, it won’t go online. I am using Nucleo F746ZG (gateway) and WL55JC1 (end node).
Do You have any idea what could be my problem?

Best regards,

Filip

Ben1983 · March 20, 2024, 10:42am

Doorsensors, soilsensors, Relais

brocaar · March 27, 2024, 10:40am

Are you using a proxy, e.g. NGINX? In that case you must add some configuration to make sure the gRPC streaming requests are handled and proxied correctly:

github.com

chirpstack/chirpstack-ansible-playbook/blob/master/roles/chirpstack/templates/chirpstack.nginx#L21


      
          	listen 443 ssl http2;
          	server_name {{ chirpstack.fqdn }};
          	{% if chirpstack.letsencrypt.request %}
          	ssl_certificate /etc/letsencrypt/live/{{ chirpstack.fqdn }}/fullchain.pem;
          	ssl_certificate_key /etc/letsencrypt/live/{{ chirpstack.fqdn }}/privkey.pem;
          	{% else %}
          	ssl_certificate /etc/nginx/certs/chirpstack.pem;
          	ssl_certificate_key /etc/nginx/certs/chirpstack-key.pem;
          	{% endif %}
          
          	location ^~ /api { 
          		grpc_pass grpc://localhost:8080; 
          	} 
          
          	location / {
          		proxy_pass http://localhost:8080;
          	}
          }

Ben1983 · March 27, 2024, 11:39am

Hi. in my Network, there is no proxy in use.

brocaar · April 11, 2024, 7:58am

In some cases, it could be due to a virus scanner at the client-side. In this case the virus scanner intercepts all browser traffic, causing the gRPC stream functionality to break. You will find some topics on the forum about this.