LinnJS - Hello everyone I am trying to setup a ...
Hello everyone I am trying to setup a new signal k server and I am working on getting the signalk-to-influxdb2 plugin working. I got influxdb installed I created a user, org, and bucket. The token is working with signalk but it says the org does not exist even though when I login to the ui I see both the org and the bucket. Not sure how to troubleshoot further since eveything seems to be there.
Thanks in advance for the help! π
Screenshots in π§΅
14 Replies
Influx orgs and buckets
![No description](https://cdn.answeroverflow.com/1225616316623224882/Screenshot_2024-04-04_at_9.19.49_PM.png)
Signal k config
![No description](https://cdn.answeroverflow.com/1225616715447271445/Screenshot_2024-04-04_at_9.22.36_PM.png)
Singal k error logs for influxdb 2
![No description](https://cdn.answeroverflow.com/1225616799895130172/Screenshot_2024-04-04_at_9.22.53_PM.png)
Did you try using "sailfuture" as the org?
this is mine, Org is Apres, Bucket is Apres:
![No description](https://cdn.answeroverflow.com/1225641482430578739/image.png)
Good call @Jason_SV.Apres|Hunter336|WI I actually had it as sailfuture in the beginning I was just testing. I figured if the Org name didnt work to try the ID both have same error.
![No description](https://cdn.answeroverflow.com/1225803699432198255/image.png)
I am also using bookwork so I downgraded to 2.7.4-1 as you suggested in your post and I got the same error as above. Could it be something with a path being off somewhere?
Did you use scopes to generate the token? Try allowing everything when generating the token instead of specifying the bucket and group
I also had issues with it connecting and ended up restarting, as restarting SignalK and Influx didn't work. even when it was back up, it was a few mins before data started appearing
@Tony I think you are onto something I dont think I did let me try making a new token with more scopes.
@Tony that seemed to be the issue when I created the token I made it via the CLI and was not aware of the UI and when I made the new token gave it global access and it worked, or at least I am not getting the error anymore. Going to go the boat on Sunday to put the new image on there configure the canboat connection.
For local instances I donβt think scopes are necessary. If you are using the cloud instance in AWS I would definitely make scoped tokens
Everything is working and problem is solved, thanks for the help ya'll!