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
Related
I am new to ECS. I have an Apollo React web app client and an Apollo Express server API. I have deployed React client (:80) successfully via ECS Getting Started. Also configured HTTPS and it can be accessed at https://my-application/
Now I am trying to deploy API server (:8081). I created a new task definition and created a new service by following this tutorial - https://www.youtube.com/watch?v=3Kr_455zMk4
I chose 80:HTTP for Production listener port and same load balancer name with React client, created a new target group: ecs-default-cluster-server-api. Path pattern: /server-api* and 1 for Evaluation order. However it does not work for me.
I want to deploy server API at https://api.my-application/ or any other suitable path. How do I do it?
I have deployed the Pimcore DAM app on Amazon EC2 instance. The Pimcore product offers REST services to integrate it with PHP which I am able to access successfully from the POSTMAN client but the same services are not working when I am trying to access it from my local WAMP server through cURL request. It's giving me the below error -
"cURL Error #:Failed to connect to 13.58.32.47 port 80: Timed out" [13.58.32.47 - Public IP of the EC2 instance]
Could you please help me in order to resolve this connectivity issue?
Inbound Rules - [1]: https://i.stack.imgur.com/JJIW8.png
Outbound Rules - [1]: https://i.stack.imgur.com/2ACYF.png
Thanks & Regards,
Anup
I have an AWS EC2 instance acting an FTP server as described here:
https://www.xadmin.net/how-to-setup-ftp-on-aws-ec2-instance/
The EC2 instance has a security group with custom TCP rules to allow connections from any IP.
Connections via FileZilla and other FTP clients are successful.
I have a Spring Boot app that connects to this EC2 FTP server and it works locally. However, when deployed to Heroku, attempts at listing files or getting specific files hangs without any error.
The Spring Boot app uses the full public URL to the EC2 instance as the FTP host (ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com).
How do I allow the Heroku app to access the EC2 FTP server?
Most probably the server is misconfigured and sends its internal IP address in the FTP PASV command response.
While FileZilla and many other FTP clients can workaround that, Heroku probably cannot.
Check FileZilla log file for:
Server sent passive reply with unroutable address in FileZilla.
If this is the case, you will need to fix your FTP server.
I have installed PencilBlue on AWS EC2 instance. i have started PB by using the command pbctrl start
Now, how can I access the PencilBlue login page?
Just like you run any other web server on EC2, you start the service, open the port in the Security Group, and then open the website in your browser.
I have two servers on EC2. One hosting my php application and other hosting my redis server. I am managing my php session and data on redis server. So on my php server I gave the ip:port as session save path and got the error FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught exception 'RedisException' with message 'Connection closed'
So I search on the web and came to know that I need to open port 6379 on my redis instance for inbound traffic. I opened it by setting a custom TCP setting in AWS security group but still the port is coming closed to outside world. But I am able to listen to the port on redis server itself. Am i Missing anything in the process? Do I need to make any other change somewhere. Please guide me on this. I am very much new to AWS management
On Instance 1: I am using php-fpm, nginx and phpredis
On Instance 2: Using Redis