[GH-ISSUE #200] setting up multiple computers with same .pem file generated by mkcert #127

New issue

Closed

opened 2026-02-25 22:32:40 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 22:32:40 +03:00

Owner

Originally created by @junduan125 on GitHub (Sep 19, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/200

Hi, this might be a rookie question.

I have an unqiue development network setup at work. If I serve my https web page "example.org", not only I see "example.org" on my machine locally, but also other developers on their machines within the same network see "example.org".

If I run on my own machine:

mkcert -install
mkcert example.org

It configures my windows computer so that my browser doesn't complain when I visit https://example.org served with example-key.pem and example-cert.pem.

Is there a quick and easy way of also configuring my co-workers' machines to use mkcert with example-key.pem and example-cert.pem generated for my machine so that their browser wouldn't complain either?

Originally created by @junduan125 on GitHub (Sep 19, 2019). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/200 Hi, this might be a rookie question. I have an unqiue development network setup at work. If I serve my https web page "example.org", not only I see "example.org" on my machine locally, but also other developers on their machines within the same network see "example.org". If I run on my own machine: ``` mkcert -install mkcert example.org ``` It configures my windows computer so that my browser doesn't complain when I visit https://example.org served with example-key.pem and example-cert.pem. Is there a quick and easy way of also configuring my co-workers' machines to use mkcert with example-key.pem and example-cert.pem generated for my machine so that their browser wouldn't complain either?

kerem

2026-02-25 22:32:40 +03:00

closed this issue
added the
question
label

kerem commented

2026-02-25 22:32:41 +03:00

Author

Owner

@FiloSottile commented on GitHub (Sep 19, 2019):

Try these instructions and let me know if they are not clear enough!

https://github.com/FiloSottile/mkcert#installing-the-ca-on-other-systems

@FiloSottile commented on GitHub (Sep 19, 2019): Try these instructions and let me know if they are not clear enough! https://github.com/FiloSottile/mkcert#installing-the-ca-on-other-systems

kerem commented

2026-02-25 22:32:41 +03:00

Author

Owner

@junduan125 commented on GitHub (Sep 20, 2019):

Thanks for the quick response!

from #123, I found 2 ways of changing the $CAROOT variable

 $ CAROOT=~/local_certificates mkcert -install

or changing the ~/.bashrc file

export CAROOT="$HOME/local_certificates"

Does editing system environment variable in control panel in windows work?
i.e. adding a new entry under system variables
Variable | Value
CAROOT "C:\dev\local_certificates"

Also, once the rootCA.pem is installed, is it safe to remove the rootCA.pem file?

@junduan125 commented on GitHub (Sep 20, 2019): Thanks for the quick response! from #123, I found 2 ways of changing the $CAROOT variable ``` $ CAROOT=~/local_certificates mkcert -install ``` or changing the ~/.bashrc file ``` export CAROOT="$HOME/local_certificates" ``` Does editing system environment variable in control panel in windows work? i.e. adding a new entry under system variables Variable | Value CAROOT "C:\dev\local_certificates" Also, once the rootCA.pem is installed, is it safe to remove the rootCA.pem file?

kerem commented

2026-02-25 22:32:41 +03:00

Author

Owner

@FiloSottile commented on GitHub (Sep 20, 2019):

Yes, system wide env vars should also work.

You can delete rootCA.pem after installing, yes.

I'll close this now, but let us know if there are ways we can improve the instructions.

@FiloSottile commented on GitHub (Sep 20, 2019): Yes, system wide env vars should also work. You can delete rootCA.pem after installing, yes. I'll close this now, but let us know if there are ways we can improve the instructions.