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

Appstore not loading #1767

Open
Colug0 opened this issue Jul 25, 2024 · 3 comments
Open

Appstore not loading #1767

Colug0 opened this issue Jul 25, 2024 · 3 comments

Comments

@Colug0
Copy link

Colug0 commented Jul 25, 2024

When I log in with admin creds in my SignalK Server and navigate to the "Appstore", only an empty list is displayed (selected "All" and nothing in the search field). Also If I click on "Server -> Update" the following message is displayed: "Waiting for App Store data to load..."

I tried to restart the SignalK Server and the Raspberry Pi 4, on which the SignalK Server runs. SignalK was installed via Openplotter.

I am looking for ideas on what I could check/do.

@tkurki
Copy link
Member

tkurki commented Jul 27, 2024

The app store data is coming from npmjs.com, more specifically from the api https://registry.npmjs.org/-/v1/search?size=250&text=keywords:signalk-webapp (for webapps). You can try loading that url from your boat to check basis connectivity to npmjs.

The api is accessed from the Signal K server, so even if you can connect to this for example from your phone or tablet on the boat network the server may not be able to do so. Using a browser or for example curl running on the same machine as the server give the definitive answer for connectivity.

People have reported that restarting their linux installation has fixed their app store related problems.

Reports of app store loading problems have been increasing lately. We could tweak the way the app store data is loaded, eagerly and periodically but on demand when the app store is loaded, but there is no really good strategy here. Sometimes people want the module that was just released, and with cached data the update won't be there.

@fmt871
Copy link

fmt871 commented Nov 1, 2024

I have the same issue. Basis connectivity to npmjs with no issues.
Looking for solutions. Thx.
Server log:
Nov 01 13:30:32 signalk-server running at 0.0.0.0:[object Object]
Nov 01 13:30:33 GET /signalk/v1/api/vessels/self 200 38.015 ms - -
Nov 01 13:30:33 [object Object]
Nov 01 15:18:41 1 Nov 15:18:41 - [info] Welcome to Node-RED ===================
Nov 01 15:18:41 1 Nov 15:18:41 - [info] Node-RED version: v3.1.11
Nov 01 15:18:41 1 Nov 15:18:41 - [info] Node.js version: v18.17.1
Nov 01 15:18:41 1 Nov 15:18:41 - [info] Linux 6.6.58-v8+ arm64 LE
Nov 01 15:18:41 GET /signalk/v1/api/vessels/self 200 29.412 ms - -
Nov 01 15:18:42 1 Nov 15:18:42 - [info] Loading palette nodes
Nov 01 15:18:44 1 Nov 15:18:44 - [info] Dashboard version 3.6.5 started at /plugins/signalk-node-red/redApi/ui
Nov 01 15:18:45 1 Nov 15:18:45 - [info] Context store : 'default' [module=memory]
Nov 01 15:18:45 1 Nov 15:18:45 - [info] User directory : /home/fmt871/.signalk/red
Nov 01 15:18:45 1 Nov 15:18:45 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
Nov 01 15:18:45 1 Nov 15:18:45 - [warn] Flows file name not set. Generating name using hostname.
Nov 01 15:18:45 1 Nov 15:18:45 - [info] Flows file : /home/fmt871/.signalk/red/flows_vayu.json
Nov 01 15:18:45 unable to check for new server version: FetchError: request to http://registry.npmjs.org/-/package/signalk-server/dist-tags failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org
Nov 01 15:18:45 1 Nov 15:18:45 - [info] Creating new flow file
Nov 01 15:18:45 1 Nov 15:18:45 - [warn] Encrypted credentials not found
Nov 01 15:18:45 1 Nov 15:18:45 - [info] Starting flows
Nov 01 15:18:45 1 Nov 15:18:45 - [info] Started flows
Nov 01 15:19:30 GET / 302 12.399 ms - 58
Nov 01 15:19:30 GET /admin/ 200 22.317 ms - 562
Nov 01 15:19:30 GET /@signalk/vesselpositions/remoteEntry.js 304 46.985 ms - -
Nov 01 15:19:30 GET /admin/main.js 304 24.942 ms - -
Nov 01 15:19:31 GET /admin/208.js 304 12.661 ms - -
Nov 01 15:19:31 GET /admin/144.js 304 10.263 ms - -
Nov 01 15:19:31 GET /admin/41.js 304 10.153 ms - -
Nov 01 15:19:31 GET /admin/259.js 304 6.715 ms - -
Nov 01 15:19:32 GET /skServer/loginStatus 200 10.177 ms - 205
Nov 01 15:19:32 GET /skServer/plugins 304 38.258 ms - -
Nov 01 15:19:32 GET /skServer/security/access/requests 304 10.429 ms - -
Nov 01 15:19:32 GET /skServer/webapps 304 32.532 ms - -
Nov 01 15:19:32 GET /skServer/addons 304 29.102 ms - -
Nov 01 15:19:32 GET /signalk 304 29.302 ms - -
Nov 01 15:19:32 GET /admin/fonts/signal-k-logo-image-text.d132ec2c4f0269c103c868aaa6868f01.svg 304 8.417 ms - -
Nov 01 15:19:32 GET /admin/fonts/Simple-Line-Icons.3826fa1cb2348dd93948a50cbd2b8fb6.woff2 304 9.886 ms - -
Nov 01 15:19:33 GET /admin/fonts/fa-solid-900.1551f4f60c37af51121f106501f69b80.woff2 304 6.371 ms - -
Nov 01 15:20:30 GET /skServer/security/config 304 11.974 ms - -
Nov 01 15:20:45 GET /skServer/logfiles/ 304 14.253 ms - -
Nov 01 15:20:45 GET /skServer/debugKeys 200 5.902 ms - -
Nov 01 15:25:55 GET /skServer/appstore/available - - ms - -
Nov 01 15:33:08 GET / 302 8.787 ms - 58
Nov 01 15:33:08 GET /admin/ 200 14.370 ms - 562
Nov 01 15:33:10 GET /@signalk/vesselpositions/remoteEntry.js 304 20.619 ms - -
Nov 01 15:33:10 GET /admin/main.js 304 16.608 ms - -
Nov 01 15:33:10 GET /admin/208.js 304 8.274 ms - -
Nov 01 15:33:10 GET /admin/41.js 304 8.474 ms - -
Nov 01 15:33:10 GET /admin/144.js 304 8.797 ms - -
Nov 01 15:33:10 GET /admin/259.js 304 14.592 ms - -
Nov 01 15:33:11 GET /skServer/appstore/available 401 7.256 ms - 91
Nov 01 15:33:11 GET /skServer/loginStatus 200 4.485 ms - 168
Nov 01 15:33:11 GET /skServer/plugins 401 2.646 ms - 91
Nov 01 15:33:11 GET /skServer/security/access/requests 401 1.729 ms - 91
Nov 01 15:33:11 GET /skServer/webapps 304 10.495 ms - -
Nov 01 15:33:11 GET /skServer/addons 304 6.851 ms - -
Nov 01 15:33:11 GET /signalk 304 32.902 ms - -
Nov 01 15:33:11 GET /admin/fonts/signal-k-logo-image-text.d132ec2c4f0269c103c868aaa6868f01.svg 304 2.368 ms - -
Nov 01 15:33:11 GET /admin/fonts/Simple-Line-Icons.3826fa1cb2348dd93948a50cbd2b8fb6.woff2 304 5.229 ms - -
Nov 01 15:33:12 GET /admin/fonts/fa-solid-900.1551f4f60c37af51121f106501f69b80.woff2 304 1.754 ms - -
Nov 01 15:33:30 POST /signalk/v1/auth/login 401 324.803 ms - 56
Nov 01 15:33:41 POST /signalk/v1/auth/login 200 278.882 ms - 136
Nov 01 15:33:41 GET /skServer/plugins 304 44.764 ms - -
Nov 01 15:33:41 GET /skServer/loginStatus 200 7.614 ms - 205
Nov 01 15:33:41 GET /skServer/webapps 304 32.689 ms - -
Nov 01 15:33:41 GET /skServer/addons 304 26.726 ms - -
Nov 01 15:33:41 GET /skServer/security/access/requests 304 7.056 ms - -
Nov 01 15:33:41 GET /signalk 304 17.192 ms - -
Nov 01 15:33:50 GET /skServer/security/config 304 9.681 ms - -
Nov 01 15:33:58 GET /skServer/logfiles/ 304 26.448 ms - -
Nov 01 15:33:58 GET /skServer/debugKeys 304 10.225 ms - -

@tkurki
Copy link
Member

tkurki commented Nov 4, 2024

EAI_AGAIN means that dns lookup is failing for registry.npmjs.org on your server.

When you say Basis connectivity to npmjs with no issues how did you check that? Did you try to restart sk server or the machine where it is running?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants