@brocaar, maybe this particular ‘error’ deserves its own entry in ChirpStack FAQ because (a) its causes and solutions vary, (b) there is no prescribed, logical procedure of things to check - what @cstratton supplies is wonderful but I didn’t find it until today! And, combined, these factors mean that (c) this ‘error’ has high probability of affecting most (all?) ChirpStack users sooner or later.
Benefits are numerous and obvious; these include:
- Sure would be nice to have an ‘official’ procedure to eliminate all known possibilities. This reduces anxiety through its mere existence and makes ChirpStack administration more predictable.
- Forum user can direct users to that entry, which has high probability of bringing quick relief to people who encountered this issue.
- If problem persists, people can state in the forum that they’ve already followed the FAQ entry, which saves time for everyone
- If someone runs into a new cause & solution, they can submit/open a ticket instead of only sharing it via the forums or (worse yet) not sharing it at all.
Thank you.