Error:-
Cause:-
The most likely issue causing this is the stty terminal line setting. To resolve this issue lookout for the solution below.
-->
One stop blog for Aws Cloud, Webservers, Application Servers, Database Servers, Linux Admin, Scripting and Automation.
Error:-
The most likely issue causing this is the stty terminal line setting. To resolve this issue lookout for the solution below.
While deploying the application deployment for the gitlab runner recently faced the following error in the EKS Fargate on Amazon AWS
0/111 nodes are available: 111 node(s) had untolerated taint {eks.amazonaws.com/compute-type: fargate}
After installing the Argocd in kubernetes facing issue during the login to Argocd UI in browser with error invalid username or password
Invalid username or password
MosCt of the places you will find that the initial password for the Argocd is the container name with argocd-server or argocd-server.namespace but by entering both of them you would still go through the same issue and it wont login. Argocd set up a one time password and you wont be able to decode the password which is in secrets manager as that password even dont work.
Check the solution below
While creating a ubuntu machine in vagrant recently faced a issue where the image download failed with a SSL error as mentioned below
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'krec/ubuntu2004-x64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
The box 'krec/ubuntu2004-x64' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Vagrant Cloud, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:
URL: ["https://vagrantcloud.com/krec/ubuntu2004-x64"]
Error: SSL certificate problem: self signed certificate in certificate chain
If you're encountering a "self signed certificate in certificate chain" error when using Vagrant, it means that the SSL certificate used by the server you're connecting to is not trusted by your system because it is self-signed or not signed by a trusted authority. This can be a security risk, so there can be 2 cases
1. In some cases(testing) it may be acceptable to temporarily disable certificate validation for testing or development purposes.
2. you need to use a self-signed certificate for SSL/TLS connections in a production environment, you can add the certificate to the trusted certificates on your system.
Based on your use case you can implement any of the solution mentioned below
While creating the multiple region vpc through the terraform getting the error during terraform apply when it tries to create the subnets in 2nd vpc.
module.vpc2.aws_subnet.public[0]: Creating...
╷
│ Error: creating EC2 Subnet: InvalidParameterValue: Value (us-west-2b) for parameter availabilityZone is invalid. Subnets can currently only be created in the following availability zones: us-east-1a, us-east-1b, us-east-1c, us-east-1d, us-east-1e, us-east-1f.
│ status code: 400, request id: 79a19b0b-93d1-4a78-9c0c-124e429c78de
│
│ with module.vpc2.aws_subnet.public[1],
│ on .terraform/modules/vpc2/main.tf line 359, in resource "aws_subnet" "public":
│ 359: resource "aws_subnet" "public" {
Even though i mentioned the providers still the terraform was trying to create the us-west-2b subnet in the wrong region i.e. us-east-1 and it was not able to find those subnets and thats why aws is throughing the error that only us-east-1a, us-east-1b, us-east-1c, us-east-1d, us-east-1e, us-east-1f subnets are available to create the subnets.