sshed | sshed - ssh config editor and bookmarks manager | SSH Utils library

I was trying to set up git pipeline, but for some reason, I am unable to do so now. It is throwing error showing the above error. I tried different things, but could not see anything out of the order.

I am at my wits end and do not know how to proceed. Kindly tell me how should I proceed to fix this ?.

Note:- Currently Jenkins is installed in an ec2 instance and another ec2 instance is used as build server, in both servers git is installed and working correctly. I have sshed into build server and tried accessing repo from it and was able to clone the repo sucessfully in build server.

Kindly advise me on what might be the possible issue here?

I have an AWS EC2 instance on which I would like to run a job of infinite time. However, I don't want to have to SSH into my instance to run the command.
I basically need to run a python script, which performs work indefinitely, so I want to run python3 script.py from my EC2 instance in such a way that I can do it remotely, and as long as my instance is running the script.py script is running.
To be more clear, if I run a command like sudo service httpd start I don't have to remain SSHed into my instance to know that the traffic is being served. Similarly, I would like to run a command such that even if I terminate my SSH connection to the instance, script.py is still running.
A solution I thought of is to have a local machine explicitly connect to the instance and run the command in an infinite loop, but I would like to avoid this.
A further question is if there is a way to scale to multiple instances performing this same job.
I have also tried editing rc.local in the etc directory, but I confirmed that the job was not running.

I am using Circle CI's aws-ecs/deploy-service-update orb to deploy my docker container by pulling the latest image in AWS ECR and deploy it in AWS ECS with AWS EC2 instance. This container is a Machine Learning model that accepts API requests at TCP port 3000(I am using fastAPI for this) and returns the predictions. After I deployed it I couldn't send requests to the public IP of the container instance of the task that deploys the container at port 3000 (This IP is not my EC2 instance's public IP; it only has private IP and public IP is disable).

1. I checked my security group and made sure that the port 3000 is open to receive requests from all IPs(0.0.0.0), as part of the inbound rule.
2. I stopped the task(which automatically will stop the container running in the EC2 instance) with the thought that something may have gone wrong from Circle CI. Then, according to the service configuration(1 desired task) and task definition of AWS ECS, a new task has started(hence the container) automatically. But, I couldn't send requests to this either.
3. I SSHed into my EC2 instance to know if the port 3000 is open. This is when is when I learned that ports weren't mapped at all:
   As you can see, PORTS column is empty for the container and the container has to accept requests at port 3000 from the command.

And here are the open ports of the EC2 instance: As you can see, port 3000 is not listed here.

Here is the task with port mappings which deployed the container (to AWS ECS) that you see docker ps screenshot above:
In the task definition, you can see the port mappings I have defined for the container.

Here is the task running on my EC2 instance with the task-definition shown above and the network mode I am using is 'awsvpc':

Here's the "Networking" tab of ENI associated with the task, and also the inbound rule of the security group associated with the EC2 instance that the task is running inside, which accepts requests on port 3000 from all IPs.

After I did

I successfully ran MERN app in my local machine using docker. Then, just for fun, I wanted it to deply to AWS, EC2 instance. After deploying, the fetch call in react-app gives this error:

Instead of the usual way of deployment via Gcloud command line, I simply sshed the GCP Ubuntu instance and deployed my flask app via WinSCP by transferring the files onto the Ubuntu instance I have created. I was able to get it to run like so:

I have also reserved a static address so that I could allow users to view the Flask app.

However, when I tried to access the external ip address, GCP refused to connect and I can't view my flask app.

What could I have possibly done wrong?

I deployed an Azure Functions App with Python 3.8. Later on I tried to use dataclasses and it failed with the exception that the version available does not support dataclasses. I then SSHed to the host of the Function App and by using python --version figured out that version 3.6 was actually installed. As dataclasses are available from 3.7 on it makes sense why this module can't be used.

But what can I do to actually have version 3.8 running on the Function App host?

Helllo, I created a mosquitto broker via the eclipse docker image and recently followed this guide to add SSL/TLS support: http://www.steves-internet-guide.com/mosquitto-tls/.

When I am sshed in the VPS which is running the broker, I can use the command:

I'm running ECS tasks, and recently the service cpu hit 100% and went down.

I waited for the instance to settle down and sshed-in. I was looking for logs, but it seemed docker container restarted and logs are all gone (logs when the cpu was high)

Next time, how do I make sure I can see the logs at least to diagnose the problem?

I have the following, hoping to see some logs somewhere (mounted in the host machine)

I have an EKS cluster running kubernetes 1.14. I deployed the Nginx controller on the cluster following these steps from the following link.

Here are the steps that I followed -

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/mandatory.yaml

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/aws/service-l4.yaml

kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/deploy/static/provider/aws/patch-configmap-l4.yaml

But I keep getting these errors intermittently in the ingress controller.