Settings → Accounts shows activated but there is no account settings option.
Google suggests creating a log entry which I can do but no login prompt and the entry is not saved.
So how can I force 4.5 to login to my Rosepoint account?
Settings → Accounts shows activated but there is no account settings option.
Google suggests creating a log entry which I can do but no login prompt and the entry is not saved.
So how can I force 4.5 to login to my Rosepoint account?
When the Coastal Explorer v4.5 beta is installed on a PC that has an activated Coastal Explorer license, the beta will automatically sign-in to the account associated with that license.
In that case, the Account Settings button does not appear in “Settings > Accounts” (but it probably should). If you need to get to your account settings, you can get there from the user menu on www.rospoint.com.
I’m not sure what you mean by Google suggesting you create a log entry…
The problem is that 4.5 is not signed in. It does not ask for a login. It does want me to buy a subscription but as I understand it I don’t need one other than for the Android version. Google suggested to create a log entry for force a login prompt. No joy.
So 4.5 is not logged into my Rosepoint account. If that is supposed to be automatic its not working for me. Version 4 works fine
.
I think we figured out what went wrong and will be releasing an update later today that should fix this.
Thanks, i like the look of what I can see in 4.5 so far.
Thanks, that’s good to hear!
We just released an update that I hope will fix the problem you ran into.
It does but it crashes when configuring a UDP NMEA stream.
Uninstall and installing again does not fix it. Is there a ini file or something I can remove to get 4.5 running? Find and grep doesn’t turn up anything useful.
That’s odd…we just fixed that in this release, or least we did on a bunch of other systems.
Unfortunately there is not a file that can be removed to fix this. Can you disconnect from the network or turn off whatever is broadcast to that port? That should let you remove the port with the UI.
If you are able to do that, could you send us your application log so we can troubleshoot it? Once Coastal Explorer is running again, you can get to the log by using the Search browser to look for $data which will open a file explorer on a folder containing a “PreviousApplication.log” file which should be the log from the run that crashed.
With not net connection I get a login page. Supplying credentials starts 4.5 an then crashes. Now that I know the file name I can access it.
Uncaught exception: undefined RangeError [ERR_SOCKET_BAD_PORT]: Port should be > 0 and < 65536. Received type number (101101457). I had entered 1457 but I had not cleared the previous entry. Should be an easy fix.
cat AppData/Roaming/Coastal\ Explorer\ (Beta)/PreviousApplication.log
[2026-06-08 18:46:13.382] [info] [Main Process] Platform: win32
[2026-06-08 18:46:13.388] [info] [Main Process] User data directory: C:\Users\jc\AppData\Roaming\Coastal Explorer (Beta)
[2026-06-08 18:46:13.389] [info] [Main Process] Main process VITE_APP_VARIANT: coastal-explorer
[2026-06-08 18:46:13.461] [info] [Main Process] Renderer logging set up at log level ‘INFO’
[2026-06-08 18:46:13.487] [info] [Main Process] Loading window state from “C:\Users\jc\AppData\Roaming\Coastal Explorer (Beta)\mainWindow.json”
[2026-06-08 18:46:13.492] [info] [Main Process] wss listening on {“address”:“::”,“family”:“IPv6”,“port”:56951}
[2026-06-08 18:46:13.514] [info] [Main Process] {
“fullScreen”: false,
“maximized”: false,
“bounds”: {
“x”: 214,
“y”: 81,
“width”: 1029,
“height”: 772
}
}
[2026-06-08 18:46:14.328] [info] [Renderer DEBUG] using 1017 as screen width
[2026-06-08 18:46:14.628] [info] [Renderer DEBUG] Setting renderer log level to info
[2026-06-08 18:46:14.630] [info] [Renderer INFO] Version: 4.5.0-260608202940.beta
[2026-06-08 18:46:14.633] [info] [Renderer INFO] Version date: 260608202940
[2026-06-08 18:46:14.635] [info] [Renderer INFO] Build commit: 20dbebd13e5bb2a9144b358d5b456f761e33173a
[2026-06-08 18:46:14.637] [info] [Renderer INFO] App variant: coastal-explorer
[2026-06-08 18:46:14.639] [info] [Renderer INFO] App variant is locked: true
[2026-06-08 18:46:15.331] [info] [Renderer INFO] Electron product store is not yet implemented.
[2026-06-08 18:46:15.396] [info] [Main Process] Offline database located at: C:\Users\jc\AppData\Roaming\Coastal Explorer (Beta)\offlineRegion.db
[2026-06-08 18:46:15.403] [info] [Main Process] discoverer: loading gofree…
[2026-06-08 18:46:15.408] [info] [Main Process] GoFree: starting…
[2026-06-08 18:46:15.410] [info] [Main Process] discoverer: loading ssdp…
[2026-06-08 18:46:15.421] [info] [Main Process] Network: WiFi address 10.1.58.91
[2026-06-08 18:46:15.423] [info] [Main Process] M-SEARCH: Searching for urn:rosepointnav-com:service:nemo:1…
[2026-06-08 18:46:15.426] [info] [Main Process] M-SEARCH: Searching for urn:axis-com:service:BasicService:1…
[2026-06-08 18:46:15.431] [info] [Main Process] udpGateway: 101101457
[2026-06-08 18:46:15.440] [info] [Main Process] listening
[2026-06-08 18:46:15.455] [info] [Main Process] Using Velopack update path: https://planz-updates.sfo3.cdn.digitaloceanspaces.com/velopack/coastal-explorer
[2026-06-08 18:46:15.460] [info] [Main Process] Using Velopack update channel: windows-x64
[2026-06-08 18:46:15.472] [info] [Main Process] Using Velopack update channel: windows-x64
[2026-06-08 18:46:16.427] [info] [Main Process] M-SEARCH: Done waiting on urn:rosepointnav-com:service:nemo:1 closing socket
[2026-06-08 18:46:16.448] [info] [Main Process] M-SEARCH: Done waiting on urn:axis-com:service:BasicService:1 closing socket
[2026-06-08 18:46:16.520] [error] [Main Process] Uncaught exception: undefined RangeError [ERR_SOCKET_BAD_PORT]: Port should be > 0 and < 65536. Received type number (101101457).
at Socket.send (node:dgram:672:12)
at WebSocket. (file:///C:/Users/jc/AppData/Local/com.rosepoint.planz/current/resources/app.asar/index.mjs:2736:66)
at WebSocket.emit (node:events:509:28)
at Receiver.receiverOnMessage (C:\Users\jc\AppData\Local\com.rosepoint.planz\current\resources\app.asar\node_modules\ws\lib\websocket.js:1239:20)
at Receiver.emit (node:events:509:28)
at Receiver.dataMessage (C:\Users\jc\AppData\Local\com.rosepoint.planz\current\resources\app.asar\node_modules\ws\lib\receiver.js:650:14)
at Receiver.getData (C:\Users\jc\AppData\Local\com.rosepoint.planz\current\resources\app.asar\node_modules\ws\lib\receiver.js:534:10)
at Receiver.startLoop (C:\Users\jc\AppData\Local\com.rosepoint.planz\current\resources\app.asar\node_modules\ws\lib\receiver.js:189:16)
at Receiver._write (C:\Users\jc\AppData\Local\com.rosepoint.planz\current\resources\app.asar\node_modules\ws\lib\receiver.js:116:10)
at writeOrBuffer (node:internal/streams/writable:570:12)
Now that I know the directory to remove 4.5 is running.
Thanks for the log! I’m happy to see this is a very different problem than what we fixed, but am surprised that you didn’t get an error message when configuring the port. We’ll get an update out ASAP that will get you going again…it should only take a few minutes.
I just noticed you got it running before I sent my last message… That’s great! We did just make another update available to fix the crashing in case invalid port numbers are used again.