[GH-ISSUE #43] Assistance in building mkcert v1.0.0 #24

Closed
opened 2026-02-25 22:32:23 +03:00 by kerem · 7 comments
Owner

Originally created by @kodewise on GitHub (Jul 8, 2018).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/43

Hello FiloSottile,

I'm trying to install mkcert on Ubuntu 18.04. I have already installed libnss3-tools and downloaded the mkcert tarball

apt install libnss3-tools

wget https://github.com/FiloSottile/mkcert/archive/v1.0.0.tar.gz

I'm not sure how to proceed from there. Kindly assist me. Thank you.

Originally created by @kodewise on GitHub (Jul 8, 2018). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/43 Hello FiloSottile, I'm trying to install mkcert on Ubuntu 18.04. I have already installed libnss3-tools and downloaded the mkcert tarball apt install libnss3-tools wget https://github.com/FiloSottile/mkcert/archive/v1.0.0.tar.gz I'm not sure how to proceed from there. Kindly assist me. Thank you.
kerem 2026-02-25 22:32:23 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@FiloSottile commented on GitHub (Jul 8, 2018):

Download the pre-built binary instead (https://github.com/FiloSottile/mkcert/releases/download/v1.0.0/mkcert-v1.0.0-linux-amd64), make it executable (chmod +x) and use it directly (./mkcert-...).

<!-- gh-comment-id:403303488 --> @FiloSottile commented on GitHub (Jul 8, 2018): Download the pre-built binary instead (https://github.com/FiloSottile/mkcert/releases/download/v1.0.0/mkcert-v1.0.0-linux-amd64), make it executable (chmod +x) and use it directly (./mkcert-...).
Author
Owner

@kodewise commented on GitHub (Jul 8, 2018):

This is what I'm getting.

root@ip-172-31-44-56:/home/ubuntu# ./mkcert-v1.0.0-linux-amd64
Using the local CA at "/root/.local/share/mkcert"
Warning: the local CA is not installed in the system trust store! ⚠️
Run "mkcert -install" to avoid verification errors ‼️

Usage:

    $ mkcert -install
    Install the local CA in the system trust store.

    $ mkcert example.org
    Generate "example.org.pem" and "example.org-key.pem".

    $ mkcert example.com myapp.dev localhost 127.0.0.1 ::1
    Generate "example.com+4.pem" and "example.com+4-key.pem".

    $ mkcert '*.example.com'
    Generate "_wildcard.example.com.pem" and

"_wildcard.example.com-key.pem".

    $ mkcert -uninstall
    Uninstall the local CA (but do not delete it).

Change the CA certificate and key storage location by setting $CAROOT,
print it with "mkcert -CAROOT".

On Sun, Jul 8, 2018 at 8:37 PM Filippo Valsorda notifications@github.com
wrote:

Closed #43 https://github.com/FiloSottile/mkcert/issues/43.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FiloSottile/mkcert/issues/43#event-1721922174, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Af_AG_cfR955j3svRHwjtY4AcgIXolOiks5uEkNjgaJpZM4VGv-_
.

<!-- gh-comment-id:403306961 --> @kodewise commented on GitHub (Jul 8, 2018): This is what I'm getting. root@ip-172-31-44-56:/home/ubuntu# ./mkcert-v1.0.0-linux-amd64 Using the local CA at "/root/.local/share/mkcert" ✨ Warning: the local CA is not installed in the system trust store! ⚠️ Run "mkcert -install" to avoid verification errors ‼️ Usage: $ mkcert -install Install the local CA in the system trust store. $ mkcert example.org Generate "example.org.pem" and "example.org-key.pem". $ mkcert example.com myapp.dev localhost 127.0.0.1 ::1 Generate "example.com+4.pem" and "example.com+4-key.pem". $ mkcert '*.example.com' Generate "_wildcard.example.com.pem" and "_wildcard.example.com-key.pem". $ mkcert -uninstall Uninstall the local CA (but do not delete it). Change the CA certificate and key storage location by setting $CAROOT, print it with "mkcert -CAROOT". On Sun, Jul 8, 2018 at 8:37 PM Filippo Valsorda <notifications@github.com> wrote: > Closed #43 <https://github.com/FiloSottile/mkcert/issues/43>. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/FiloSottile/mkcert/issues/43#event-1721922174>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/Af_AG_cfR955j3svRHwjtY4AcgIXolOiks5uEkNjgaJpZM4VGv-_> > . >
Author
Owner

@ninjamonz commented on GitHub (Jul 9, 2018):

./mkcert-v1.0.0-linux-amd64 -install
./mkcert-v1.0.0-linux-amd64 example.org

<!-- gh-comment-id:403344833 --> @ninjamonz commented on GitHub (Jul 9, 2018): ./mkcert-v1.0.0-linux-amd64 -install ./mkcert-v1.0.0-linux-amd64 example.org
Author
Owner

@kodewise commented on GitHub (Jul 10, 2018):

Great, the commands run just fine. I have hosted an apache web server on
AWS and run the commands as indicated. The problem is that the web server
is still using http://ip-address instead of https://ip-address Any clue as
to what I'm doing wrong?

On Mon, Jul 9, 2018 at 5:47 AM ninjamonz notifications@github.com wrote:

./mkcert-v1.0.0-linux-amd64 -install
./mkcert-v1.0.0-linux-amd64 example.org


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FiloSottile/mkcert/issues/43#issuecomment-403344833,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Af_AGzG-q6g6BeXd93LE6xE5UEqawrXqks5uEsRWgaJpZM4VGv-_
.

<!-- gh-comment-id:403867398 --> @kodewise commented on GitHub (Jul 10, 2018): Great, the commands run just fine. I have hosted an apache web server on AWS and run the commands as indicated. The problem is that the web server is still using http://ip-address instead of https://ip-address Any clue as to what I'm doing wrong? On Mon, Jul 9, 2018 at 5:47 AM ninjamonz <notifications@github.com> wrote: > ./mkcert-v1.0.0-linux-amd64 -install > ./mkcert-v1.0.0-linux-amd64 example.org > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/FiloSottile/mkcert/issues/43#issuecomment-403344833>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/Af_AGzG-q6g6BeXd93LE6xE5UEqawrXqks5uEsRWgaJpZM4VGv-_> > . >
Author
Owner

@adamdecaf commented on GitHub (Jul 10, 2018):

@NaiCity mkcert doesn't automagically setup your apache2 configs to use the certificate. You'll need to add that to your apache config.

Here's an example: https://www.digicert.com/ssl-support/apache-multiple-ssl-certificates-using-sni.htm

<!-- gh-comment-id:403870041 --> @adamdecaf commented on GitHub (Jul 10, 2018): @NaiCity `mkcert` doesn't automagically setup your apache2 configs to use the certificate. You'll need to add that to your apache config. Here's an example: https://www.digicert.com/ssl-support/apache-multiple-ssl-certificates-using-sni.htm
Author
Owner

@kodewise commented on GitHub (Jul 12, 2018):

Hey Filippo could you please give me a step by step guide on how to do this
I have tried configuring the apache config file but it doesn't work on my
side.

On Tue, Jul 10, 2018, 18:43 Adam Shannon notifications@github.com wrote:

@NaiCity https://github.com/NaiCity mkcert doesn't automagically setup
your apache2 configs to use the certificate. You'll need to add that to
your apache config.

Here's an example:
https://www.digicert.com/ssl-support/apache-multiple-ssl-certificates-using-sni.htm


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FiloSottile/mkcert/issues/43#issuecomment-403870041,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Af_AG5R8T7vc1RZtRqlTylrzD8rgDM1mks5uFMuXgaJpZM4VGv-_
.

<!-- gh-comment-id:404525722 --> @kodewise commented on GitHub (Jul 12, 2018): Hey Filippo could you please give me a step by step guide on how to do this I have tried configuring the apache config file but it doesn't work on my side. On Tue, Jul 10, 2018, 18:43 Adam Shannon <notifications@github.com> wrote: > @NaiCity <https://github.com/NaiCity> mkcert doesn't automagically setup > your apache2 configs to use the certificate. You'll need to add that to > your apache config. > > Here's an example: > https://www.digicert.com/ssl-support/apache-multiple-ssl-certificates-using-sni.htm > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/FiloSottile/mkcert/issues/43#issuecomment-403870041>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/Af_AG5R8T7vc1RZtRqlTylrzD8rgDM1mks5uFMuXgaJpZM4VGv-_> > . >
Author
Owner

@FiloSottile commented on GitHub (Jul 12, 2018):

I'm sorry, but I can't provide support for all the web server configurations.

mkcert will generate trusted certificates for you. You have to configure your web server to:

  • use that cert and key
  • listen on port 443 for HTTPS
  • redirect from HTTP to HTTPS (if that's what you want)
  • possibly change links and resource addresses (if needed)
<!-- gh-comment-id:404596495 --> @FiloSottile commented on GitHub (Jul 12, 2018): I'm sorry, but I can't provide support for all the web server configurations. mkcert will generate trusted certificates for you. You have to configure your web server to: * use that cert and key * listen on port 443 for HTTPS * redirect from HTTP to HTTPS (if that's what you want) * possibly change links and resource addresses (if needed)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/mkcert#24
No description provided.