I need to give the root URL for my ec2 server, can someone please give me the syntax of the root URL of a general ec2 server? (Just so I know what syntax to give my specific web server details in). I tried this one:
http://ec2-**-**-**-**.eu-west-1.compute.amazonaws.com/
but it doesn't work, flash builder says that it is invalid, but it works in a browser so I can't see how it can be.
To answer your question, assuming what you mean is what is the general syntax for an EC2 server DNS name?
It's
ec2-<external-ip-with-dashes-instead-of-dots>.<region>.compute.amazonaws.com
so yes:
ec2-**-**-**-**.eu-west-1.compute.amazonaws.com
is correct for the eu-west-1 region.
Now it looks like you have another problem, either you are not allowing port 80 on your security group associated with the instance or you are just not running anything on port 80. i.e. apache, nginx, etc.
Related
I'm facing an issue with my ec2 instance. Until now, I had an ec2 instance working with an IP like this: ec2-xx-xxx-xxx-xxx.compute-1.amazonaws.com.
Now I configured an elastic IP to make that instead of use the default domain uses one of my own.
Something goes wrong because now a receive a 403 if I make a request pointing to my new domain.
I'm check that I'm still able to connect to my Ubuntu server 20.04 LTS through SSH. Only have to change the host name to my new domain.(I'm using PuTTy)
Searching on internet if found that the problem can be that my machine still have the old domain in some config files. I don't have experience with Ubuntu servers. I try to find the http.conf file or the apache2 directory in etc., but no one is present.....
I don't know what to do next.
I have to change some configuration file? In that case, which one?
I leave you some images from my machine:
Root
etc folder
For further information, the security group of my ec2 instance have these rules:
Any help will be appreciated. Thanks
-EDIT
I'm trying to access the server, making a request, with Postman like this.
And that is the error:
For more information. I implemented my ec2 using this video:ec2 video
And I changed the domain with that video:link ec2 with namecheap domain
I'm afraid it is a propagation issue, that takes more time than the 48 hours, because now it starts to works without changing absolutely nothing. Sorry
It appears that your requirement is to point bochogame.com to an Elastic IP address.
You can do this by using a DNS Service, such as Amazon Route 53. You would create a A-Record record that points that domain name to the IP address.
If you are unfamiliar with these concepts, I recommend watching some YouTube videos such as DNS with AWS Route 53 - YouTube.
My machine is configured in ubuntu. It has a python flask service. I use a domain that I bought with a certificate that I generated at aws.
I am concerned about the security of my service and wanted to use a tool called flask ip ban. However the IP I receive from users both on the console and in the code using '' request.remote_addr '' are specific ip's of the same domain that starts with 172.31. *. *
Even if I use proxies the ip of my pc is always 172.31.4.145 and this is neither my ip nor my proxies.
I tried to use the ip ban flask but I ended up banning literally all users, because those few ip's that seem to bring my clients, without me knowing how, were banned
I would like to know how to do to show the real ip's. Could it be because my service is micro? Or because am I using Load balancer with my certificate? I couldn't get any relationship with flask or python
You are behind a load balancer which mean the IP address you are seeing is the one from your load balancer. As Mark advise above you can use the x-forwarded-for header but what I wanted to add is that you have a wonderful blog post that explain it all.
https://aws.amazon.com/premiumsupport/knowledge-center/elb-capture-client-ip-addresses/?nc1=h_ls
I remotely hosted the Realm Server on AWS and I got it to run and I am able to connect to the Realm Dashboard, but I'm not sure how to connect to the Realm Object Server using the Realm Browser App.
I was able to find the admin access token but since the server is remotely hosted what would the Server URL be? The Realm website tutorial provided us with realm://127.0.0.1:9080, but that's only for when the Realm Server is locally hosted.
You have to replace the localhost IP (in our examples, that is listed as 127.0.0.1) with the hostname or IP address of your EC2 machine. Please note that the numbers/addresses below are made up. They are just to serve as an example.
Typically, this will be something of the form 198.51.100.38, giving you the root URL: realm://192.51.100.38:9080. To this, you obviously have to append the path of the Realm file that you are trying to access.
Alternatively, you should be able to use the EC2 hostname, if you prefer that. Your EC2 hostname should look something like ec2-198-51-100-38.compute-1.amazonaws.com. You should check your EC2 dashboard for more information to get these proper values.
More information:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html
We just created an AWS Windows Server 2012 Instance and now want to Redirect our Domain (bought and managed by 3rd Party) to this server.
we followed the two steps at the 1st ranked answer here: How redirect a domain to Amazon EC2 Machine?
While we managed to create and associate the elastic IP, the problem seems to be step 2 now: actually we have setup a A record at our current domain manager but still doesnt work. If we enter our domain at browser it seems to load for something and then stops after some seconds
We are very beginners and wondering where we need to put the lets say "index.html" or so like we did at our previous Webspace hoster. In other words, if the user access our server through the elastic ip, which direction the browser is firstly trying to enter?
The standard pattern is
... in aws route53 create a Hosted Zone
... by default it auto gives you Type NS and SOA copy the set of 4 values under your Type NS (similar to)
ns-125.awsdns-15.com.
ns-642.awsdns-16.net.
ns-1653.awsdns-14.co.uk.
ns-1473.awsdns-56.org.
... now get into your Domain Registrar and edit Nameservers by using above list
... upon deploying your aws cluster it will give you a loadbalancer value similar to
af327bdd34eca101010100a02debd892-11516969089.us-east-1.elb.amazonaws.com
... get into your aws route53 hosted zone console pick your domain
... hit Create Record Set on the right pick Type A
... IMPORTANT pick Alias YES see doc
... click in box Alias Target empty out field ... then choose above mentioned loadbalancer
I think you have security and firewall issues,
Check following items step by step:
Enter your EC2 IP address in your browser; you should see your app home page.
If you can't reach your server response by direct IP address, check your security group, inbound tab, you must open port 80 to source 0.0.0.0/0
Each time you see your home page by direct IP address in the browser you can go to next steps for domain and route53.
I tried to telnet 52.59.50.150 80 to your instance and it timed out so that means your HTTP port 80 is not open. Add below security rule to your security group. And then check your domain it will work.
We are actually wondering how the whole Setup should actually work.
We have dropped the Index.html on c:
Lets say we are trying to request the Microsoft Server EC2 through the elastic IP. How it is even trchnically possible that the server is finding and responding with exactly this Index.html?
Thats completely a blackbox for us besides the question if the security groups/rules/ports are established correctly...
I have solved my problem. Just for people that have the same problem:
Besides the points mentioned above you have to setup IIS (Microsoft Internet Information Service) on your server in order to redirect your domain to specific "folders" / index.htmls
i've registered a .com domain name. At the Amazon Web Services account i own, I have already set up the DNS zone,i've changed the nameservers at my registrar's panel and i've created an A-record in my AWS DNS zone,too. I think i've done all the preparation needed. But my website is not opening!
This is not a DNS propagation time-requiring issue,by the time i did all the above stuff about 5 days ago (DNS had enough time to be refreshed globally in any ISP). Also via ipduh.com i can see that all the nameservers are correctly configured and recognised, as well as the *.mydomain.com A record which points at my AWS instance's IP.
What possibly would be wrong guys? :/ i've done anything i know and i've followed also the directions i've found in SO and i had no luck till now :/
Any suggestion and help would be highly appreciated :D
Thank you in advance guys!
I'm going to assume that the DNS is set up properly, and that the A record is pointing at the IP address assigned to your instance.
If this is a new AWS account, you're probably running in a VPC. Did you make sure that you allocated a public IP address to the instance? If your IP is 10.something, that's the internal, private IP address and you won't be able to use that. You'll need to allocate an Elastic IP and associate it with your instance, then update your DNS settings.
Next, make sure that the web server is up & running? If you log into the instance, what happens if you wget localhost? You might not get the page you're expecting if you're running multiple name-based virtualhosts, but you should get the index page for the default web site.
OK, so how you're sure the web server is running. Next thing to do is check the security rules. When you created your instance, you had give it the name of a security group. The default is, strangely enough, called "defaut". Take a look and see if port 80 is open. If not, open it up to the world (0.0.0.0) and see if you can access the web site now.
None of this helps? Reboot your instance and see if it starts working when it comes back up - it's possible that you're on a bad host, and rebooting will bring it up on different hardware.