After configuring SIP, Jami will not start, crashes without an error message

Support in English
1

Windows 10, April 2025 updated.
Jami version 1.0.9259.35486.

Created an initial Jami account, then created an SIP account with the server details for VoipVoip.
Was able to create the SIP account, then when I saved it, Jami crashed without an error.

Now, whenever I try to start it, it closes immediately without the main window appearing, so I cannot change the profile or any settings.

When I looked at it with Process Monitor, it showed that it was crashing around the point of looking up CA certificates.

It has a WER created, but I would like to know if there is a way to sort this out.

2

Also, the Event viewer shows the following:
Faulting application name: Jami.exe、version: 0.0.0.0、timestamp: 0x681d06ca
Faulting module name: ucrtbase.dll、version: 10.0.19041.3636、timestamp: 0x81cf5d89
Exception code: 0xc0000409
Fault offset: 0x0000000000071208
Faulting process ID: 0x1e6c
Faulting application start time: 0x01dbc178141f2ea1
Faulting application path: C:\Program Files\Savoir-Faire Linux\Jami\Jami.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: 5095ba0c-a086-4f29-927b-cf61965d497d
Faulting package full name:
Faulting package-relative application ID:

3

After deleting the profile files, I was able to get it to load, however I had to re-import my backup, it didn’t have a couple of my contacts though.
Anyway, the error seems to happen when I select TLS as a connection option.
The UDP seems to at least let me go online.
Will have to try actually do a call though ~_~.

4

So, I solved the issue with my original profile and was able to bring it up properly,
However, it is bad that it will not be able to start on such an error with a configuration error.
I will share how I fixed it.
Open this folder:
C:\Users\YOURUSERNAME\AppData\Local\Jami

Edit the following file(back it up first):
dring.yml

Change the following:area:

accounts:
  - id: ID REDACTED
~~ the stuff in between redacted ~~
    tls:
      calist: ""
      certificate: ""
      password: ""
      privateKey: ""
      enable: true  <----- Change this to false
~~ stuff afterwards redacted ~~

Then Jami will start up again normally.

I was able to use SIP to call a landline successfully after this.