I'm try to use Heroku CLI.
But when I want to do some commamd like:
heroku login, heroku log, etc.
The below error will show
SELF_SIGNED_CERT_IN_CHAIN self signed certificate in certificate chain
How can I sovled it?
I had the same issue however this helped me:
Verify your proxy export
export NO_PROXY='localhost,localnets, <company proxy IP settings>
Then verifying my companies .pem file stored in my user directory:
export NODE_EXTRA_CA_CERTS=~/.ssh/bc.pem
(or wherever you store it.)
Then try
heroku login
Its moreover related to security and firewall settings over machine and network.
If you are in secure network, try to connect over proxies / public network, then you can able to run heroku commands.
Or manually acquire SSL/TLS certificate on machine. Kindly refer to this link
Related
I am setting up the airflow in my macOS using Docker and I am encountering this below error while doing the setup. Any help would be appreciated.
ERROR: Get "https://registry-1.docker.io/v2/": x509: certificate is valid for *.integration.livongo.com, integration.livongo.com, not registry-1.docker.io
Thanks.
I have had the same issue this week when upgrading to the latest Docker Desktop 4.4.4.
I am behind a company proxy which injects it's own CA certificate which can cause this problem. If that is your case, make sure you know what is the http & https proxy URL or IP if there is one, and add it in the Docker Desktop settings, under Resources/Proxies.
You may also add the http_proxy and https_proxy environment variables to your system with the full url,IP of the proxy server.
If the problem persists, roll back to a previous version of Docker Desktop. That's what I ended up doing in the end because the latest version didn't work with my proxy configuration.
I am trying to run the bitnami let's encrypt SSL tool to setup an SSL certificate on my amazon lightsail wordpress server.
this is the tool:
sudo /opt/bitnami/bncert-tool
read more about it here: https://aws.amazon.com/premiumsupport/knowledge-center/linux-lightsail-ssl-bitnami/
but when i run it, I get this error:
Account [email address of account] is not registered. Use 'run' to register a new account.
it's not clear how to resolve this from the let's encrypt or bitnami documentation. How do I get around this ?
I am trying to login to a private repository from a windows machine using the docker command prompt, but I cannot figure out where I am supposed to place the SSL cert on a Windows machine.
I have successfully logged in from a Linux machine by placing the cert file in /etc/docker/certs.d/mydomain.com:port/
I have found in some of the documentation they are suggesting to place this .cert file in
C:\Program Files\Docker\certs.d{my domain goes here }{port}
But Still, I'm getting below error when I'm trying to log in
Error response from daemon: Get https://{my domain goes here }.com:{port No}/v2/: x509: certificate signed by unknown authority.
Can anyone help me to sort out this issue?
I think I have found my mistake, which is I have placed the .cert file in
C:\Program Files\Docker\certs.d{my domain goes here }{port}.
It should be in,
C:\ProgramData\docker\certs.d{my domain goes here }{port}
(Please note that this ProgramData folder is a hidden folder)
I use sourcerepo.com as SVN server. My XCode5 bot complains : error validating server certificate for "https://myproject.sourcerepo.com:443"
- the certificate is not issued by a trusted authority. Use the fingerprint etc....
How can I make my XCode Server accept this svn server and retrieve sources ?
thanks for your advice
Frank
Verify why the certificate is untrusted. (E.g., is it a self-signed certificate?)
Start Terminal and run svn info https://myproject.sourcerepo.com:443/<path-to-repository>. Accept the certificate permanently when prompted.
I found a way to make it work from the Xcode 5 release notes:
https://developer.apple.com/library/ios/releasenotes/developertools/rn-xcode/xc5_release_notes/xc5_release_notes.html
Communicating with a remote SVN repository over HTTPS can fail with an
error similar to “Error validating server certificate for server
name.” Edit the file
/Library/Server/Xcode/Config/xcsbuildd.plist
and change the TrustSelfSignedSSLCertificates key from false to true.
Then, from a Terminal window, run:
sudo killall xcsbuildd
I did exactly the above. To edit the file you actually need to
sudo vi /Library/Server/Xcode/Config/xcsbuildd.plist
After restarting the build daemon I was able to get my Xcode bot to checkout the sources from the remote repository and perform the integration. Hope this helps!
I have now built up a gitlab server on my Ubuntu computer as your installation guide on www.gitlab.org official website tells.
Then I signed in the gitlab server homepage through IE browser in the client computer.
Subsequently I modified the "My Profile" and uploaded my SSH public key.
Logged out and reboot server, then login again.
Create my first git project : gitlab_testing.git
At that time when I did 'git clone' to download the gitlab_testing.git repository from server, or when I push the first commit upon to server, it always showed the below error message, please kindly see the below snapshots :
As mentioned here:
"Name or service not known" is a socket-level error which usually points to either an invalid IP address/DNS hostname, or an unregistered port name.
Check if this is a proxy issue (as in this question).
Either you need to configure a proxy, or make sure that you don't use a proxy when accessing a local gitlab server (using the no_proxy environment variable)