The Heroku documentation says that I should use the following proxy settings when I use the heroku create command:
> set HTTP_PROXY=http://proxy.server.com:portnumber
or
> set HTTPS_PROXY=https://proxy.server.com:portnumber
> heroku login
Unfortunately, I am receiving the following error message:
! ECONNRESET: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND proxy.server.com
! proxy.server.com:8080
How can I fix this error?
I am also having trouble cloning the GitHub repo which is mentioned in the Heroku documentation, so I have to download it manually.
That documentation is under the heading Using an HTTP proxy. Are you sure that you need to use an HTTP proxy? In many cases you won't need one; simply running heroku create will work.
If you are sure that you need an HTTP proxy you should make sure to replace proxy.server.com with your actual proxy server's name or IP address. proxy.server.com is just an example.
Related
I have a dependency which is published in company's GitLab and is only discoverable with domain name from a certain dns server. The go get command is failing to fetch such dependency on my local environment like this:
go get our-domain.com/group/library#v0.1.0
go: our-domain.com/group/library#v0.1.0: verifying go.mod: our-domain.com/group/library#v0.1.0/go.mod: reading https://sum.golang.org/lookup/our-domain.com/group/library#v0.1.0: 410 Gone
server response: not found: our-domain.com/group/library#v0.1.0: unrecognized import path "our-domain.com/group/library": https fetch: Get "https://our-domain.com/group/library?go-get=1": dial tcp: lookup our-domain.com on 8.8.8.8:53: no such host
It works if I'm building inside docker with adding dns to /etc/docker/daemon.json
{ "dns": ["1.2.3.4"] }
How to do it for getting dependency locally?
Running on MacOs with go1.13
I tried to add DNS address to the Network settings but go get still doesn't use it.
Try set GOPRIVATE=our-domain.com.
go env -w GOPRIVATE=our-domain.com
Otherwise the command tries to resolve the name using the Go proxy and checksum db.
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
I cannot access Gitlab from the browser.
I am getting the following message:
This site can’t be reached
gitlab.com took too long to respond.
Try:
Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_TIMED_OUT
I am not able to use git pull origin master and git push -u origin master from the terminal.
It is showing the following error message:
**fatal: unable to access "https://gitlab.com/myproject.git/" : OpenSSL SSL_connect: SS_ERROR_SYSCALL in connection to gitlab.com:443**
Help me to fix the isssue,
Thanks.
Check your DNS settings, can you reach other sites? This doesn't seem to be a gitlab specific problem.
Also, your remote URL seems quite weird. It's usually gitlab.com/user/repo.git
Try other sites, do they work?
Try acquiring the IP Address from gitlab using an online whois service. Does opening this IP work?
Adjust your origin:
git remote rm origin
git remote add origin "https://username#gitlab.com/username/password.git"
Try this and report back if something worked.
I was using GIT BASH to connect with the Heroku server, I have successfully logged into the heroku website and downloaded Heroku Toolbelt 3.2.0 for windows. When i tried to log in using the GIT Bash it throws me the error message.
Error: A socket operation was attempted to an unreachable host. - connect(2) (Errno::EHOSTUNREACH) (Excon::Errors::Socket
I tried to update the proxy setting using,
set HTTP_PROXY=:http//%username%:%password%#%SERVER%:%PORT%
and using
export HTTP_PROXY='http://user:pass#proxy:port'
After setting this proxy when i tried to log in it throws an error message saying,
Error: getaddrinfo: No such host is known. (SocketError) (Excon::Errors::SocketError)
git bash doesn't seem like a valid command. Are you trying to connect to the Heroku dyno to play around with the environment? If so, you should try: heroku run bash.
When I tried using the export command with the following parameters the issue gets resolved.
The export command were:
export HTTP_PROXY="http://SERVER:PORT"
and
export HTTPS_PROXY="https://SERVER:PORT"
I'm facing some problems while git clone a repo from my ubuntu server running gitolite.
First, I got a public key from the developer who wants to clone the repository from the server. It was a rsa key created with putty. So I did the following to parse it from the putty-style to openssh format with:
ssh-keygen -i -f /tmp/ssh2/YourName.pub > /tmp/openssh/YourName.pub (taken from http://gitolite.googlecode.com/git/doc/ssh-troubleshooting.mkd?r=d3a663d03f1027f909732d55d0519bdd84edb62c)
and uploaded the public key along with a new entry for the repo and the new user in the config file to gitolite-admin repo.
So far, so good.
The developer is using **** along with putty to connect to the server, which is running git on a non-standard port and he keeps on getting the same error over and over again:
Cloning into 'D:\path\to\dirctory'...
error: Recv failure: Connection was reset while accessing http://sub.domain.com/info/refs
fatal: HTTP request failed
git did not exit cleanly (exit code 128)
Could anyone give me some advice about this issue?
EDIT:
In the meantime, we managed to git clone the repository by addressing it with the ssh:// protocol instead of git://, so it doesn't seem like it is a problem of the rsa_public.key or something like that.
The iptables on the server are accepting connections through the port for git, but it keeps on giving the above mentioned error.
The OP herom initially commented that the developer used git://git#remote.server.com:port/repo.git as an address.
I asked if there was any firewall issue, preventing the use of the git port (9418), but the OP mentioned:
no, there shouldn't be a firewall issue as iptables is accepting traffic for the git port - the port is forwarded and appears to be another port when connecting from outside...
Now, the developer cloned the repo through ssh:// (and even connecting to the ssh-port!)
I note that the git port can sometime be blocked, as illustrated in this thread.
If not on the client side, maybe on the server side.