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.
Related
I have a Virtual Box VM hosted on my desktop, using bridged mode.
On that VM I have installed a one node Service Fabric cluster (secured with a self-signed x509 cert).
I have setup my router to send ports 19000-19100 to that guest machine IP Address.
I am on AT&T Fiber so I am forwarding those ports to a router and then the router forwards them on to the guest OS at a specific IP address.
From my host machine I am able to get to the service fabric explorer and I can deploy services to it from visual studio.
I am not able to deploy to it from azure devops. My friend is not able to see the explorer either.
In DevOps I have configured a service connection, put the certificate in it, etc. In my pipeline I am writing to the hosts file (my public IP and the host name I need sit.mysite.com as an example). One thing to note is that I was previously able to deploy to SF when I had the cluster running on my main machine (as opposed to in a VM as it currently is)
A friend (living in another state) is not able to view my service fabric explorer. I provided the cert to him, he's imported it. He has an entry in his hosts file also. When he goes to https://sit.mysite.com:19080 (the SF explorer address), he gets a 403, not authorized. But it is correctly picking up the cert. He can also ping my IP address so we have connectivity.
Whatever is stopping him from hitting my SF is likely what is preventing me from the ability to deploy from azure devops, but I have no idea what it would be...
Any ideas?
Figured it out. Turns out my cluster config file was referencing localhost for the node as opposed to the IP (or a dns name) and that made the fabric not respond to requests from outside.
"nodes": [
{
"nodeName": "vm0",
"iPAddress": "IP_ADDRESS_HERE",
"nodeTypeRef": "NodeType0",
"faultDomain": "fd:/dc1/r0",
"upgradeDomain": "UD0"
}
],
I have a few virtual machines that are set up on bridge network. One of this virtual machines (HDP sandbox) has the web ui and I wanna use it but it's IP is not opened on the browser. What's should i do?
As i understand it,your vm has a web server.if so,check the status of apache service.If it is not running,you have to start it.
service apache2 status
service apache2 start
after you run the commands above(command may be different due to linux distro),
enter ip address into the web browser.
also,you must be sure that HDP services are running.
So I'm setting up a vm on virtualbox with Centos. I was able to configure everything fine and with a bridge connection, I have access to the internet and the VM has an IP within the network. From the host I can ssh into the vm without a problem. Now here's the issue, for some reason if I load up the gui from the browser I can access https sites but not http sites.
I noticed this after I tried to install some applications but all mirrors were timing out. Anyone have any clue what this could be?
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 have created an ASP.NET application on my local machine. In order to test this application in IE 6, I have created a VPC. I am trying to connect to this web application through the VPC. However, I cannot connect to it. I can however connect to the internet.
What am I doing wrong?
Can you ping from the virtual PC? If not, you have network configuration issues.
Otherwise, check firewalls, and make sure that port 80 is open and sending traffic to IIS.
there are many possibilities. first I'd consider would be any firewall rules on the ASP.NET side preventing incoming HTTP connections.
What is the URL you are using to go to your site? If you are using localhost, you will need to change that to the actual IP address of your development machine, as localhost on the Virtual PC image will be a different IP address than localhost on the development machine.