mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 05:26:03 +03:00
[GH-ISSUE #249] Add CA root to Insomnia #161
Labels
No labels
TLS stack issue
Windows
bug
duplicate
duplicate
enhancement
help wanted
help wanted
pull-request
question
question
root store
waiting for info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mkcert#161
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gagaXD on GitHub (Mar 23, 2020).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/249
Hello,
After running a
mkcert -installand generating certificates with it, It works fine on Chrome & Firefox.But, when I'm trying to send a request with insomnia, It tells me that the certificate can not be trusted.
Is there any way to specify to mkcert other "db" where the rootCA must be installed with
certutil?Thanks for this great package !
@francoism90 commented on GitHub (May 21, 2020):
@gagaXD Did you find a solution? I'm also keep getting the same issue with Insomnia.
@alouini333 commented on GitHub (Jul 14, 2020):
You can disable certificate validation in the settings of Insomnia
@FiloSottile commented on GitHub (Oct 25, 2020):
I'd be happy to add it to the supported DBs if someone can find out where the Insomnia's root store is.
@FinlayDaG33k commented on GitHub (Nov 18, 2020):
Under the hood, Insomnia uses

Curlwith it's CA stored in yourTEMP.For me, this was
C:\Users\Finlay\AppData\Local\Temp\insomnia_2020.4.2\2017-09-20.pem.I don't know where it is on Linux or Mac but you can find it by making a request and looking at the timeline:
Hopefully this information will be of use :)
I don't know how to "include" additional certificates but maybe someone else knows.
@Nightbr commented on GitHub (Mar 12, 2021):
Hey guys, seems there is an issue to improve insomnia and use OS CA certs when possible: https://github.com/Kong/insomnia/issues/1432
Another issue where someone ask to provide custom CA (one mention using Mkcert): https://github.com/Kong/insomnia/issues/675
Maybe we could ping them.
IMO: this is an issue with Insomnia which should provide a way to load custom root CA or load system root CA.
@bNobo commented on GitHub (Nov 26, 2021):
Yes, you can edit the file with a text editor and add your certificates into it. I tried and it works. When the file exists Insomnia will use it directly. So it is a viable workaround but I think you'll have to re-edit the file each time Insomnia is updated.
@leocavalcante commented on GitHub (Jun 1, 2022):
Aha! Thank you very much for the hack. It works just like setting
--cacertto regularcurlCLI.I just noticed there is a
CApath, would be nice if Insomnia sets this path so we can just place our custom CA certs there instead of editing the one in temp.@ghislain-bernard commented on GitHub (Sep 1, 2022):
Hi,
For latest versions 2022, the option to use the file 2017.09.20.pem is not possible anymore... :( and now it is impossible to use my own certificates from my private CA.
To use my private CA for server certificates, I disable the global option "Validate certificates" but it is not a good option.
I hope to use the CA system in future versions.
@laszlolaszlo commented on GitHub (Jun 7, 2023):
It should be very good to able to use own Root CA in Insomnia. Thank you.