-
Notifications
You must be signed in to change notification settings - Fork 48
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
Certificate has expired or is not yet valid #28
Comments
I'm getting the same on OS X with a |
@buurzx FYI I was able to get this working temporarily by doing |
@nikvdp Thanks, this works for me. |
Update cert pls 🗡 |
Same cert error with a fresh install from Homebrew (warp v0.0.3) |
Is there anything I can do to help / fix ? |
@spolu I'm getting the same error as before on a fresh install via linuxbrew. I don't use it regularly, opening this issue was actually the first time I'd tried to use warp! Would love to start though :) |
Any changes? The problem with sertificate is still relevant. |
Is there a way to automate the certificate renewal? |
It works with the --insecure_tsl flag but would be nice if it would work without as well. |
This is still a problem. $ warp open
Opened warp: xxx
Restored session: Thu May 31 19:16:44 CEST 2018
[Error] Connection error: x509: certificate has expired or is not yet valid Version$ brew info warp
warp: stable 0.0.3 (bottled)
Secure terminal sharing with one simple command
https://github.com/spolu/warp
/usr/local/Cellar/warp/0.0.3 (6 files, 5.4MB) *
Poured from bottle on 2018-05-31 at 19:17:07
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/warp.rb |
The default
and then use:
|
Hi.
Install warp from source code.
But after command
warp open..
i get connection error.Maybe i missed something?
[Error] Connection error: x509: certificate has expired or is not yet valid
The text was updated successfully, but these errors were encountered: