I installed V3.60 from V3.55 and noticed I lost NFL tracking via SignalK. Checking via Venus local I got the banner message you probably don’t have internet connectivity and the appstore showed offline in red. I reverted to V3.55 and all was working again including the NFL plugin. I then reloaded V3.60 and have the same problem again. Any thoughts to force connectivity. I haven’t had to make any internet connection settings in the past. SignalK server Version 2.13.5.
TIA
I have this same issue - was working then just stopped for appstore says offline, and NFL stopped updating.
However AISforwarder and SK to Windy are working fine. Tried previous fw (3.65) same issue.
Log error for NFL
Nov 02 21:57:30 2025-11-02T21:57:30.408Z signalk-to-noforeignland Could not send track to API due to error: FetchError: request to https://www.noforeignland.com/home/api/v1/boat/tracking/track failed, reason: at ClientRequest. (/data/conf/signalk/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:518:28) at emitErrorEvent (node:_http_client:101:11) at TLSSocket.socketErrorListener (node:_http_client:504:5) at TLSSocket.emit (node:events:518:28) at emitErrorNT (node:internal/streams/destroy:169:8) at emitErrorCloseNT (node:internal/streams/destroy:128:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { type: ‘system’, errno: ‘ETIMEDOUT’, code: ‘ETIMEDOUT’ }
Did you ever find a solution?
Hi Matt,
I never got a solution to get 3.60 to operate with SK and NFL. However either by luck or by design it appears Victron have repaired things as all works fine with 3.66 now for me. Sorry I have no more than that.
BTW do you find any issues with the Windy or AISForwarder plugins?
I updated to latest beta firmware and that fixed store issue for me.
NFL - worked with developer to find a fix
Windy - had to make sure the units were correct as per Windy stations guidelines, then worked fine. Also populated the name and url fields which seemed to make it work better.
AIS forwarder - only issue I had was the data stream from multiplexor I use didn`t have VDO (AIS own position) statement - was reporting other vessels, but mine did not update.
I was going to install another AIS reporter plugin to report own position, but ended up configuring a stream from the Vesper AIS that included the VDO and all working fine now.
That’s interesting that your fix came from NFL not Victron. Glad you got it sorted. Hopefully future updates dont corrupt our NFL plugins again. Thanks re Windy and AISForwarder. Fair winds!