I am having an issue and not able to resolve it.
I have XAMPP instaled on Azure Virtual Machine. I created a virtual host, instead of the localhost/application I am running an app as application.local in the browser. It works fine and it opens a web app.
Now, I am trying to access it over Azure VM public IP address and it doesn't work, any suggestion on what I can do to make it work?
I tried disabling the firewall and it has no luck.
It seems your application works fine inside the VM, but you can't access the application through the VM public IP address outside. Then you need to check if there is an NSG rule that allows the traffic to the port listening by the application. If no, you need to create one rule for the port.
Related
I'm not a networking guy and I have this requirement and I'm not sure if this is possible or not. By the way, my requirement is I have two App that running on my Azure Virtual Machine it's SSRS and Asp Net Core running on IIS, the condition right now is my SSRS running on Port 441 and my IIS App run on port 443. So this will make the URL have to include the port when we need to access the SSRS page, then my Company says they don't like to add the port in the SSRS URL and then they suggest to add a subdomain for the SSRS and IIS and make it running on port 443. But as My Understanding, this is can only be Achieve if I have two different public IP rights which mean two Azure Virtual Machine one for the SSRS and one for the IIS because when I only have one public Address it still needs different port right for the different App. I just need to clarify Is this true? Or it can be done somehow
An Azure Virtual Machine (VM) has one or more network interfaces (NIC) attached to it. Any NIC can have one or more static or dynamic public and private IP addresses assigned to it.
In this case, You could assign two public IP addresses to the same Azure VM. Here is the document--- Assign multiple IP addresses to virtual machines using the Azure portal
If you need to add more than one NIC to virtual machine, see the steps by steps in this blog for windows VM and Linux VM.
I am new to Qliksense and Azure. We have installed Qliksense in Azure Virtual machine. Trying to access the Qliksense hub/QMC URL (https://xxx.intranet.myclient.com/hub) from the internet/outside the azure Network, but was unsuccessful. The url is working well in the intranet.
Azure VM has a private ip address.
Created inbound rules in NSG(Network Security group) at Azure to open ports 443,80, 4244.
2.Created firewall inbound rule in VM server to open ports 80, 443, 4244, 4243, 4248, 4242
Added the url to the host white list at the virtual proxy side in Qlik QMC
May I know what wrong am doing or what I am missing here?
Firstly, If you want to access qlik url to work from the internet, you need a public IP address attached to the Azure VM or load balancer service like Azure application gateway in front of Azure VM with a public IP address. Refer to this. If you have no public IP address, you can directly deploy one and attach to the VM network interface on the Azure portal. Try to restart the Azure VM or refresh VM.
Then, make sure you have a DNS map which is pointing FQDN xxx.intranet.myclient.com to your VM public IP address. You can try to access the Qliksense hub/QMC URL like https://PublicIPaddress/hub first.
Also, you can run the command netstat -anbo as the administrator in the CMD to check if the port is listening on Qliksense service. Try to telnet or Test-NetConnection the Qliksense URL before you access the Qliksense URL on the remote machine.
If the above all are no effect, you can look at this. Let me know if this works.
I'm banging my head on this seemingly simple task. I'm trying to stand up a Redhat VM in Azure. I've tried both the resource group approach and the classic approach.
I currently have a classic deployment. I've installed httpd via yum. I confirm that I can SSH to the server via the virtual IP. Once in, I start httpd and I can perform wget http://localhost/ and get the content that I expect.
However, when I attempt to connect to the virtual IP from my local browser, there is no response. I've also tried creating a static public IP with no success.
I have created an HTTP "endpoint" in Azure portal. I set the public and private ports to 80 with a protocol of TCP. There are no ACL values (I assume it's defaulting to allow everything).
There is no network security group assigned to the VM.
Still no success. What else am I missing!?
Well, if you really setup an endpoint on the portal to allow port 80, the only thing thats left is the firewall on the Linux VM itself, allow port 80 on the firewall and you are good to go
1) service httpd restart and 2) service firewalld restart did the trick
I just setup a Windows Server VM on my Azure space, but for some reason the IIS that is configured on it isn't available publicly...
I can open the IIS welcome page trough localhost on the server, but no trough visiting the external IP or the cloudapp.net domain.
Something to note is that I actually CAN reach the server trough MSTSC with the external IP adress...
I tried:
Shutting off the Windows Firewall
Opened endpoints on the non-classic management Azure system
I binded the ip's to the cloudapp host
Checked the online Azure documentation
So I resolved it... Don't know if it's supposed to be that way, but be sure that in Azure your "Source port" is defined to be * and not 80, or other.
That will absolutely not work if you're not defining "*".
Screenshot of Azure here
I've just set up a windows azure VM and installed IIS on it.
When I remote desktop onto the box I can see the default IIS website fine but I can't get this to serve on the web from the IP address of the box.
I've opened up port 80 on windows firewall and also added an endpoint for port 80.
I've tried to access it with the firewall completely turned off also but to no avail...
I cant work out if there is anything else I need to do to get this working?
Add endpoints for port 80 (http) and port 443 (https) to the VM in the Azure portal (tip: this can be automated with powershell or the Azure cli).
Remote desktop to the machine. Open the Windows firewall control panel and allow traffic to port 80 (http) and port 443 (https) or just turn it off ... the firewall is ON by default (tip: can also be scripted through the VM agent / powershell).
Go to the Azure portal and find the cloudapp.net subdomain for your VM (actually the cloud service) your VM is running under. Try accessing the site with that domain. If that doesn't work, try browsing to http://localhost on the server (remote desktop) to make sure IIS works and troubleshoot from there.
Modify the DNS records of your custom domain to use a CNAME to the .cloudapp.net domain. If you need A records make sure to use the public IP of the cloud service (just ping the .cloudapp.net domain to find it or look in the Azure portal).
You might want to look into Azure Websites or Azure Cloud Services (web roles). Those are a lot easier to manage and a lot cheaper. They still offer most of the functionality.
What fixed the issue for me was to go into the Azure Portal, browse to 'Network Security Groups', select the VM and then create an inbound rule to allow traffic to port 80.
Note: Also ensure that the inbound rule to port 80 is added and enabled on the actual VM.
Well, I deleted the existing VM and Cloud service and started again - all worked fine out of the box this time.
How annoying! The only thing I did notice was that before my cloud service had the same name as my VM - this time they had different names so that might have been what was causing the issue.
Cheers
For the newer VMs and pre-configured setups (2015+), it's possible your setup is using an azure asset called "Public IP". If so, you can set a custom DNS name label in it, inside "Configuration". Note that this name will consider any type of region used when creating the VM (e.g. my-site.brazilsouth.cloudapp.azure.com).
It's good to remember that for testing purposes, it still suffices to use the value of the public IP that is randomly designated to you.
The VMs are actually accessed via a Cloud Service (well they are for me). Azure created a Cloud Service automatically to be the scaling engine/load balancer on the front of the VM. I have to connect to the web site via that cloud service, not the VM directly.
Its possible you were using the internal IP rather than the external IP.
The sites have to use the internal IP address in the bindings section of IIS. However, in your dns you will need to use the external IP. This is presumably since the 'internal IP' is just a virtual one that Azure uses to map traffic from the external network to the VM's inside azure.
You should find both the internal and external IP's are visible on the VM's desktop.
Switch off TLS 1.3 in the Registry Editor.
This is what worked for me as of writing this in Mar 2021.