Supervisor errors after update to 2023.03.1

Configuration
#1

After updating I notice my supervisor logs are full of repeating messages

23-03-07 22:35:34 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /addons/self/info
23-03-07 22:35:35 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /discovery
23-03-07 22:35:39 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /addons/self/options/config
23-03-07 22:35:40 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /addons/self/info
23-03-07 22:35:40 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /discovery
23-03-07 22:35:45 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /addons/self/options/config
23-03-07 22:35:45 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /addons/self/info
23-03-07 22:35:46 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /discovery
23-03-07 22:35:50 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /addons/self/options/config
23-03-07 22:35:51 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /addons/self/info
23-03-07 22:35:51 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /discovery
23-03-07 22:35:56 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /addons/self/options/config
23-03-07 22:35:56 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /addons/self/info

Any ideas how to fix ? I tried a full reboot but the errors come back, and I can’t see anyway to downgrade, is there no backup for the supervisor?

#2

Try repairing the supervisor.

ha supervisor repair
#3

Thanks, I tried that via the terminal & ssh addon web ui, it reported “Command completed successfully” but unfortunately logs still show

23-03-07 23:02:34 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /discovery
23-03-07 23:02:39 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /addons/self/options/config
23-03-07 23:02:39 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /addons/self/info
23-03-07 23:02:40 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /discovery
23-03-07 23:02:43 INFO (MainThread) [supervisor.supervisor] Repairing Supervisor 2023.03.1
23-03-07 23:02:43 INFO (MainThread) [supervisor.core] Finished repair of Supervisor Environment
23-03-07 23:02:45 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /addons/self/options/config
23-03-07 23:02:45 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /addons/self/info
23-03-07 23:02:46 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /discovery
23-03-07 23:02:51 ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /addons/self/options/config
#4

Try to go to your profile, cleanup in your tokens there , and log-out , then reboot from ha-console, and follow the start-up … (not restart , reboot host!)

#5

These are errors for system generated tokens, not user generated long lived access tokens available via your profile.

#6

I didn’t mean the “long-lived access token” they outlive me :slight_smile: … but the “log-in-token” …
If somthing messed it up, sometimes a log-out >login helps

08.03.2023_00.30.46_REC

Created 3 month ago < last used 6 hours ago, my thought is a i.e 3 month old token ( should maybe be “refreshed” by force :slight_smile:

And i assume there is no reason to have 20+ refresh-tokens 3-4-5 month old … they are NOT removed as the text says, i don’t really understand the purpose of having bunch of old tokens there

Anyway, a log-out, login sometimes solve something , and i would have tried that when i see such an error

#7

OK, I can try and clear these refresh tokens as long as it only affects log in/log out ?

#8

yeah it can’t hurt, i actually just cleaned out my self, had 10+ more than 3 month old, and not used for 3 month … i kept last month tokens, thou try to log out so you get a new … i don’t know what’s in these tokens, never bother to care about them, but as said, they can get corrupted or somehow mess up things, so you have to logout/login to solve it … not that i know it will help you, i didn’t have any problems with .23.03.1

#9

OK, so I had tokens going back 4 years, removed almost all except last 2, logged out, in again.

Then rebooted my Pi.

And, so far everything looks good :crossed_fingers:

#10

:grin: thats crazy , i wonder whether this (these) tokens is a “neglected” area, or just plain “forgotten”