curl: (28) Failed to connect to raw.githubusercontent.com port 443 after 75269 ms: Operation timed out
I'm tried to install homebrew on my macbook using /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" this commant but it can't works, how to install homebrew ?
I faced the same issue today with my newly bought macbook pro. Here is how i resolved the issue
I am using jiofiber as my ISP and had not changed the default DNS settings. This was the root cause for the issue.
Go to the DNS settings and update the DNS server to point to googles public DNS servers (8.8.8.8) and save the settings
This resolved the issue for me. Hope this helps
Related
I am using Docker Desktop for Mac.
Since version 3.3.0 and with 3.3.1 I cannot connect to altssh.gitlab.com on port 443 any more whereas 3.2.2 and earlier work.
So, these commands both work in 3.2.2 (I downgraded and verified):
$ ssh git#gitlab.com
$ ssh -p 443 git#altssh.gitlab.com
Both produce output like this:
PTY allocation request failed on channel 0
Welcome to GitLab, #user!
Connection to altssh.gitlab.com closed.
With 3.3.0 and 3.3.1 however, only ssh git#gitlab.com was working while port 443 was seemingly proxied or intercepted by Docker, resulting in this:
kex_exchange_identification: Connection closed by remote host
I verified with nc gitlab.com 22 (netcat) that gitlab.com at port 22 replied:
SSH-2.0-OpenSSH_7.9p1 Debian-10+deb10u2
nc altssh.gitlab.com 443 also prints that text in 3.2.2 but shows nothing and just hangs in 3.3.0+.
I looked at the release notes for 3.3.0 here:
https://docs.docker.com/docker-for-mac/release-notes/
Tried setting noProxy in ~/.docker/config.json because it was mentioned together with HTTPS and restarted Docker Desktop but it changed nothing:
{
"proxies": {
"default": {
"noProxy": "altssh.gitlab.com,075e5c94415c4071840fa96497443943.pacloudflare.com,172.65.251.182,2606:4700:90:0:f0ff:e6a3:2ac:f7ef"
}
}
}
Is there a way to use Docker 3.3.0+ with SSH on port 443 / altssh.gitlab.com?
As of Docker 3.3.2 and newer, the bug has been fixed.
From the 3.3.2 release notes:
• Disable the HTTP and HTTPS transparent proxies when there is no upstream proxy set. Fixes docker/for-mac#5572.
• Revert to the HTTP and HTTPS proxy implementation used in 3.2.2.
Previously...
Looks like the bug is known, though not exactly in this context.
The reason being that supposed "HTTPS" / TLS connections are dropped when they do not use SNI (server name indication), which SSH as a non-SSL/TLS protocol probably does not do.
There's already an open Docker Desktop for Mac issue:
https://github.com/docker/for-mac/issues/5568
And the linked StackOverflow question:
Cannot reach SSL IP when in docker container over bridge. Getting SSL_ERROR_SYSCALL
I am using MAC OS + PyCharm(for pro) and ubuntu16.04 server.
When I try to connect to the server's docker using local pycharm, I get the following error:
( Cannot connect: java.io.IOException: Channel disconnected before any data was reveived )
( I changed the docker daemon port. )
And, I tried searching for ports, and worked well.
Port Scanning host: 163.---.---.178
Open TCP Port: 7561
Even if I tried changing tcp to https, it gave an error.
How can I fix it?
1.set this item first, then reboot your laptop. Run pycharm as administrator, it works for me.
Iam getting the following issue while trying to clone the repository.
fatal: unable to access 'https://Tejaswikatha#bitbucket.org/activecubs_angularjs/activecubs-admin-angularjs.git/': Failed to connect to bitbucket.org port 443: Network is unreachable
For UBUNTU:
Open /etc/hosts file
Add 104.192.143.3 bitbucket.org as a first line and save file
Now cloning will work.
This may be caused by known issues trying to git push, pull, clone over IPv6.
You can force IPv4 by adding the following line to your hosts file (/etc/hosts on Linux, c:\windows\System32\drivers\etc\hosts on Windows):
104.192.143.1 bitbucket.org
In you have a newer git client (>2.8), you can also force IPv4 via the -4 or --ipv4 switch.
I have a strange issue with my psql, which was working just fine in my last session. Suddenly when I try to access my localhost server I get this issue
PG::ConnectionBad
could not connect to server: Connection refused Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432?
Money type has a fixed precision of 10 in PostgreSQL 8.2 and below, and as of
PostgreSQL 8.3 it has a fixed precision of 19. PostgreSQLColumn.extract_precision*
I'm using Postgres 9.5 and Ubuntu 14.
When I type "psql" in terminal I get the message :
psql: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?"
You seem to be trying to open a client / console connection to postgres before you've started the server. Here's information on starting the server:
http://www.postgresql.org/docs/9.1/static/server-start.html
edit
As you're on Ubuntu try:
sudo /etc/init.d/postgresql restart
Have you already logged in to postgres? (sudo -i -u user) user being the name of your postgres account.
PostgreSQL server should be running all the time.
Since I've used Brew to install PG, the fix that worked for me is in the steps below:
$ brew uninstall postgresql
$ exec $SHELL
$ brew postgresql-upgrade-database
$ brew services start postgresql
I'm running a dev kubernetes cluster on Docker Machine with GCE as provider. Cluster was setup using this tutorial: https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/docker.md. Everything's working fine except when I try to do port-forward. I get:
E1104 00:58:23.210982 18552 portforward.go:310] An error occurred forwarding 650 -> 650: Error forwarding port 650 to pod pfsd-rc-7xrq1_default, uid : Unable to do port forwarding: socat not found.
I1104 00:58:23.220147 18552 portforward.go:251] Handling connection for 650
E1104 00:58:23.480593 18552 portforward.go:310] An error occurred forwarding 650 -> 650: Error forwarding port 650 to pod pfsd-rc-7xrq1_default, uid : Unable to do port forwarding: socat not found.
I1104 00:58:23.481531 18552 portforward.go:251] Handling connection for 650
E1104 00:58:23.851200 18552 portforward.go:310] An error occurred forwarding 650 -> 650: Error forwarding port 650 to pod pfsd-rc-7xrq1_default, uid : Unable to do port forwarding: socat not found.
I1104 00:58:23.852122 18552 portforward.go:251] Handling connection for 650
I've tried installing locally, on the GCE machine and inside the container and nothing did the trick. Anyone else hit this?
It's a bit late but still, I think it will be helpful for other people.
It says socat isn't installed. Running apt-get -y install socat on the host machine resolves the problem. It worked for me.
This was a bug with socat not being include in the kubelet container.
It's now fixed.
Release 1.1.2 is the first one to include the fix.
The error clearly says "socat not found". So we need to install it(SOcket CAT), here I'm using a Ubuntu. So it can be install with apt install socat.
What image did you use for the virtual machine? If you use the container VM image, it already has socat installed.