I have created an AdministratorAccess user via
amplify configure
and I did verified my AWS account completely, but I still get this error
Initializing project in the cloud...An error occurred when creating the CloudFormation stack
× Root stack creation failed
init failed
Error: connect ETIMEDOUT 54.239.29.24:443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16) {
errno: -4039,
code: 'TimeoutError',
syscall: 'connect',
address: '54.239.29.24',
port: 443,
time: 2022-02-25T07:55:57.713Z,
region: 'us-east-1',
hostname: 'cloudformation.us-east-1.amazonaws.com',
retryable: true
}
My company is using proxy to guarantee security, so could there be something about cli proxy setting?
Well, it is the proxy that prevents me from accessing AWS,
My solution is to type these commands in win10 cmd
setx HTTP_PROXY http://username:password#proxy.example.com:1234
setx HTTPS_PROXY http://username:password#proxy.example.com:5678
You can read more in
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-proxy.html
Related
I have tried to run the Apache Airflow DockerOperator from Windows, but received the error
docker.errors.DockerException: Error while fetching server API version: ('Connection aborted.', FileNotFoundError(2, 'No such file or directory'))
What should I do?
[![Docker Desktop][1]][1]
Expose the Docker Daemon on TCP
[1]: https://i.stack.imgur.com/4uUjS.png
If you are running airflow from docker, than the host will most probably be:
host = 'host.docker.internal'
Otherwise - probably
host = 'localhost'
Add the following url in the docker_url parameter:
DockerOperator(
...
docker_url=f'tcp://{host}:2375'
...
)
Upvote the answer and the question😄
docker desktop on mac is getting error:
Unable to connect to the server: x509: certificate signed by unknown authority
The following answers didn't helped much:
My system details:
Operating system: macOS Big Sur Version 11.6
Docker desktop version: v20.10.12
Kubernetes version: v1.22.5
When I do:
kubectl get pods
I get the below error:
Unable to connect to the server: x509: certificate signed by unknown authority
Posting the answer from comments
As appeared after additional questions and answers, there was a previous installation of rancher cluster which left its traces: certificate and context in ~/.kube/config.
The solution in this case for local development/testing is to delete entirely ~/.kube folder with configs and init the cluster from the scratch.
If you are using a corporate laptop, and everything you do goes through a proxy, you will get this message. Hence, when docker desktop tries to connect to the server defined in ~/.kube/config, it will try to go through the proxy and you will need the cert issued by the company. Long story short, you are getting blocked by the the company... To fix, you can add the no proxy props, adding what ever value server: internal.docker defined in~/.kube/config . Meaning, if I am connecting to docker cluster which runs locally in my laptop, do not direct my traffic through proxy.
When doing docker info, after setting no proxy, you should see something like this.
docker info | grep -i proxy
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal,localhost,127.0.0.1,.local,.us.example.com,.examplecorp.com,.examplevcn.com,kubernetes.docker.internal
hubproxy.docker.internal:5000
I'm attempting to connect to a local Postgres server running as a docker container from my Lambda function.
I'm using the sam local invoke call to do so.
For some reason, it seems that outgoing connection from SAM's docker container for the function is disabled.
I'm getting this error message:
"errorMessage": "(psycopg2.OperationalError) could not connect to server: Connection refused\n\tIs the server running on host \"localhost\" (127.0.0.1) and accepting\n\tTCP/IP connections on port 5432?\ncould not connect to server: Cannot assign requested address\n\tIs the server running on host \"localhost\" (::1) and accepting\n\tTCP/IP connections on port 5432?\n\n(Background on this error at: http://sqlalche.me/e/e3q8)",
Is there a way to enable a Lambda function call to a local docker database?
I have no issues running the connection code outside the Lambda function as standard Python code - so I'm sure my database is up, my code works, etc.
Try running the command with —docker-network TEXT per the AWS SAM CLI documentation.
I had a similar issue attempting to run sam local start-api with a local Docker Postgres database and was getting connection refused errors. I ran sam local start-api —docker-network host and it resolved the issue.
This is a good post which helped me to understand more about Docker networks.
Hope this helps you and any others looking at this.
I resolve this by replacing localhost with host.docker.internal.
For example if you use psycopg2
conn = psycopg2.connect(host="host.docker.internal",port=5432, ...)
I try to use Kibana on Windows 10 (yeah, I know).
I think I put both yml right:
elasticsearch uri: localhost:9201
kibana uri: localhost:5601
When I start Kibana in Windows I get:
{"type":"log","#timestamp":"2019-03-06T20:25:28Z","tags":
["fatal","root"],"pid":2844,"message":"{
Error: listen EACCES: permission denied 127.0.0.1:5601\n
at Server.setupListenHandle [as _listen2] (net.js:1260:19)\n
at listenInCluster (net.js:1325:12)\n
at GetAddrInfoReqWrap.doListen (net.js:1458:7)\n
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:62:10)\n
code: 'EACCES',\n
errno: 'EACCES',\n
syscall: 'listen',\n
address: '127.0.0.1',\n
port: 5601 }"}
I tried to setup permission to full access on the kibana.bat file.
Any help appreciated!
Hi seems your port is already in use.
Also open your kibana URL to check whether it is assigned already.
Check your port and kill it inorder to use.
OR
Open your kibana config yaml file, uncomment the port info and change the port.
I had the similar issue and got solved by trying this way. Hope it helps.
C:\Users\ghunaim>heroku login
heroku: Enter your login credentials
Email: moahemdghunaim7030#gmail.com
Password:
Error: tunneling socket could not be established, cause=connect ECONNREFUSED 127
.0.0.1:8080
at ClientRequest.onError (C:/Program Files/heroku/client/node_modules/tunnel
-agent/index.js:177:17)
Remove a http_proxy in environment variables.
delete this: