Skip to content
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

error install Z-Push #1393

Closed
ltsss opened this issue Jul 5, 2018 · 11 comments
Closed

error install Z-Push #1393

ltsss opened this issue Jul 5, 2018 · 11 comments

Comments

@ltsss
Copy link

ltsss commented Jul 5, 2018

when i install mailinabox get this error
unable to access 'https://stash.z-hub.io/scm/zp/z-push.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

@mwcz
Copy link

mwcz commented Jul 5, 2018

Same here.

@just4t
Copy link
Contributor

just4t commented Jul 5, 2018

see: https://discourse.mailinabox.email/t/fatal-error-installing-z-push/3422/7

@mwcz
Copy link

mwcz commented Jul 5, 2018

Thanks, that helped! Looking forward to a true fix (new cert, git mirror with proper ssl, etc).

@ltsss
Copy link
Author

ltsss commented Jul 6, 2018

Thanks just4t ,you advice solved my problem 。

@louwers
Copy link
Contributor

louwers commented Jul 7, 2018

The 'quickfix' doesn't work for me. Maybe because I'm installing mailinabox as root and it has no git user config.

@niladam
Copy link

niladam commented Jul 9, 2018

For people having the same issue. This is what helped me:

export GIT_SSL_NO_VERIFY=1; curl -s https://mailinabox.email/setup.sh | sudo -E bash

@jvolkenant
Copy link
Contributor

There is something up with the SSL cert for stash.z-hub.io, Perhaps we can update from the mirror here on github in the meantime? https://github.com/Z-Hub/Z-Push.git

@bogao
Copy link

bogao commented Jul 30, 2018

I'd have it reopened since it becomes not only a certificate-related issue now. It is now returning 502. Installation script must get updated correspondingly.

@JoshData
Copy link
Member

Did you try the fix that's already on the master branch (but not released)?

@bogao
Copy link

bogao commented Jul 30, 2018

I'd wait for the release. Thanks!

@JoshData
Copy link
Member

The fix doesn't have the 502 error problem, so we're good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants