I am trying to set up a new traffic manager profile for a pair of application gateways which are located in east and west using this guide. These two gateways have some path based routing backends and rules. The routing method I want to choose for my new traffic manager is "Performance" and I want to add the public IPs of gateways as endpoints to it. But I am getting the following error.
Screeshot
In the dropdown for "Public IP Address", there is also this message - "cannot be associated with traffic manager endpoint". Any leads would also be appreciated.
The error observed here is due missing DNS Name on Public IP used. Please have look at this documentation for additional details. You can follow this documentation to associate an Azure DNS record for your public IP
Related
I am trying to create a new traffic manager profile of either Performance or Weight configuration but I keep getting stuck when trying to add an Azure Endpoint.
I have a two public IP inside of Azure, one with an optional DNS name, one with out.
When I try to add either of these as an endpoint, I get the following error message:
The one with a dns name on it:
Failed to save configuration changes to Traffic Manager profile 'profilename'. Error: Endpoint target type, 'DomainName', is not allowed for this profile. Valid values are: IPv4Address.
The one without a dns name:
No DNS name is configured.
If i choose External Endpoint and add the IPv4 directly it will work.
I tried with several different Traffice Manager profiles.. Is there a secret that I am missing out on? I am stuck..
Usually, There are three types of endpoint supported by Traffic Manager:
Azure endpoints are used for services hosted in Azure.
External endpoints are used for IPv4/IPv6 addresses, FQDNs, or for services hosted outside Azure that can either be on-premises or
with a different hosting provider.
Nested endpoints are used to combine Traffic Manager profiles to create more flexible traffic-routing schemes to support the needs
of larger, more complex deployments.
...
Azure endpoints are used for Azure-based services in Traffic Manager.
The following Azure resource types are supported:
PaaS cloud services. Web Apps Web App Slots PublicIPAddress resources
(which can be connected to VMs either directly or via an Azure Load
Balancer). The publicIpAddress must have a DNS name assigned to be
used in a Traffic Manager profile.
In this case, when you add a public IP address in the same subscription as an Azure endpoint, it will grey out if no DNS name configured in the Azure portal. You could add it when the public IP address configured with Azure provided DNS name like somedns.westus2.cloudapp.azure.com, this works on my side.
For example, there is a public IP address with the DNS name used for an Azure load balancer frontend.
The instance is running fine. I am using linux os and apache-tomcat-8.0.33 server. I can access from private ip using putty But when i am trying to access the same through the public ip, it is not accessible. I have seen the security configurations all ports are enabled.
Can anyone help me how to reslove this issue
inbound image
I faced the same issue recently; I was not able to access the website which I hosted on Ec2 server Via public IP.
Check 1:- the First step would check your AWS security group and make sure all the inbound traffic rules are fine.
Check 2:- Windows firewall can also play a role in disallowing the access via public IP. Create a new Rule for allowing access for HTTP and HTTPS ports (80,443).
Steps
a. Go to control panel -->Windows Firewall ---> Advanced Settings.
b. Select the Inbound rules from the left Menu.
c. Select New Rule from the Right panel.
d. Allow access to ports 80 and 443.
In my case, everything worked fine once I created a new rule in windows firewall under Inbound Rules.
You opened your amazon web console
You go to Amazon EC2 Security Groups
You should have a default group for inbound rules (see below)
You click on Modify inbound rules (modifier les règles entrantes in French here)
Once done, you add your public ip with the subnet you want
I've added my IP public address and you should be good.
Regardless of the number of ports open in your security group, if you must access your ec2 instance using it's public IP, over the internet, you must assign an internet gateway (IGW) to the subnet your ec2 instance belongs to
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Internet_Gateway.html
As you mentioned and others answers, you can find the problem by following this steps:
1- Try telnet to your server by public IP address on port 80, if it opens go to the next step, if not open you have two possible issues:
security group (Check your inbound rules)
web server settings (Check your web server settings and find why not listening on port 80)
2- If telnet was working, so you have not the connectivity issue, now track your web server access log by tail command and try open a page by the browser. If you see your request in the access log, but it does not return the correct value you expected, so you should check your web application.if you can't see your request, check your web server settings.
I have two machines in different accounts.
I'm trying to make a connection between them.
So I added a rule that allows all traffic from the external and internal one.
Outbound allows all traffic for both machines but there's no connection at all.
one machine : 172.31.43.115
second machine : 172.31.26.95
I pinged. No response.
I also tried Trace route, but also no response
I searched for a guide on Google, but had no luck.
I understand that I have to do Route.
How can I do that? Is there any solution for that?
it looks like (based off the IPs) you are mistaking the private IP with the public IP. Check your EC2 console again, and click on the instance and look at the bottom metadata. On the right column nearish to the top there should be public IP.
If you want to communicate them externally, you should attache an EIP ( elastic ip ) to them and allow in Security group. If you need to communicate internally , you should create vpc peering.
Currently I just create an instance on Amazon EC2 and I can ssh to the server. I installed Apache2 server and it is up but when I try to access via its public ip, then the browser come with timeout error. I have no idea related to EC2 and your idea would be worthwhile for me.
Thanks
From EC2 Docs:
If you are unable to see the Apache test page, check that the security group you are using contains a rule to allow HTTP (port 80) traffic. For information about adding an HTTP rule to your security group, see Adding Rules to a Security Group.
By default all traffics port are blocked for security reason. You need to add Inbound rules for allow http traffic(port 80)
You can add inbound rules by following these steps:
From EC2 Dashboard find "Security Groups" and then "Create Security Group"
Give a security group name and description and rules like shown in picture and then create security group.
Now you can access your ec2 public IP from anywhere.
Hi I am having my own domain mydomain.ac.in and i am having my own server (windows 2008) and a Public static IP.
Now i want to host my site in my own server.
Please give me the step by step information to get it done.
Thanks.
You need to register your domain with some DNS hosting service (DNS provider), there is such an astronomic number of these on the web that I do not want to spam the site. Google.
Also, collocation center where you keep this server (and from where you have probably obtained that public IP) may also provide DNS services.
From the other side, any computer can be configured as the name server but this will probably not work Internet wide and can be used inside the local network only (combined with DHCP service). If there is an easy way to make this Internet wide, I would also be very interested in, but I doubt.
Your operating system is not much relevant to this question.
I registered my domain already in ernet by indian Government and I got my Public Static IP from BSNL India. I hosted my site already and i am able to access my site already using the ip. Now i want to map my domain with the server that i have so that i can access my domain using a domain name.
I tried the steps in http://www.hosting.com/support/dedicated/dns/setdns#additional.. But when i add the name server information it says cannot resolve hostname??? that s why i want to know where i am making mistake..
I once again tried the steps at http://www.hosting.com/support/dedicated/dns/setdns and got it right..Now i have updated the name server info at my domain registrar ernet and waiting for it to be updated. Thanks fo the people helped me