LoraWan Frames come with 5 min delay when using NGINX as proxy


I noticed a strange change right after I configured the nginx for https > all the frames from different nodes are coming with ~5 min delay.

I am using Chirpstack v4.
Tried different Internet provider, different GWs, nodes. Same.

Is that an expected behavior? Sorry for generic question, maybe anyone has faced it also, before I dig deeper?


Short feedback, I have disabled ufw and nginx and now messages are coming immediately like before (but no https).
So confirmed, the delay is a side effect of https/nginx config. I remember there was some comment on Chirpstack forum about API feed delay after enabling https? (can’t recall where it was exactly). Perhaps this is common for the front-end as well?

Please see this NGINX proxy example:

1 Like

Thanks brocaar,

You have pointed me in right direction.
I have replaced below lines in /etc/nginx/sites-available/default config file


WebSocket configuration
location ~ ^/api/(gateways|devices)/(\w+)/(frames|events)$ {
proxy_pass http://localhost:8080/api/$1/$2/$3;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “Upgrade”;
proxy_read_timeout 86400s;
proxy_send_timeout 86400s;


location ^~ /api {
grpc_pass grpc://localhost:8080;

Restarted nginx service and now I see the lorawan frames immediately once uplink in sent from the node (before this change, messages were coming all at once with 5 min delay).
Perhaps it was due to proxy read/send timeout…not sure. Anyway, it looks ok now.

Thanks a lot

Hi, and what if I have setup that chirpstack is served from subpath like:

How can I solve this situation?

location ^~ /api { 
		grpc_pass grpc://localhost:8080; 

does not seem to work, even

location ^~ /api/chirpstack { 
		grpc_pass grpc://localhost:8080; 

is not working.

any advice will be blessing

Kind regards

Should be /chirpstack/api?

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