adam/Remote-Terminal-for-MeshCore
1
0 Fork 0
mirror of https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git synced 2026-11-03 08:02:19 +01:00
Code Issues 26 Packages Projects Releases Wiki Activity

Failed to export private key #6

New Issue
Closed
opened 2026-10-05 01:51:50 +02:00 by adam · 12 comments
adam commented 2026-10-05 01:51:50 +02:00
Owner
Copy link
Copy source

Attempting to run this for the first time on Windows, using the PS command: $env:MESHCORE_SERIAL_PORT="COM3"; uv run uvicorn app.main:app --host 0.0.0.0 --port 8000

This is what I see after that:

INFO:     Started server process [30344]
INFO:     Waiting for application startup.
INFO:app.database:Connecting to database at data/meshcore.db
INFO:app.main:Database connected
INFO:meshcore:Serial Connection started
INFO:app.main:Connected to radio
INFO:app.event_handlers:Event handlers registered
INFO:app.keystore:Exporting private key from radio...
ERROR:app.keystore:Failed to export private key: {'reason': 'no_event_received'}
INFO:app.radio:Syncing and offloading radio data...```

Then it just hangs there.

<!-- github-sync-id:3981881776 -->
Attempting to run this for the first time on Windows, using the PS command: `$env:MESHCORE_SERIAL_PORT="COM3"; uv run uvicorn app.main:app --host 0.0.0.0 --port 8000` This is what I see after that: ```INFO:app.frontend_static:Serving frontend from C:\Users\alanr\src\Remote-Terminal-for-MeshCore\frontend\dist INFO: Started server process [30344] INFO: Waiting for application startup. INFO:app.database:Connecting to database at data/meshcore.db INFO:app.main:Database connected INFO:meshcore:Serial Connection started INFO:app.main:Connected to radio INFO:app.event_handlers:Event handlers registered INFO:app.keystore:Exporting private key from radio... ERROR:app.keystore:Failed to export private key: {'reason': 'no_event_received'} INFO:app.radio:Syncing and offloading radio data...``` Then it just hangs there. <!-- github-sync-id:3981881776 -->
adam closed this issue 2026-10-05 01:51:50 +02:00
adam commented 2026-10-05 01:51:51 +02:00
Author
Owner
Copy link
Copy source

Hm, which firmware are you using? Are you certain it's client firmware (not repeater or room server)? This can happen for certain firmwares that don't permit privkey export, but I haven't had a ton of experience with that (the ones I use are the default meshcore.co.uk firmwares, which generally all permit that) Firmwares should behave with RemoteTerm even if they don't permit key export (although the main value prop of RemoteTerm is lost, but the core messaging will still work).

Hm, which firmware are you using? Are you certain it's client firmware (not repeater or room server)? ~~This can happen for certain firmwares that don't permit privkey export, but I haven't had a ton of experience with that (the ones I use are the default meshcore.co.uk firmwares, which generally all permit that)~~ Firmwares should behave with RemoteTerm even if they don't permit key export (although the main value prop of RemoteTerm is lost, but the core messaging will still work). <!-- github-comment-id:3949600780 -->
adam commented 2026-10-05 01:51:52 +02:00
Author
Owner
Copy link
Copy source

This also may be an issue with port assignment; to be totally honest, I haven't run this code on a Windows platform since starting development. I'll see if I can repro, but checking if your radio behaves on a *nix/Mac platform may be a helpful way to rule out radio issues as opposed to OS level issues (which I would love to fix, but will need to reproduce before I can target).

This also may be an issue with port assignment; to be totally honest, I haven't run this code on a Windows platform since starting development. I'll see if I can repro, but checking if your radio behaves on a *nix/Mac platform may be a helpful way to rule out radio issues as opposed to OS level issues (which I would love to fix, but will need to reproduce before I can target). <!-- github-comment-id:3949928255 -->
adam commented 2026-10-05 01:51:52 +02:00
Author
Owner
Copy link
Copy source

Hm, which firmware are you using? Are you certain it's client firmware (not repeater or room server)?

I'm using a Heltec v3. No GPS module

> Hm, which firmware are you using? Are you certain it's client firmware (not repeater or room server)? I'm using a Heltec v3. No GPS module <!-- github-comment-id:3953113148 -->
adam commented 2026-10-05 01:51:53 +02:00
Author
Owner
Copy link
Copy source

This also may be an issue with port assignment; to be totally honest, I haven't run this code on a Windows platform since starting development. I'll see if I can repro, but checking if your radio behaves on a *nix/Mac platform may be a helpful way to rule out radio issues as opposed to OS level issues (which I would love to fix, but will need to reproduce before I can target).

I don't have a Mac, and the machine I plan to use this on is Windows, so I'll have to wait til I can get past this bug.

> This also may be an issue with port assignment; to be totally honest, I haven't run this code on a Windows platform since starting development. I'll see if I can repro, but checking if your radio behaves on a *nix/Mac platform may be a helpful way to rule out radio issues as opposed to OS level issues (which I would love to fix, but will need to reproduce before I can target). I don't have a Mac, and the machine I plan to use this on is Windows, so I'll have to wait til I can get past this bug. <!-- github-comment-id:3953131650 -->
adam commented 2026-10-05 01:51:54 +02:00
Author
Owner
Copy link
Copy source

I've got my radio up and running on Windows, so I don't think this is a consistent issue with Windows.

Where is your firmware sourced from? Exactly what version are you on? Have you triple-checked that you're on the client firmware?

https://app.meshcore.nz/ should definitely work for you. If you can't connect via that application, then it is an issue with your radio and not with RemoteTerm.

I've got my radio up and running on Windows, so I don't think this is a consistent issue with Windows. Where is your firmware sourced from? Exactly what version are you on? Have you triple-checked that you're on the client firmware? https://app.meshcore.nz/ should definitely work for you. If you can't connect via that application, then it is an issue with your radio and not with RemoteTerm. <!-- github-comment-id:3953182530 -->
adam commented 2026-10-05 01:51:55 +02:00
Author
Owner
Copy link
Copy source

Did this resolve for you? Were you able to reflash firmware and confirm version/standard client firmware from meshcore.co.uk?

Did this resolve for you? Were you able to reflash firmware and confirm version/standard client firmware from meshcore.co.uk? <!-- github-comment-id:3968802135 -->
adam commented 2026-10-05 01:51:55 +02:00
Author
Owner
Copy link
Copy source

I flashed the Heltec v3 with the latest from the MC website, and I confirmed it connects and works properly with https://app.meshcore.nz. However, it's still not able to see the radio. Here's what I get when I run set MESHCORE_SERIAL_PORT=COM3; uv run uvicorn app.main:app --host 0.0.0.0 --port 8000

PS C:\Users\alanr\src\Remote-Terminal-for-MeshCore> set MESHCORE_SERIAL_PORT=COM3; uv run uvicorn app.main:app --host 0.0.0.0 --port 8000
INFO:app.frontend_static:Serving frontend from C:\Users\alanr\src\Remote-Terminal-for-MeshCore\frontend\dist
INFO:     Started server process [16416]
INFO:     Waiting for application startup.
INFO:app.database:Connecting to database at data/meshcore.db
INFO:app.main:Database connected
INFO:app.radio:No serial port specified, auto-detecting...
WARNING:app.radio:No serial devices found
WARNING:app.main:Failed to connect to radio on startup: No MeshCore radio found. Please specify MESHCORE_SERIAL_PORT.
INFO:app.radio:Radio connection monitor started
INFO:     Application startup complete.
INFO:     Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit)
INFO:app.radio:Attempting to reconnect to radio...
INFO:app.radio:No serial port specified, auto-detecting...
WARNING:app.radio:No serial devices found
WARNING:app.radio:Reconnection failed: No MeshCore radio found. Please specify MESHCORE_SERIAL_PORT.
I flashed the Heltec v3 with the latest from the MC website, and I confirmed it connects and works properly with https://app.meshcore.nz. However, it's still not able to see the radio. Here's what I get when I run `set MESHCORE_SERIAL_PORT=COM3; uv run uvicorn app.main:app --host 0.0.0.0 --port 8000` ``` PS C:\Users\alanr\src\Remote-Terminal-for-MeshCore> set MESHCORE_SERIAL_PORT=COM3; uv run uvicorn app.main:app --host 0.0.0.0 --port 8000 INFO:app.frontend_static:Serving frontend from C:\Users\alanr\src\Remote-Terminal-for-MeshCore\frontend\dist INFO: Started server process [16416] INFO: Waiting for application startup. INFO:app.database:Connecting to database at data/meshcore.db INFO:app.main:Database connected INFO:app.radio:No serial port specified, auto-detecting... WARNING:app.radio:No serial devices found WARNING:app.main:Failed to connect to radio on startup: No MeshCore radio found. Please specify MESHCORE_SERIAL_PORT. INFO:app.radio:Radio connection monitor started INFO: Application startup complete. INFO: Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit) INFO:app.radio:Attempting to reconnect to radio... INFO:app.radio:No serial port specified, auto-detecting... WARNING:app.radio:No serial devices found WARNING:app.radio:Reconnection failed: No MeshCore radio found. Please specify MESHCORE_SERIAL_PORT. ``` <!-- github-comment-id:3977289990 -->
adam commented 2026-10-05 01:51:56 +02:00
Author
Owner
Copy link
Copy source

Hmmm that's a step backwards from your earlier syntax; that log indicates that the env var is not being passed through but the one in your original message was.

Could you open powershell and run

winget install usbipd

then restart powershell and run

usbipd list

This should tell us more about how your radio is appearing on the system.

Hmmm that's a step backwards from your earlier syntax; that log indicates that the env var is not being passed through but the one in your original message was. Could you open powershell and run ``` winget install usbipd ``` then restart powershell and run ``` usbipd list ``` This should tell us more about how your radio is appearing on the system. <!-- github-comment-id:3977485459 -->
adam commented 2026-10-05 01:51:57 +02:00
Author
Owner
Copy link
Copy source

Checking back in with this -- any updates?

Checking back in with this -- any updates? <!-- github-comment-id:4002613856 -->
adam commented 2026-10-05 01:51:57 +02:00
Author
Owner
Copy link
Copy source

FWIW I have also found some issues with windows usage that I have put something of a bounty on in the README.md in https://github.com/jkingsman/Remote-Terminal-for-MeshCore/blob/main/README.md#backend, but troubleshooting it is outside my understanding, and, most importantly, the problems I encountered don't align with the issues you were seeing.

I used to be an all-Windows user, so I do care about getting this fixed, but if I can't repro/my repro is different than yours, I don't know that there's all that much meaningful action I can take on this problem.

I cringe as I say this, but have you considered WSL2? It's been such a boon/my main development env for the last few years, and I do address how to get windows COM ports punched through to it in the readme :badpokerface:

FWIW I have also found some issues with windows usage that I have put something of a bounty on in the README.md in https://github.com/jkingsman/Remote-Terminal-for-MeshCore/blob/main/README.md#backend, but troubleshooting it is outside my understanding, and, most importantly, the problems I encountered don't align with the issues you were seeing. I used to be an all-Windows user, so I do care about getting this fixed, but if I can't repro/my repro is different than yours, I don't know that there's all that much meaningful action I can take on this problem. I cringe as I say this, but have you considered WSL2? It's been such a boon/my main development env for the last few years, and I do address how to get windows COM ports punched through to it in the readme :badpokerface: <!-- github-comment-id:4002633308 -->
adam commented 2026-10-05 01:51:58 +02:00
Author
Owner
Copy link
Copy source

Apologies for the delay. Yes I did get it fixed! I ended up having to install usbipd, so I could assign that port to WSL... or something like that. I got this working, so thanks for following up!

Apologies for the delay. Yes I did get it fixed! I ended up having to install usbipd, so I could assign that port to WSL... or something like that. I got this working, so thanks for following up! <!-- github-comment-id:4005911391 -->
adam commented 2026-10-05 01:51:59 +02:00
Author
Owner
Copy link
Copy source

Eyyyy glad things are working for you 🙂

Eyyyy glad things are working for you 🙂 <!-- github-comment-id:4006247796 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#6