Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Your access token is not authorized - how to fix it? #273

Open
manoloxxl opened this issue Dec 13, 2022 · 5 comments
Open

Your access token is not authorized - how to fix it? #273

manoloxxl opened this issue Dec 13, 2022 · 5 comments
Labels
documentation Improvements or additions to documentation

Comments

@manoloxxl
Copy link

Hi,

I can see in my logs, that there are many errors:
getWebApi(): Error retrieving logs: 401 - {"detailMessage":"Your access token is not authorized","stackTrace":[],"suppressedExceptions":[]}

I created all tokens new, but the issue is the same. How can i fix this issue?

Best Regards

Manuel

Screenshots & Logfiles

nuki-extended.0 2022-12-13 16:27:15.700 warn getWebApi(): Error retrieving logs: 401 - {"detailMessage":"Your access token is not authorized","stackTrace":[],"suppressedExceptions":[]}
nuki-extended.0 2022-12-13 16:27:15.453 warn getWebApi(): Error retrieving logs: 401 - {"detailMessage":"Your access token is not authorized","stackTrace":[],"suppressedExceptions":[]}
nuki-extended.0 2022-12-13 16:27:15.197 warn getWebApi(): Error retrieving logs: 401 - {"detailMessage":"Your access token is not authorized","stackTrace":[],"suppressedExceptions":[]}
nuki-extended.0 2022-12-13 16:27:14.993 warn getWebApi(): Error retrieving notifications: 401 - {"detailMessage":"Your access token is not authorized","stackTrace":[],"suppressedExceptions":[]}
nuki-extended.0 2022-12-13 16:26:16.995 info Listening for Nuki events on port 51989.
nuki-extended.0 2022-12-13 16:26:16.515 warn Callback not attached because too many Callbacks attached to the Nuki Bridge already! Please delete a callback!
nuki-extended.0 2022-12-13 16:26:15.789 warn getWebApi(): Error retrieving logs: 401 - {"detailMessage":"Your access token is not authorized","stackTrace":[],"suppressedExceptions":[]}
nuki-extended.0 2022-12-13 16:26:15.537 warn getWebApi(): Error retrieving logs: 401 - {"detailMessage":"Your access token is not authorized","stackTrace":[],"suppressedExceptions":[]}
nuki-extended.0 2022-12-13 16:26:15.294 warn getWebApi(): Error retrieving logs: 401 - {"detailMessage":"Your access token is not authorized","stackTrace":[],"suppressedExceptions":[]}
nuki-extended.0 2022-12-13 16:26:15.132 warn getWebApi(): Error retrieving notifications: 401 - {"detailMessage":"Your access token is not authorized","stackTrace":[],"suppressedExceptions":[]}

Versions:

  • Adapter version: 2.6.5
  • JS-Controller version: 4.0.23 and 4.0.21
  • Node version: 16.18.0 and 14.19.0
  • Operating system: linux & docker
@manoloxxl
Copy link
Author

Nobody else?

@Kroate
Copy link

Kroate commented Jan 17, 2023

Same Problem here......

@manoloxxl
Copy link
Author

Same Problem here......

Let's check if there are same environments:

  • Are you using the token generated by the bridge or by the web api?
  • do you have more than one bridge in yout network

@JamesBHof
Copy link

JamesBHof commented Jan 28, 2023

Same problem.
I'm using the "long" token from web api and one bridge in network (Smart Lock 3.0).

I found this warining in log:

getWebApi(): Error retrieving smartlocks: Cannot read properties of undefined (reading 'toLowerCase')

@manoloxxl
Copy link
Author

I‘ve removed the long token and now just use the local bridge token - error message is not longer visible. The problem seems to be the web API / long token.

I think, the manual and the gui should be updated with the information that only one of both is necessary and maybe also a hint why (or when) should be the local or the long web API key.

for a newbie the wiki is unclear - I’m pretty sure I’m not the only one that used both options - which is not useful/ necessary.

@mcm1957 mcm1957 added the documentation Improvements or additions to documentation label Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants