I was about to respond that it was all working again by adding the DeviceID in my Uplink node.
Could it be that due to the whole flow working on minute and failing the other that it is related to:
Is there some firewall on the discovery server that can be triggered and results in clients being blocked?
I now have two hosts, in different countries, that can no longer connect to:
discovery.thethingsnetwork.org:1900
I’ve just gone and moved the whole application stack from one host to another to resolve this after connections from the first were being blocked, and now it’s happened on the second.
Not doing anything unusual and simply using Node Red to connect.
Hi,
We have found that whilst running the TTN forwarder on a Virgin Media (Large UK ISP) internet connection, we are unable to contact the discovery server on port 1900.
The forwarder fails with:
grpc: addrConn.resetTransport failed to create client transport: connection error: desc = “transport: context deadline exceeded”; Reconnecting to {discover.thethingsnetwork.org:1900
After some digging we found that Virgin Media issued a security warning on port 1900, here and even though my VM Sup…
2 Likes