Recently I installed SSL using ZeroSSL on my website and for doing that I had to deploy Load Balancer for my EC2 instance (IIS 10). I was initially using ftp to directly publish my ClickOnce application. But now I am not able to publish my application. It shows:
Failed to connect to 'ftp://website/folder' with the following error: Unable to create the Web site 'ftp://website/folder'. The server unexpectedly closed connection.
On the other hand I am able to connect via telnet to the server. But I am unable to connect via file explorer, it shows connection timed out.
Is it possible to do ftp publish through aws Load Balancer? If yes then, please point me in correct direction. And if no, what are other options?
Thanks a lot for taking time to answer and read my question!
PS. Please do let me know if you want any other details.
Related
I have a Spring boot project which I want to host on an AWS-EC2 instance. I was able to create its image using Git-hub, Jenkin and docker. I was also able to successfully pull and run this image in the Linux console of my AWS-EC2 instance.
According the tutorial I was following I should have been able to open the project now using the public IPv4 DNS but the response I got was that it refuse to connect.
I know that this usually has to do with Inbound rules so I added a rule to allow all traffic but it didn't help.
For anyone who wants to know:
Git-hub repository: https://github.com/SalahuddinShayan/telecom
Docker-Hub repository: https://hub.docker.com/repository/docker/salahuddinshayan/telecom
Command I used to run the image in AWS:
docker run -p8081:8081 --name final-app --link docker-mysql:mysql salahuddinshayan/telecom
Security Groups:
Networking Details:
Here is the Error:
I am completely stumped by it. Does anyone an idea on what to do to fix this?
Please check if your client is calling the right protocol, e.g. http vs https.
You are transmitting on port 8081. http://3.110.29.193:8081/ works fine from the EC2 side. 404 status is raised, so this is a client side error, not a server side error.
It means that no firewall is blocking traffic and a process (your app) was found that listens on IP:Port that you require. The problem is that the process it encountered (your app) is sending only a WhiteLabel Error Page, which is a generic Spring Boot error page that is displayed when no custom error page is present. So the issue is with the Spring app itself and not with EC2 or with connection. In other words: the traffic can reach your Spring app, but your Spring app has nothing to say in response.
As a side note, after deploying your app I would advise to refine the inbound traffic rules to allow only the traffic you want. There is no need of allowing all traffic on all ports.
I added a dockerhub image to the the Container Registry. Then, succesfully ran the image in Cloud Run. The image is https://hub.docker.com/r/atmoz/sftp. The thing is I'm unable to access the sftp server from FileZilla client.
Any thoughts on what could be going on? Any alternatives? I've considered running the image in a Compute Engine container so that I can actually generate a private key to use it to connect from the FileZilla client. Would appreciate to hear from your wisdom.
You can run an SFTP server in Cloud Run, but you cannot connect to the server.
The reason is that Cloud Run only supports HTTP Requests and responses. SFTP uses a different protocol (SSH) that is not supported by Cloud Run.
I successfully installed Datalab on Dataproc cluster and I followed the instructions in this tutorial, but when I try to use Datalab on Google Chrome, it shows "This connection is not secure".
When I try to modify the connection with notebook interface from http://cluster-name-m:8080 to https://cluster-name-m:8080, the page didn't load.
Can someone please help me to solve this issue :'(
If you follow the Cluster web interfaces documentation it has you:
Create an SSH tunnel
Setup a SOCKS proxy to use that tunnel
Not open random ports that have no security
I'd recommend you follow those directions, as they will provide access to the web interfaces but encrypt all traffic via the SSH tunnel. While the browser will indicate the connection does not use SSL, the mechanism that is moving data from your browser to the cluster (SSH) is encrypting all data in the tunnel. Unfortunately, the browser does not know about this so it creates a warning.
I am trying to run my springboot API on AWS however when i try to connect to the endpoint the error Site cannot be reached IP refused to connect. This my first time working with AWS.
I created a linux instance and connected to it using filezilla. Afterwards i added my jar to a folder which i created on the linux instance using filezilla. I started the springboot project and its running but the problem is that i cannt seem to connect to the endpoints. Am i missing something, how do i connect to my endpoints.
The other thing to note is that i enabled https on my API and added swagger also.
You need to enable relevant ports in the instances' Security Group.
Look at this to create a new Inbound rule for the specific port.
You can go to the aws console, (here I am assuming you have deployed to us-east-1 if its something else, go to the relevant region.
Open up the relevant security group, and then click edit Inbound roles.
I am new to aws and have very little networking knowledge.
I have set up an EC2 instance and installed sucessfully
MongoDB
my nodejs app server and
my angular web app on the same instance
I tried to access my web server from a browser using
https://ec2-54-255-239-55.ap-southeast-1.compute.amazonaws.com:3443/
and
ec2-54-255-239-55.ap-southeast-1.compute.amazonaws.com:3443/
but have not been successful so far. The error message :
This site can’t be reached
ec2-54-255-239-55.ap-southeast-1.compute.amazonaws.com refused to connect.
I need help