I have Google Cloud instance (RHEL 6.7 and I have an application working on HTTPS protocol on port 10614). This is perfectly working when I am using the internal IP https://10.125.0.7:10614/home.
I have an external IP with which I am connecting to this machine which is 104.118.81.121.
So i would like to expose my application to the internet using this IP address. Could you please help, how should I be doing the mapping for this?
I have already created the firewall rule for this, but it is not working.
You need to open port 10614 in your Google Cloud Console firewall. You can use the following link: https://console.cloud.google.com/networking/firewalls/list?project=your-project-id. Just replace your-project-id with your project id.
Related
I am working with Minikube on VM (VirtualBox - Linux Ubuntu). I need to access the ONAP Portal App service's GUI through the internet browser, which I can't.
I have deployed ONAP Portal App on Minikube and now I want to access its GUI through the internet browser. There was no external IP when I looked at "kubectl get services". As I found I used the Minikube tunnel. Now, I have the external IP by the portal-app service (which is by the way same as the cluster IP), but I can't get to its GUI - the website is unreachable/unable to connect. Then I tried "minikube service portal-app --url", which showed me different IP with the correct port, but in the browser I got to the apache tomcat and not to the portal-app. What am I missing?
Thanks for any advice.
I have 3 websites running on my server, all of them on different ports. One is on port 80 and it works fine, the other one is on port 88 and it also works fine. Today I deployed a third one on port 8080, opened the port in Firewall.
I can access it with http://localhost:8080/, with 127.0.0.1:8080 and with it's internal IP address. I can't access it using the external IP address for some reason. I tried accessing it locally using the external IP address and I tried from another computer.
It is worth noting that the website on port 8080 is almost identical to the one on port 80.
Initially I thought it was a firewall issue but I disabled the firewall and tried again and I get the same result (The website took too long to respond).
I am using Windows 10 on the server.
Any ideas as to why this is happening?
I figured out the answer. I am using an EC2 instance from Amazon Web Services for a server. I forgot to go into the console in AWS and open the port there too. I did that and now it's working as it should.
There could be couple of reasons.
Cloud Provider(AWS) Specific
Check your subnet's ACL rules. Both ingress and egress
Check the security group attached to the instance. It should allow ingress
on that port/protocol
Windows Server Firewall: All windows servers and desktops have firewall running which blocks any non-standard traffic. Make sure to add a custom rule to allow the traffic that you want to allow. I found this https://computingforgeeks.com/how-to-open-a-port-in-windows-server-firewall/ link helpful
I am new in Azure. I want to open IIS to external access. My VM is WS 2012 R2, and all is configured by default.
The only access I get from internet is RDP, which I use for admin.
I tried both FTP and HTTP, but none works to find my server from outside. Same for nslookup.
If I do an RDP connexion on sp16fu12.westeurope.cloudapp.azure.com, it succeeds.
If I try http://mymachine.westeurope.cloudapp.azure.com, it fails.
I have added inbound and outbound security rules for protocols http and ftp on my network security group.
DNS is default Azure DNS.
What is wrong ?
According to your description, please ensure you had open ports(FTP and HTTP) on Azure network security group and Windows Firewall.
1.Open Ports on Azure network security group(NSG Inbound rules).More information about NSG please refer to this link.
Notes:Azure NSG could associate on NIC and subnet. Please refer to this link.
2.Open ports on Firewall. More information about open ports on Windows Firewall please refer to this link.
I deployed a web site into a Azure VM and did the following
1) Create a HTTP Endpoint with TCP protocol and port 80 (both
internal and external) for the VM
2) configure the web site to be assigned with the internal IP
assigned
I can browse to the site within the VM, but can not connect to it from external using either the DNS or the public VIP assigned by Azure. the browser said "can not connect to [vip]".
Have I missed any steps or any advice on how to trouble shoot this issue?
If this is a "normal" VM and not a Cloud Service then you need to connect to the VM and open port 80 in the Windows Firewall directly on the machine as well.
In the end, i found it is caused by the selection of "direct connect" at the Endpoint setting.
Untick it, it works...
I am hosting an asp.net MVC 3 application on my local IIS 7.5 server. People can connect using my IP and the port I set. I can connect by typing localhost:port in a browser. If I type the IP:port however, the browser says it cannot connect.
Using wamp and other hosting programs (and even IIS at one point if memory serves), I could always connect using my own IP.
How can I set IIS to let me connect using my own IP? Or is the problem somewhere else?
My firewall is disabled, the port is forwarded and other people can connect just fine (people outside my LAN) and I have tried 3 browsers.
You cannot connect to your IIS using static IP, but, howerver you can by adding your Static IP as a lookup entry.
Please check this link:
How to Edit Your Windows Hosts File
The article explains how to resolve the IP to reach the IIS locally.