[GH-ISSUE #64] Vagrant question #32

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

Originally created by @mattkaye on GitHub (Aug 19, 2018).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/64

I’m running Ubuntu via vagrant on a Mac. Do I install and run this on the host or guest OS?

Originally created by @mattkaye on GitHub (Aug 19, 2018). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/64 I’m running Ubuntu via vagrant on a Mac. Do I install and run this on the host or guest OS?
kerem 2026-02-25 22:32:25 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@nickkaczmarek commented on GitHub (Aug 22, 2018):

Where is your webserver located? On macOS or Ubuntu?

<!-- gh-comment-id:415218241 --> @nickkaczmarek commented on GitHub (Aug 22, 2018): Where is your webserver located? On macOS or Ubuntu?
Author
Owner

@nickkaczmarek commented on GitHub (Aug 22, 2018):

This might help it. https://ishan.co/ssl-vagrant-local

<!-- gh-comment-id:415218499 --> @nickkaczmarek commented on GitHub (Aug 22, 2018): This might help it. https://ishan.co/ssl-vagrant-local
Author
Owner

@mattkaye commented on GitHub (Aug 22, 2018):

The web server is on Ubuntu running in virtual box. I already have followed
steps like the one in the url you posted. I do have a self signed cert for
each of my vhosts , but can’t get chrome to trust them . I’ve tried almost
everything I can think of. I was hoping this tool would handle all that
manual configuration for me and handle the keychain, but I’m not sure it
will.

On Wed, Aug 22, 2018 at 7:19 PM Nick Kaczmarek notifications@github.com
wrote:

This might help it. https://ishan.co/ssl-vagrant-local


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

--
Regards
Matt Kaye

<!-- gh-comment-id:415220399 --> @mattkaye commented on GitHub (Aug 22, 2018): The web server is on Ubuntu running in virtual box. I already have followed steps like the one in the url you posted. I do have a self signed cert for each of my vhosts , but can’t get chrome to trust them . I’ve tried almost everything I can think of. I was hoping this tool would handle all that manual configuration for me and handle the keychain, but I’m not sure it will. On Wed, Aug 22, 2018 at 7:19 PM Nick Kaczmarek <notifications@github.com> wrote: > This might help it. https://ishan.co/ssl-vagrant-local > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/FiloSottile/mkcert/issues/64#issuecomment-415218499>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ACpruQ8PY7FmcMhQNtGnSJVfDAM6v6_zks5uTebrgaJpZM4WCx0S> > . > -- Regards Matt Kaye
Author
Owner

@mrmuli commented on GitHub (Nov 8, 2018):

@mattkaye I am running an Ubuntu box on MacOS and I had to install the CA in the box. So the tool is initially installed on my Mac and certs generated there but I copy over the rootCA into the box and run install and it works.

An issue I'm however facing is I can't seem to get ansible to install the root CA with the certificate I copied over. I have to manually ssh and run mkcert -install to get the box using the cert I copied over.

I hope you got help though :)

<!-- gh-comment-id:436953796 --> @mrmuli commented on GitHub (Nov 8, 2018): @mattkaye I am running an Ubuntu box on MacOS and I had to install the CA in the box. So the tool is initially installed on my Mac and certs generated there but I copy over the rootCA into the box and run install and it works. An issue I'm however facing is I can't seem to get ansible to install the root CA with the certificate I copied over. I have to manually ssh and run mkcert -install to get the box using the cert I copied over. I hope you got help though :)
Author
Owner

@adamdecaf commented on GitHub (Nov 8, 2018):

I have to manually ssh and run mkcert -install to get the box using the cert I copied over.

Yep. Vagrant is a virtual machine, so the certs won't be installed by running mkcert on the host.

<!-- gh-comment-id:437103755 --> @adamdecaf commented on GitHub (Nov 8, 2018): > I have to manually ssh and run mkcert -install to get the box using the cert I copied over. Yep. Vagrant is a virtual machine, so the certs won't be installed by running `mkcert` on the host.
Author
Owner

@FiloSottile commented on GitHub (Jan 6, 2019):

You want to run mkcert -install on the system that is going to have to trust the certificates. So if the server runs in Vagrant and the browser on the laptop, you run mkcert -install on the host, and install the generated certificates inside the guest.

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

<!-- gh-comment-id:451785593 --> @FiloSottile commented on GitHub (Jan 6, 2019): You want to run `mkcert -install` on the system that is going to have to trust the certificates. So if the server runs in Vagrant and the browser on the laptop, you run `mkcert -install` on the host, and install the generated certificates inside the guest. See also https://github.com/FiloSottile/mkcert#installing-the-ca-on-other-systems
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#32
No description provided.