Skipper never connects to signalk on windows

[alexrhyshurn]

Describe the bug
On initial run, the connection wizard detects signalk server, but will never connect to it, either with or without authentication request.

To Reproduce
Steps to reproduce the behavior:

1. Start Skipper
2. Select the signalk server in the list of detected server
3. Click Connect
4. Watch skipper app "initializing connection to signal k server" for ever.

Expected behavior
Skipper should connect to signalk

Screenshots

Desktop (please complete the following information):

• OS: Windows 11
• Firefox browser

Additional context
Same problem exists with either authenticated or unauthenticated sessions.

Tested against signalk 2.19.1 and 2.30.0 I have two signalk servers.

Thank you,
Alex

[JohnySeven]

Hi Alex,

I've just released new version 26, can you please download it and try it again with new version?

Link is here: https://docs.skipperapp.net/SkipperApp_1.26.19.msi

Thank you!
Jan

[alexrhyshurn]

The bug report I filed is in fact against version 1.26.19 so that is what I am using, as I only installed it this morning. Sorry I did not put version in bug report.

Thank you,
Alex

[JohnySeven]

Ok, let me check with my own setup if not I'll need logs to understand what is wrong. Using Windows for development of SKipper and didn't notice any issues.

[JohnySeven]

I've updated my test server to Signal K latest 2.30 and it works fine for me. Can you try to type your server address manually? Windows needs Bojour service for mDNS work correctly (here download link: https://support.apple.com/en-us/106380).

So, if you're using DNS like myawesomepi.local it might have issue finding that DNS name.

If that doesn't work for you I'll need SKipper logs to correctly analyze the issue you have.

[alexrhyshurn]

Hi,

Using Skipper App v.1.26.19 on windows 11.

I have two signalk servers.
1: Running on Victron Cerbo v2.19.0, running on port 3000 with MDNS / Avahi - detected fine
2: Running on Raspberry Pi v2.30.0 with self signed HTTPS certificate on port 80 - not detected

I have tried on both of them to "type" address. In the case of number two it does prompt about the self signed certificate but still never connects.

I have the same behaviour if I type address, or if I select a server from list. Same behaviour if it is with HTTPS or without. Same behaviour if I select read only or not.

If I click cancel then it returns to the server selection screen.

If I exit the skipper app and start it again, then the first time start wizard begins, and I must choose installation name, units etc.

I am happy to send logs, please direct me how to do it, as I never see any settings or place to do the "paste" function. I am stuck in the first start wizard so I never have access to the screen in the documentation below:

Many thanks for your patience,

Alex

[JohnySeven]

There is a tip in onboarding mode for enabling logs.

1. When you tap/click on SKipper logo it will show you SKipper about modal, where you can turn on logs. So, enable them at start before doing anything like connecting.
2. Then try to connect to server and again tap/click on SKipper logo to use share button and share the link with me.

No worries, I thank you for your patience and getting back to me with this issue!

Appreciated!

[alexrhyshurn]

Hi,
Sorry I didn't see that. Please clarify this option in the documentation.

Here is a paste of the logs taken after pressing connect:

https://paste.skipperapp.net/get/cpdx4

Also sent via email

Alex

[erikjber]

I have this exact same problem (SKipper never connects after selecting a server) on both Android and Linux. Android version 1.26.19. Linux version 1.26.19. Both versions installed a couple of hours ago.

I am running Signal K version 2.30.0 on a Raspberry Pi. There are no access requests in Signal K. Nothing shows up in the Signal K log when I try to connect the SKipper clients.

[JohnySeven]

Hi Erik,

I'm sorry for any inconvenience caused.

I am running Signal K version 2.30.0 on a Raspberry Pi. There are no access requests in Signal K. Nothing shows up in the Signal K log when I try to connect the SKipper clients.

I'm working on the fix, can I ask you for logs? I just want to make sure you hit the same issue as Alex, did.

Here are steps to gather logs.

When you tap/click on SKipper logo it will show you SKipper about modal, where you can turn on logs. So, enable them at start before doing anything like connecting.
Then try to connect to server and again tap/click on SKipper logo to use share button and share the link with me.
No worries, I thank you for your patience and getting back to me with this issue!

Appreciated!

[JohnySeven]

@alexrhyshurn I see from your screenshots you're connecting with "readonly-mode" that check box that appears above list of servers. Can you try to uncheck this and connect to your server? It should create new access request in Signal K.

@erikjber can you verify the same? Do you try to connect "Use Signal K in read-only mode" or do you use access request mode (checkbox unchecked)?

Thank you both, bug is fixed for read-only mode!

[erikjber]

@erikjber can you verify the same? Do you try to connect "Use Signal K in read-only mode" or do you use access request mode (checkbox unchecked)?

I have tried both read-only and access request mode. The result is the same: SKipper hangs on the "initializing connection to Signal K server" screen.

When you tap/click on SKipper logo it will show you SKipper about modal, where you can turn on logs. So, enable them at start before doing anything like connecting.

Are those instructions for Android? If there is a way to turn on logs on Linux, that would make this a lot simpler.

[JohnySeven]

@erikjber

I have tried both read-only and access request mode. The result is the same: SKipper hangs on the "initializing connection to Signal K server" screen.

You might be hitting something else then.

Are those instructions for Android? If there is a way to turn on logs on Linux, that would make this a lot simpler.

Yes, Android, Linux, Windows and even iOS. For Linux you can run the SKipper from terminal, and send me the output. Just open your Terminal and run this command:

/usr/local/bin/skipper/SkipperApp --console-log

And send me the output to investigate.

Thank you!