I followed these steps :
I created two EC2 machines hosting a single wordpress (EFS) at port 8000, the website is accessible in both machines using their ip:8000
I created a target group for both machines (port 8000)
I created an ELB that listens to port 80 and attached it the the target group
I have the domain hosted in Route53 (domain.com)
I pointed the A record of sub.domain.com to the alias of the ELB
dig sub.domain.com will give nothing.
I have been waiting for more than 48 hours.
Do you see any possible problem with my configuration ?
Related
I need two containers in one task defination. One for wordpress and another for nginx, however the traffic should route from nginx to wordpress. This should be done using aws fargate.
How to connect two containers ? so that nginx should send traffic to wordpress container !
In AWS Fargate, all containers in the same task can access each other at 127.0.0.1 or localhost over their respective ports.
Let's say you have Nginx configured to listen on port 80 and WordPress configured to listen on port 9000. To setup Nginx and Wordpress as you describe, you would have your Application Load Balancer forward traffic to the Nginx container on port 80, and you would configure Nginx to forward traffic to WordPress at 127.0.0.1:9000.
I have installed IIS on docker, disabled any firewall and configure no-ip for access externalLy, and finally configured no-ip on my router with port fowarding...
I have configured iis and congirured local port 91 to 80 container port...
from local 'http://pincopallino-no-ip:91' compare correctly the default iis page, but externally network I get 'err_connection_timed_out'....
after, I installed apache server on docker, and configured always local port 91 to 80 container port, and apache page it works both indoors the network and outdoors 'http://pincopallino-no-ip:91'
there is a solution?
perfect, now I restarting my computer, ad if run externally !
I used terraform to deploy my k8s cluster, and i used kubectl to deploy nginx on my worker nodes. Again using kubectl and creating a LoadBalancer targeting the nginx deployment on port 80 worked perfectly fine. I wanted to test out using an ALB, rather than an ELB.
I deleted the ELB, and then used the EC2 interface to setup a target group.
The target group uses port 80, is on the same vpc, and is targeting the two worker nodes.
Next I created an ALB, which is internet facing uses the same security group as the nodes, and again is on the same VPC. Its listening on port 80 and forwarding traffic to my target group.
I cant access nginx using the DSN name. I'm pretty sure it has to do with my port configuration?
Kubernetes does not natively support alb's.
https://github.com/kubernetes-sigs/aws-alb-ingress-controller
So I have two domains:
http://firstexample.com
http://secondexample.com
on my router I currently have portforwarding so that when someone goes to http://firstexample.com, they see the website that my computer with internal IP 192.168.0.15 is hosting
How can I set it up so that if someone goes to http://secondexample.com, they would see the website that my other computer, with internal ip 192.168.0.16 is hosting?
Both of my computers have the same public IP.
Is it a setting on my router I would change? Or would godaddy allow me to configure something?
No it is not possible to listen for two domains on the same IP/port configuration, using just Layer3/4 functionality alone. Most of the web servers do it based on the Host field in the request. If you are okay with using two ports on your router, that's possible eg. you can do something like following port forwarding
<router_ip>:80 -> 192.168.0.15:80
<router_ip>:8080 -> 192.168.0.16:80
But the problem with that is anyone trying to access http://secondexample.com should always access it as http://secondexample.com:8080 which is very inconvenient.
Here's another alternative you can do -
run a webserver on say 192.168.0.15 like nginx or something and create two backends one for each http://firstexample.com and http://secondexample.com . Refer nginx docs for how to do it. You'd not need three machines for that firstexample.com can run on 192.168.0.15 (except not on a standard port 80 but on a port 8080 say) and secondexample.com would run on another machine. And then add only following entry on your router port forwarding
<router_ip>:80 -> 192.168.0.15:80 # assuming ngninx is listening on port 80.
I am assuming both firstexample.com and secondexample.com do resolve to your router IP address.
I have a server to which I connect using VPN. I have a deployed a site on this on IIS server. URL for the site is "http://localhost:8080/mysite". when I use this Url on server it is opening up.
But When I use its ip address Lets say http://172.x.x.x:8080/mysite it is not accessible. (not on the server not from my dev machine (Which uses VPN)).
But if I disable firewall on server then It is accessible using the IP and port 8080 also or if I change the port number of deployed site to 80 then also I can access it(without disabling firewall).
Is there any way so that I can use my port number 8080 and also don`t need to disable firewall on server.