AWS Load Balancer https configure not working - amazon-ec2

I have created Load Balancer on AWS EC2. But when I open URL with https I get such error:
ERR_SSL_PROTOCOL_ERROR
I have port following port conf. for LB
My app is running on port 3000. Can anyone help to solve this issue?

port 80 should redirect to port 443
443 should talk to an endpoints using port 3000
please remember about opening up relevant ports on security groups.

Related

Not able to access Springboot deployed at GCP compute instance at port 8080

I have a springboot app running at port 8080 at one of the GCP instance. I have turned on the firewall rules to allow traffic to port 8080. But still when I try to access the deployed port [ http://external-IP:8080/myservice ] I am not able to. From browser I get "This site can be reached" and from postman I get the error Error: connect ECONNREFUSED :8080
I am not sure if there are any specific firewall rules or anything that I need to set.

Google Cloud Load Balancer

I created a java app and I deployed into a Google Cloud Compute Engine, then I created a Load Balancer, but when I try to access to Load Balancer Frontend IP with port 443 it redirect to port 80
You can create forwarding rules that reference an IP address and port(s) on which Load balancer accepts traffic. Here are the conceps for forwarding rules 1.
IP address specification 2
To add a forwarding rule, please follow the steps here 3

Accessing webserver on AWS ec2 (Ubuntu)

I am running a webserver on an Ubuntu ec2 instance. The service accepts http connections over port 8080.
The next step is to allow the service to be e accessible using public_DNS:8080. I've modified the security group to accept all incoming traffic on 8080. However, I get connection refused when I try it on my browser. I am guessing it is something to do with the Ubuntu firewall.
I have very little idea about it. Any suggestions on how I can proceed to resolve this?

Not able to access EC2 custom port from remote machine

I have hosted web application (developed in PHP) on Amazon EC2 micro instance. As per default setting, i can access 80, 22, 443 and 3306 ports from remote locations means from Home(terminal window) using telnet command.
I want to open another custom TCP port XXXXX. I have added that port in Security Group. when i am trying to connect that port through telnet command it is always show "Connection refused".
I have been trying to solve this issue for 3 days but could not get successful solution.
Help would be really appreciated.
Thanks
Adding a port in security group (inbound) ensures that the port can be accessed from outside. Please check following
Is the port open for anywhere (0.0.0.0/0) or for a custom IP. If for custom IP, please check the IP of your machine (search 'what is my ip' on google).
Is there any application listening on the port on EC2 machine.

Unable to connect to moquette in aws ec2 instance

I am new to MQTT and have been trying to implement MQTT MOquette on AWS EC2, i tried the configuration and installation of broker on my machine and was able to connect and test it from client, however when i do the same from Aws EC2 instance i can see the ports 1883, 8080 listening to 0.0.0.0 ip address but when i connect from client i am not able to connect.
While configuring host in local machine i provided 0.0.0.0 for host and ports 1883, 8080 and on AWS server i provided the private ip for host and ports are 1883, 8080. I have added rules in security groups to allow tcp on 1883 & 8080.
My question is what should be the host value i should use on AWS like private ip or aws url like 'ec2-XX-XX-XXX-XX.us-west-2.compute.amazonaws.com' and what would be the url from which i could access broker from client like 'tcp://ec2-XX-XX-XXX-XX.us-west-2.compute.amazonaws.com' or the IP
What would i be doing wrong here ?? stuck with this issue
Thanks All
After some search i was finally able to solve the issue, i was always checking for security groups where everything was right but i missed adding rule in ec2 instance firewall for the ports 1883, 8080. Once its done i was able to connect to the broker from external clients.
Thanks for all who tried to help.

Resources