I just restarted my instance of InfluxDB Core to use the processing engine. Things are going well untill I try to connect to the Explorer UI or Grafana. What I use my previous token to connect to the server from there, I get: Invalid API token for Core/Enterprise product (plus an error line on the terminal where I’m running Influx: ERROR influxdb3_server::http: cannot authenticate token e=InvalidToken)
When I try to create a new admin token using “influxdb3 create token --admin” it throws the following: Failed to create token, error: ApiError { code: 409, message: “token name already exists, _admin” }
Just a guess as I’m not using Influxdb3, but have you tried adding a non-admin token and using that for access instead of the admin token?
Otherwise, you can probably delete the existing admin token and then create a new one using the command you referenced. I’ve done this in Influxdb2.
I tried this and it didn’t work either, I’m going a different route. Thanks @tkohhh !
Hey Laurence, I understand you’re going a different direction now, but also wanted to chime in here to help if possible, or any others who might come upon this thread. Sounds like you definitely have the token stored properly, since it already exists. Could you ensure that you’re using only the token when inputting into Explorer or Grafana? Not Authorization: Bearer apiv3_… but just the apiv3_… portion.
Additionally, with our 3.3 update today, you can now regenerate the Operator token in case it’s lost or forgotten.
