Error context deadline exceeded

Hello,
I installed also ChirpStack on a raspberry debian buster (without Docker). Everything work for some days and today when i click on some items (gateway or device) on the web interface i get the error:
Error context deadline exceeded (code 2)
Can someone help me?

Have you had any success with this? I too am getting this bug. I got this bug even after reverting back to an image that was working completely on a different SD card. The pi worked for about 2 weeks and now it throws this exception when trying to access Gateway-profiles, service-profiles, device-profiles, gateways or applications

Hey all,
I just had this issue on my R-Pi using a somewhat suspect 8Gb SD card.

I solve it by just employing some house-keeping…

I recommend you check the following:

  1. Is your SD card good/fake etc?

  2. verify all SD card image reading and writing sessions

  3. clean your Ubuntu (clear old cache and logs files) to gain more disk space if you need it (my Chirpstack stated running quite slow and after I freed up space its back to fast UI loading etc)

  4. make sure you have a large enough swap file setup

  5. make back-up of your SD card image regularly.

  6. Use a class 10 16 or 32Gb SD card

  7. fit a CPU reset button on your R-Pi and only ever power up and down the R-Pi pressing the reset button first, only ever insert/remove the SD card when the power is off!

  8. watch out for log files etc building up over time and reducing the memory available!

  9. check for linux malware

Hi @brocaar, I have installed using apt but not docker. And since certificates are optional, I haven’t provided any. How do I resolve this error?

I know this is a bit late, but I’ll comment in case it helps anyone else.
Try putting in the LAN or WAN IP address of the VM rather than ‘localhost’.
If this doesn’t fix it or your machine doesn’t have an IP address, this may be a problem with the either,

  1. The VM firewall
  2. The hypervisor/VM hosting application (e.g. I’ve run into an issue with docker-ce not resolving hostnames between containers if not connecting to a WAN)

Good luck!

Hi, maybe my answer to another post can help some people for this issue. Here is the link :

I have got the same problem. I copy the virtual machine to new IP address and got “context deadline exceeded (code 2)”. I solve the problem when I change the correct address in tab “Network servers”

I have installed in AWS EC2 ubuntu [no docker]and the same error rises. I tried different methods and finally given localhost:8000 and it works.

i am trying to do it with debian ubuntu , but still i am also getting he same error

Oct 04 10:59:37 mqtt.tihiitb.org chirpstack-application-server[176883]: time=“2024-10-04T10:59:37.307145303Z” level=warning msg=“creating insecure network-server client” server=“13.235.236.141:8000”
Oct 04 10:59:37 mqtt.tihiitb.org chirpstack-application-server[176883]: time=“2024-10-04T10:59:37.808203356Z” level=warning msg=“[core] grpc: addrConn.createTransport failed to connect to {13.235.236.141:8000 13.235.236.141:8000 0 }. Err: connection error: desc = "transport: Error while dialing dial tcp 13.235.236.141:8000: operation was canceled". Reconnecting…”
Oct 04 10:59:37 mqtt.tihiitb.org chirpstack-application-server[176883]: time=“2024-10-04T10:59:37.808435508Z” level=error msg=“finished unary call with code Unknown” ctx_id=eee750b1-b3d8-4563-914d-a17ed562712b error=“rpc error: code = Unknown desc = context deadline exceeded” grpc.code=Unknown grpc.method=Create grpc.service=api.NetworkServerService grpc.start_time=“2024-10-04T10:59:37Z” grpc.time_ms=502.887 peer.address=“127.0.0.1:58174” span.kind=server system=grpc
Oct 04 10:59:39 mqtt.tihiitb.org chirpstack-application-server[176883]: time=“2024-10-04T10:59:39.962837793Z” level=warning msg=“creating insecure network-server client” server=“13.235.236.141:8000”

this is the ip adress of my machine and my port 8080 is also working with this ip adress , but when i am trying to add a network server to this port , then it is showing context deadline exceeded , please support me to clear this problem

Please realize that you are trying to setup a ChirpStack version which is no longer supported. ChirpStack v4 contains many improvements and is a lot easier to setup.