New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation error: x509: certificate signed by unknown authority #1635

Closed
klanahan opened this Issue Sep 30, 2016 · 8 comments

Comments

Projects
None yet
2 participants
@klanahan

klanahan commented Sep 30, 2016

Please complete the following steps. The more steps you complete the more
likely we are to address your issue!

  1. Please review the current list of issues to make sure you are not submitting a duplicate.
  2. Please tag your issue appropriately. Please review the tagging criteria.
  3. Based on the issue type tag selected above please fill in the relevant section below.

Bug Report

Version 2.0.0 on MacBook Pro OS X 10.11.6

I have previously installed beta versions on an older machine, which got migrated onto my new machine. I have deleted the old versions as best I can.

When I try to install, I get the following error (from install.log):
installd[3585]: ./postinstall: Error while pulling image: Get https://index.docker.io/v1/repositories/kalabox/proxy/images: x509: certificate signed by unknown authority

When I installed Kalabox on a new Mac, it installed fine, but with importing old files and settings from my previous machine, it just won't work.

I had experimented with Kalabox on a bare computer with no problems, but I can't get it to work on this one. Since my previous experiences were good, I'd really like to switch to this instead of my old XAMPP setup.

@pirog

This comment has been minimized.

Member

pirog commented Sep 30, 2016

@klanahan i would check out the ~/.docker directory. There are certs there that may be stale or unusable if migrated from another machine.

If you don't have other docker things happening on your machine it might be worth doing something like

  1. Completely remove Kalabox
  2. Remove all of ~/.docker
  3. Try installing again.

Let me know if this resolves the issue for you. If so i'm going to add this to our troubleshooting docs.

@klanahan

This comment has been minimized.

klanahan commented Sep 30, 2016

Removed kalabox and docker and reinstalled. Same error.

Looking at the logs a little closer, I was also getting this error earlier
in the process:

(Kalabox2) Unable to get the latest Boot2Docker ISO release version: Get
https://api.github.com/repos/boot2docker/boot2docker/releases/latest: x509:
certificate signed by unknown authority

On Sep 30, 2016 1:13 PM, "Mike Pirog" notifications@github.com wrote:

@klanahan https://github.com/klanahan i would check out the ~/.docker
directory. There are certs there that may be stale or unusable if migrated
from another machine.

If you don't have other docker things happening on your machine it might be
worth doing something like

  1. Completely remove Kalabox
  2. Remove all of ~/.docker
  3. Try installing again.

Let me know if this resolves the issue for you. If so i'm going to add this
to our troubleshooting docs.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1635 (comment),
or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEUAJBDHxASMHBUtpW24r2BU4x_lLLMhks5qvVFggaJpZM4KLUxG
.

@pirog

This comment has been minimized.

Member

pirog commented Sep 30, 2016

@klanahan have you googled that error at all? Looks like it is coming from docker directly.

@klanahan

This comment has been minimized.

klanahan commented Sep 30, 2016

Got it figured out. It is something odd with our agency firewall. When I
went in on the guest network, it installed without a hitch.

Sometimes I really hate my network environment 😀

So, not much to see here after all. It looks like running on an open
network prevents that error from happening.

On Fri, Sep 30, 2016 at 2:14 PM, Mike Pirog notifications@github.com
wrote:

@klanahan https://github.com/klanahan have you googled that error at
all? Looks like it is coming from docker directly.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1635 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEUAJK-DGgiNpbrwZua3Z3bnZKS9bz4Oks5qvV-YgaJpZM4KLUxG
.


Kevin Lanahan

@pirog

This comment has been minimized.

Member

pirog commented Oct 3, 2016

@klanahan do you have any relevant details on how your agency handles these kinds of requests? Are they blocking a port or doing something else? I know that docker has some underlying config you can set to set up proxied requests. Might be worth trying to install kalabox again in the offending network using some of the PROXY envs
https://docs.docker.com/machine/reference/create/#specifying-configuration-options-for-the-created-docker-engine

@pirog

This comment has been minimized.

Member

pirog commented Oct 3, 2016

@klanahan im also going to add some documentation around this to our troubleshooting guide so people can find their way here.

@pirog pirog self-assigned this Oct 3, 2016

pirog added a commit that referenced this issue Oct 3, 2016

@klanahan

This comment has been minimized.

klanahan commented Oct 3, 2016

Thanks. I'll take a look at the ports and see if something is blocked. If I
can figure out what they are doing, I'll let you know.

On Mon, Oct 3, 2016 at 4:34 PM, Mike Pirog notifications@github.com wrote:

@klanahan https://github.com/klanahan im also going to add some
documentation around this to our troubleshooting guide so people can find
their way here.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#1635 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEUAJP8HXsWEZEvpSgen9zVFsDyL_fi9ks5qwXTngaJpZM4KLUxG
.


Kevin Lanahan

@pirog

This comment has been minimized.

Member

pirog commented Oct 3, 2016

@klanahan awesome! that would be great to know and document!

pirog added a commit that referenced this issue Oct 3, 2016

@pirog pirog closed this Nov 3, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment