Axios Error while trying to view device details on TTN web console

TTN Network and Services The Things Stack v3
1

Need help with this error:

An error occurred and the request could not be completed. If the error persists, please contact support.
We’re sorry for the inconvenience.
Error Type: AxiosError

{
  "message": "timeout of 10000ms exceeded",
  "name": "AxiosError",
  "stack": "AxiosError: timeout of 10000ms exceeded\n    at u.ontimeout (https://assets.cloud.thethings.network/console.4a399eda2365b7b8e6de.js:2:915342)\n    at Oe.request (https://assets.cloud.thethings.network/console.4a399eda2365b7b8e6de.js:2:920092)",
  "config": {
    "transitional": {
      "silentJSONParsing": true,
      "forcedJSONParsing": true,
      "clarifyTimeoutError": false
    },
    "adapter": [
      "xhr",
      "http"
    ],
    "transformRequest": [
      null
    ],
    "transformResponse": [
      null
    ],
    "timeout": 10000,
    "xsrfCookieName": "XSRF-TOKEN",
    "xsrfHeaderName": "X-XSRF-TOKEN",
    "maxContentLength": -1,
    "maxBodyLength": -1,
    "env": {},
    "headers": {
      "Accept": "application/json, text/plain, */*",
      "Authorization": "Bearer MFRWG.Q"
    },
    "baseURL": "https://au1.cloud.thethings.network/api/v3",
    "method": "get",
    "url": "/as/applications/aus-depth/devices/aa24",
    "params": {
      "field_mask": "version_ids,formatters,skip_payload_crypto_override,session,pending_session"
    }
  },
  "code": "ECONNABORTED",
  "status": null
}```
1 Like
2

I have the same error too. I tried to view the device details and encountered AxiosError.

I couldn’t register new end devices as well.

3

I have also similar case, then now unable to explore end device, with this error type:AxiosError
image

The technical detail as bellow

{
  "message": "timeout of 10000ms exceeded",
  "name": "AxiosError",
  "stack": "AxiosError: timeout of 10000ms exceeded\n    at u.ontimeout (https://assets.cloud.thethings.network/console.4a399eda2365b7b8e6de.js:2:915342)\n    at Oe.request (https://assets.cloud.thethings.network/console.4a399eda2365b7b8e6de.js:2:920092)",
  "config": {
    "transitional": {
      "silentJSONParsing": true,
      "forcedJSONParsing": true,
      "clarifyTimeoutError": false
    },
    "adapter": [
      "xhr",
      "http"
    ],
    "transformRequest": [
      null
    ],
    "transformResponse": [
      null
    ],
    "timeout": 10000,
    "xsrfCookieName": "XSRF-TOKEN",
    "xsrfHeaderName": "X-XSRF-TOKEN",
    "maxContentLength": -1,
    "maxBodyLength": -1,
    "env": {},
    "headers": {
      "Accept": "application/json, text/plain, */*",
      "Authorization": "Bearer MFRWG."
    },
    "baseURL": "https://au1.cloud.thethings.network/api/v3",
    "method": "get",
    "url": "/as/configuration",
    "params": {}
  },
  "code": "ECONNABORTED",
  "status": null
}
4

Moved as not similar to “End device already registered”

5

Top brains at TTI are aware of the situation and are investigating. Time scales will be in line with the SLA, so please be patient and don’t ask.

1 Like
6

The issue seems to have been resolved for my console. I am sure the good folks at TTI would do an RCA and fix the root cause in due course.

7

TTS is OK, it wasn’t an issue for EU. It seems to be an over enthusiastic community user draining resources for AU & NAM with some faulty integration access.

Which goes to show how we all need to play nicely with the kit provided for free as it’s not a bottomless pit of CPU cycles!

2 Likes
8

Hmm… looks like that user’s enthusiasm hasn’t waned yet! [something an API rate limit can solve?]
Still seeing a few of these Axios timeouts once in a while! :slight_smile:, just saying.

9

Rate limiting works in many circumstances which is why this sort of thing is a rare event, but there are configurations that can confound such things by careless coding - like logging in, query, log out, repeat at speed. Or one of the more priceless ones, having a bunch of end users directly accessing the TTN servers rather than having the data proxied via own system backend.

This is the new realistic world of TT Sandbox. It was sort of like this previously, but there aren’t the resources to jump all over out of hours issues anymore. Even then a volunteer moderator contacted TTI staff by back channels to make sure it wasn’t all going to completely collapse.

If you can’t live with this sort of hiccup coming up you should be on a TTI instance, perhaps @rish1 can help out if you have a fair number of users on your system being inconvenienced.

10

I would be interested in finding out how to set up a TTI instance. Doesn’t seem like the person hogging the resources has given up as I am still getting Axios errors. Is there a way to disable their device and does this not breach some TOS agreement?

11

You buy it for €200/month - simples.

It’s not their device, one device can’t achieve that, it’s typically an integration gone wild. And it’s actually incredibly hard to disable a rogue device without disabling all the gateways around it and even then the gateways would still send network traffic to the servers even if they were silently dropped.

Terms of Service implies a contract of which there is only the moral & ethical contract of the community use with the guidance of the Fair Use Policy. We don’t pay for TTN so it’s all run on good will.


It is straight forward enough for TTI staff to disable an account but they, like the rest of the world, benefit from down time every few days, whilst some of them are god like, even God rested on the Seventh day.

However if you pay for an instance and support, then there are funds to access the support network that runs all the time. But you’d rarely face such issues because people tend to look after the kit they pay for, mostly.

1 Like