Instance switcher is not able to find My Local Cert

(#3656) Bug Open: Confirmed

Reproduction steps

Set up an selfhost. Have it been fully Lan. With HTTPS. you will have to self-sign it using caddy. then try to login to it. i tested this on Linux. then I dual booted into windows

Observed behaviour

I put in my Lan IP having my Local Certificate installed on my computer. But it still was unable to connect. I got this error code in console. Which is shown in the evidence. I edited out my Lan IP even though I am aware no one can actually do anything with it. it's just for security anyway

Build information

Canary Desktop 2026.1008.32323, Web 2026.1008.32323, Windows 11 10.0.26300 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US

Platform

Windows, Linux

Evidence

[InstanceSelector] [Warn] Instance discovery failed for Error: Error invoking remote method 'desktop-runtime-config:resolve': DesktopRuntimeDiscoveryUnreachableError: No usable instance discovery document was served for https:// : https:// /.well-known/fluxer (unable to get local issuer certificate); https:// /api/.well-known/fluxer (unable to get local issuer certificate)
  1. Amethyst changed the status from Awaiting confirmation to Confirmed
  1. The pull request fluxer#3281 mentions this post Merged

8 comments

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote
Status changed from Needs triage to Awaiting confirmation
Fixed in desktop canary 2026.1008.190209. The app now trusts certificates installed in your system store, so an instance with a local certificate authority can be found. On Linux this also covers images, media and voice.
Comment by Hampus
HampusStaff 1 vote 2 replies
Canary Desktop 2026.1006.202846 seems like an older desktop build. Does the issue persist on a newer build?
Comment by Hampus
HampusStaff 1 vote 1 reply
This could also have been why you marked the other fixed bug, #3620, as not fixed.
Comment by Amethyst
I apologize I used the build i had before the selfhosting update to copy the build info. I have both the native and the old build open at the same time so i confused them. here is the correct build info. i will update it there also. The profiles were broken. it was fixed after last update. I forgot to mention it I apologize Canary Desktop 2026.1008.32323, Web 2026.1008.32323, Windows 11 10.0.26300 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US The latest build of canary doesn't have this working
Comment by Amethyst
Amethyst OP1 vote Still happening 3 replies
This is Kinda fixed? I am able to login but i still contain bugs that prevent me from using the instance in its entirety, still seems to be issue that is related due to the error
[Gateway] [Error] Gateway transport error Error: gateway websocket connect failed: IO error: invalid peer certificate: UnknownIssuer
    at eY.handleRouterEvent (79cdedbf4ebb9956.js:1:97473)
    at callback (79cdedbf4ebb9956.js:1:94755)
    at eZ.handleNativeEvent (79cdedbf4ebb9956.js:1:101010)
    at 79cdedbf4ebb9956.js:1:100522
I'll attach a screenshot in a reply to this