I am getting net/http: TLS handshake timeout when trying to install aws-sdk-go with go get.
go get -v github.com/aws/aws-sdk-go
go: downloading github.com/aws/aws-sdk-go v1.30.10
go get: github.com/aws/aws-sdk-go#v1.30.10: Get https://storage.googleapis.com/proxy-golang-org-prod/153044bb636484b4-github.com:aws:aws-sdk-go-v1.30.10.zip?Expires=1587550038&GoogleAccessId=gcs-urlsigner-prod%40golang-modproxy.iam.gserviceaccount.com&Signature=Py%2Fu6vp6bq%2F%2Bz57LXE4oUVTvCjAL08bnxnlWuHUh2FME7v89fzIz1%2FNOJ5kKsXCJV39OMJLsjF5j3457p1mZJsBZSgTjMnFbPbuVRHu%2FhKPFPmvVsLYvchvB7Va%2F%2BGcyYHhOsP0XMdSo3N8GjqltihMWfKML49RNOmqCrQT%2F0Qc1b%2BBhbz9iH88QNd9mSwYYQpr0kuAVOb3OGfyQGY11vrTHLWp5ammOH%2B6Xa7g5cpCMO91Ane8aOEYywc0oSsgvv4y32qp0G%2FGm18pDHzLq1o0OA7HEKUU59ACFpOsTyEhF0uECBoNfFpiBuOub%2BY%2FMhGzsojk1dW0vzmR0SOGxqg%3D%3D: net/http: TLS handshake timeout
I can install any other go packages without any trouble. And my colleagues (in different network) can install aws-sdk-go without any problem. But, I am continuously facing this problem. I have tried with two different laptops. I have also tried switching to 3G network instead of broadband but, no luck there too.
How can I troubleshoot this problem?
Related
I'm getting the following error when trying to install a plugin from the Grafana CLI installed on Kubernetes. I deleted and rebuilt the pod, it works fine but the error persists. Other Grafana features are working fine. What can I do?
Failed to send requesterrorGet "https://grafana.com/api/plugins/repo": context deadline exceeded (Client.Timeout exceeded while awaiting headers)Error: ✗ Failed to send request: Get "https://grafana.com/api/plugins/repo": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
BR
You say there is no problem with Grafana working. Kubernetes also does not give an error with the pod. In the error content, it says "Failed to send request: Get". Most likely it can access the internet but not dns resolution. If ping 8.8.8.8 is working but ping google.com is not working, you need to add nameserver.
For this, you can add something like the following into the /etc/resolv.conf file.
nameserver 8.8.8.8
Seemingly out of the blue (i.e. I haven't edited code recently), I've started receiving a lot of these error messages in my cron jobs in the past couple days:
FacebookAds\Exception\Exception, Code: 35: LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to graph.facebook.com:443
As a test, I was able to SSH into my server and run this without problem: curl -vvv https://www.facebook.com
Also, the cron job that runs every 5 minutes and often causes this error doesn't always cause this error. And in the few times I've manually dispatched the job, I haven't seen the error.
What does this mean, what suddenly caused my cron job to often throw this error, and how can I fix it?
P.S. These seem to be related questions but none seem to have answers about LibreSSL and Facebook:
Laravel 5.7 OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to graph.facebook.com:443
Facebook PHP SDK: Unknown SSL protocol error
SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443
fatal: unable to access 'https://github.com/xxx': LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443
I still don't know the root cause, but I ran service docker restart and haven't noticed the error since.
Thanks to https://stackoverflow.com/a/52740968/470749 for the idea.
Had a similar error message while installing ruby gems.
Upgrading the OS to Mojave 10.14.5, solved the problem for me.
While debugging I realised that confd doesn't pick up the keys and my journal looks like this:
Sep 18 18:31:50 ip-10-171-54-76.ec2.internal docker[24891]: [nginx] waiting for confd to refresh nginx.conf
Sep 18 18:31:56 ip-10-171-54-76.ec2.internal docker[24891]: 2014-09-18T18:31:56Z 9122c7a54edc confd[9572]: ERROR 501: All the given peers are not reachable (Tried to connect to each peer twice and failed) [0]
I use nsenter to log in to the running container to run some experiments for debugging purposes. I ran this command
confd -onetime -node 172.17.42.1:4001 -config-file /etc/confd/conf.d/nginx.toml
Then received this error as above
confd[12894]: ERROR 501: All the given peers are not reachable (Tried to connect to each peer twice and failed) [0]
I am totally clueless at this point. I am using EC2 with the stable version of CoreOS and I am sure that etcd is running on the host. Also, I can ping the host from inside the container successfully.
Any ideas on what's wrong?
Assistance will be much appreciated.
This error indicates that your etcd cluster isn't operating correctly, so confd has nothing to watch. It has probably lost quorum. The logs (journalctl -u etcd) should indicate what happened.
I'm in the middle of trying to deploy a Django project on Subsys.no, Who uses FastCGI. I have never deployed a project before and have been trying for 3 days straight.
I have made a virtualenv on the server and installed all the packages I need.
I have uploaded (FTP) the project I have onto the server (in the correct place)
I have tired using Fabrics "fab all" command on the server and locally. The server gave this response:
--
all
---
-------
install
-------
$ cat /etc/default/locale ->
Fatal error: Low level socket error connecting to host subsys.no on port 22: Connection refused (tried 1 time)
Underlying exception:
Connection refused
Aborting.
The local gave the same answer but with one twist:
Fatal error: Timed out trying to connect to subsys.no (tried 1 time)
Underlying exception:
timed out
I'm not sure if the error lie here or here on the site. It gives out alot that I dont understand.
All help is greatly appreciated and thanks in advance!
I am trying to get Django-Celery running on my Django App. I cannot get the worker server to run. When I try I get the message: No Connection could be made because the target machine actively refused it
Here is what I have done so far. First, I installed the django celery package: http://pypi.python.org/pypi/django-celery
I can load it into python without problems. I also installed the RabbitMQ server per the windows install instructions: http://www.rabbitmq.com/install.html#windows
Starting the tutorials in pytho on the RabbitMQ site I saw the need to install pika: http://pypi.python.org/pypi/pika. It imports without any problems.
From there I start the RabbitMQ server by running this at the command line: rabbitmq-service start
I get the message back that Service RabbitMQ started
Here is where I start to have problems.
I attempted the first steps in django-celery: http://packages.python.org/django-celery/getting-started/first-steps-with-django.html and the "hello world" example on the rabbitMQ site: http://www.rabbitmq.com/tutorials/tutorial-one-python.html
In both cases I get the message: No Connection could be made because the target machine actively refused it
My first thought was that this sounded like a firewall problem. So I went into the windows 7 firewall and added inbound and outbound rules to open the local and remote ports 5672 and 5673 to TCP protocol, but I still get the same error message.
When I run rabbitmqctl status i get the message:
Error: unable to connect to node 'rabbit#hostname': nodedown
diagnostics:
- nodes and their ports on hostname: [{rabbitmqctl18856, 505031}]
Does that mean it that it is trying to operate on those ports? what about the default 5672?
Any suggestions?
UPDATE: This was actually a problem resulting from several failed rabbitmq installs conflicting with the latest installation. If you have to remove rabbitmq use the 'rabbitmq-service remove' command and not SC DELETE, which cause a lot of problems for me and I had to go in and clean up my windows registry file.
The nodedown error indicated by rabbitmqctl suggests that the server isn't running on that machine.
Try going though the steps in RabbitMQ's troubleshooting guide. In particular, pay close attention to the logs. Has the server crashed for some reason? Could you post the logs somewhere?