I have created one service called **fleetman-webapp**:

```
apiVersion: v1
kind: Service
metadata:
 name: fleetman-webapp

spec:
 selector:
  app: webapp

 ports:
  - name: http
    port: 80
    nodePort: 30080

 type: NodePort

```

also, a pod named **webapp**:

```
apiVersion: v1
kind: Pod
metadata:
 name: webapp
 labels:
  app: webapp
spec:
 containers:
 - name: webapp
   image: richardchesterwood/k8s-fleetman-webapp-angular:release0

```

I have checked the **minikube ip**:

***192.168.99.102***

But when I type in the browser **192.168.99.102:30080**, the webapp is not reachable:[![enter image description here](https://i.stack.imgur.com/v6GiX.png)](https://i.stack.imgur.com/v6GiX.png)

Please note that I use Ubuntu latest version. I have verified furthermore if proxies and firewalls are active:

**cat /etc/environment**:

```
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"

```

**iptables -L**:

```
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy DROP)
target     prot opt source               destination         
DOCKER-USER  all  --  anywhere             anywhere            
DOCKER-ISOLATION-STAGE-1  all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere             ctstate RELATED,ESTABLISHED
DOCKER     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     all  --  anywhere             anywhere            

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

Chain DOCKER (1 references)
target     prot opt source               destination         

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
target     prot opt source               destination         
DOCKER-ISOLATION-STAGE-2  all  --  anywhere             anywhere            
RETURN     all  --  anywhere             anywhere            

Chain DOCKER-ISOLATION-STAGE-2 (1 references)
target     prot opt source               destination         
DROP       all  --  anywhere             anywhere            
RETURN     all  --  anywhere             anywhere            

Chain DOCKER-USER (1 references)
target     prot opt source               destination         
RETURN     all  --  anywhere             anywhere 

```

I have also disabled **ufw** in Ubuntu, but no success, the url **192.168.99.102:30080** .

Would you help me please ? thanks in advance for your answer.
['https://Stackoverflow.com/questions/60710171', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/8384029/']
I have had the same issue and have been trying to solve that for the last 2 days I have tried to install ingress addon:

```sh
minikube addons enable ingress

```

and also tried to run :

```sh
minikube tunnel

```

looked for a way to allow the host machine to access the container IP address but apparently couldn't find a way to do that.

If you run minikube on docker:

```sh
minikube start --driver=docker

```

you won't be able to access the **minikube IP** from your **host machine** since the minikube container's IP address would by accessible through `DockerDesktopVM` but not from your host machine.

You could run **minikube** on another driver such as `VirtualBox` or `Hyperv`, and that might help.

```sh
minikube start --driver=hyperv
minikube start --driver=virtualbox

```

Read more about the [minikube drivers](https://minikube.sigs.k8s.io/docs/drivers/)

> 
> In fact, that's really annoying if you don't have enough resources on your computer to run both the Docker desktop VM and the minikube VM at the same time and will eventually slow down your computer.
> 
> 
> 

To solve that `docker-desktop UI` for `Mac and Windows` provides an easier alternative compared to minikube, which you could simply [activate the Kubernetes feature on your docker-desktop UI](https://docs.docker.com/desktop/kubernetes/):

![enable-kubernetes](https://user-images.githubusercontent.com/49565791/150873987-48b80313-a396-4906-8785-6f2149320c61.png)

once it is setup you can right click on the docker desktop icon > Kubernetes
![docker-desktop](https://docs.docker.com/desktop/images/kube-context.png)

To verify now that your deployement/service works properly:

```sh
kubectl apply -f /file.yaml

```
If you are running minikube in a Windows, then minikube must run as an Administrator command prompt window.