Access token should be removed if the token has been deleted from the server

[nadrog]

Hi,

with fresh SignalK server installation and SensESP 2.1.1, my SailorHat is trying to authenticate with SignalK server (that was succesfully found). SK connection status on SensESP is "Authorizing with SignalK" and debug message is "(C1) Attempting to connect to Signal K Websocket...", but I do not know what I need to do to authenticate this new device with SignalK server. Please, point me to appropriate documentation. Thanks!

Gordan

[nadrog]

Further info: "Allow New Device Registration" is enabled in SignalK and there is no inputs in "Access Requests"

[nadrog]

I used the approach defined in an old version of Troubleshooting page found on Way Back Machine (https://web.archive.org/web/20211217183358/https://github.com/SignalK/SensESP/wiki/Troubleshooting). Can you please add this info back? Thanks!

[mairas]

I was just going to comment that resetting the device might help. But nevertheless, the same troubleshooting information still exists: https://signalk.org/SensESP/pages/troubleshooting/. Instead of writing elaborate workaround instructions for bugs that I myself can't reproduce, I'd prefer getting as detailed description of the bug and the environment so that the bug could be reproduced or at least narrowed down.

For that, could I get:

• Copy of the serial monitor output
• Server version
• Server configuration
• Related server log entries, if any

[mairas]

I have been able to reproduce similar behavior by removing the device access on the server side. The device doesn't recognize that the access has been removed and keeps on reconnecting with the old token.

[nadrog]

Hi Matti,

Yes, that’s how I got into this problem: I reinstalled the SignalK.

Br, G

From: Matti Airas @.> Sent: Saturday, February 12, 2022 11:49 AM To: SignalK/SensESP @.> Cc: nadrog @.>; Author @.> Subject: Re: [SignalK/SensESP] Authorizing with SignalK (Issue #552)

I have been able to reproduce similar behavior by removing the device access on the server side. The device doesn't recognize that the access has been removed and keeps on reconnecting with the old token.

— Reply to this email directly, view it on GitHub https://github.com/SignalK/SensESP/issues/552#issuecomment-1037129737 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABXQ476HQGGCXDJHZ63EGZDU2Y3ITANCNFSM5OE6YDPQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . You are receiving this because you authored the thread.Message ID: @.***>

[nadrog]

My problem was finding the troubleshooting section when I started from SensESP Git page. This could potentially be improved.

From: Matti Airas @.> Sent: Friday, February 11, 2022 10:31 PM To: SignalK/SensESP @.> Cc: nadrog @.>; Author @.> Subject: Re: [SignalK/SensESP] Authorizing with SignalK (Issue #552)

I was just going to comment that resetting the device might help. But nevertheless, the same troubleshooting information still exists: https://signalk.org/SensESP/pages/troubleshooting/. Instead of writing elaborate workaround instructions for bugs that I myself can't reproduce, I'd prefer getting as detailed description of the bug and the environment so that the bug could be reproduced or at least narrowed down.

For that, could I get:

• Copy of the serial monitor output
• Server version
• Server configuration
• Related server log entries, if any

— Reply to this email directly, view it on GitHub https://github.com/SignalK/SensESP/issues/552#issuecomment-1036641244 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABXQ47YYHRDDWAMGEBXS7OTU2V5ZNANCNFSM5OE6YDPQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . You are receiving this because you authored the thread.Message ID: @.***>

[mairas]

My problem was finding the troubleshooting section when I started from SensESP Git page. This could potentially be improved.

Maybe you could give more concrete suggestions how to improve on that? I think the documentation site is quite prominently linked to in the README, and also in the "About" sidebar text.

The wiki is deprecated and only used for the legacy v1 documentation. I just added a link to the documentation site on the wiki home page, though.

[nadrog]

I believe the link you just added is the only missing thing.

From: Matti Airas @.> Sent: Sunday, February 13, 2022 11:17 AM To: SignalK/SensESP @.> Cc: nadrog @.>; Author @.> Subject: Re: [SignalK/SensESP] Access token should be removed if the token has been deleted from the server (Issue #552)

My problem was finding the troubleshooting section when I started from SensESP Git page. This could potentially be improved.

Maybe you could give more concrete suggestions how to improve on that? I think the documentation site is quite prominently linked to in the README, and also in the "About" sidebar text.

The wiki is deprecated and only used for the legacy v1 documentation. I just added a link to the documentation site on the wiki home page, though.

— Reply to this email directly, view it on GitHub https://github.com/SignalK/SensESP/issues/552#issuecomment-1037988539 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABXQ47227J4WVYCJCJRHSPLU26AIXANCNFSM5OE6YDPQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . You are receiving this because you authored the thread.Message ID: @.***>

[mairas]

Accidentally closed; the actual reported issue remains unfixed.