# Cannot access my ASP.Net MVC service at all

**URL:** <https://discuss.kubernetes.io/t/cannot-access-my-asp-net-mvc-service-at-all/22270>\
**Category:** microk8s\
**Tags:** microk8s\
**Created:** [December 12, 2022, 8:26am UTC](https://discuss.kubernetes.io/t/cannot-access-my-asp-net-mvc-service-at-all/22270 "2022-12-12T08:26:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![eaindra-tih](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/eaindra-tih/32/11364_2.png) [@eaindra-tih](https://discuss.kubernetes.io/u/eaindra-tih)\
**Post date:** [December 12, 2022, 8:26am UTC](https://discuss.kubernetes.io/t/cannot-access-my-asp-net-mvc-service-at-all/22270/1 "2022-12-12T08:26:18Z")

</div>

I am new to Kubernetes, and would like to access my [ASP.Net](http://ASP.Net) MVC web application service, but it just gets timed-out when I `curl` the external IP address generated by the Metallb load balancer from microk8s. However, when I describe the service created, the endpoint is generated correctly as shown below.

```auto
Name: sensory-service-loadbalancer
Namespace: default
Labels: <none>
Annotations: <none>
Selector: app=sensory-aromalab
Type: LoadBalancer
IP Family Policy: SingleStack
IP Families: IPv4
IP: 10.152.183.141
IPs: 10.152.183.141
LoadBalancer Ingress: 10.64.140.44
Port: <unset> 81/TCP
TargetPort: 8080/TCP
NodePort: <unset> 30243/TCP
Endpoints: 10.1.136.170:8080
Session Affinity: None
External Traffic Policy: Cluster
Events:
  Type Reason Age From Message
  ---- ------ ---- ---- -------
  Normal nodeAssigned 84s (x215 over 17h) metallb-speaker announcing from node "tihg-nbg-test-1" with protocol "layer2"

```

The home HTML page is displayed when I type `curl 10.1.136.170` (the endpoint address), but the connection gets refused when I try to `curl` the IP and LoadBalancer Ingress addresses.

This issue doesn’t happen to other applications whose frontend and backend services are deployed separately, which means I can `curl` them locally with no issue, but the timed-out problem or the connection being refused issue is happening to this [ASP.Net](http://ASP.Net) Core application.

My yaml files for the deployment and service are as mentioned below. It would be great to hear any suggestions to this issue.

deployment.yaml

```auto
apiVersion: apps/v1
kind: Deployment
metadata:
  name: sensory-deploy
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      app: sensory-aromalab
  template:
    metadata:
      labels:
        app: sensory-aromalab
    spec:
      containers:
      - name: aromalabweb
        image: ewptih/sensoryaroma
        imagePullPolicy: IfNotPresent
        ports:
          - containerPort: 8080

```

service.yaml

```auto
apiVersion: v1
kind: Service
metadata:
  name: sensory-service-loadbalancer
  namespace: default
spec:
  type: LoadBalancer
  selector:
    app: sensory-aromalab
  ports:
  - protocol: TCP
    port: 81
    targetPort: 8080

```

---

<div class="post-metadata">

**Author:** ![Yalton](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/yalton/32/11560_2.png) [@Yalton](https://discuss.kubernetes.io/u/Yalton)\
**Post date:** [January 17, 2023, 8:31am UTC](https://discuss.kubernetes.io/t/cannot-access-my-asp-net-mvc-service-at-all/22270/2 "2023-01-17T08:31:50Z")

</div>

> [@eaindra-tih](#):
>
> sue doesn’t happen to other applications whose frontend and backend services are deployed separately, which means I can

Hello eaindra-tih,  
Microk8s team is advising on issues created on github for Microk8s, Do you mind to open a threat there?

> **[Issues · canonical/microk8s](https://github.com/canonical/microk8s/issues)**
>
> MicroK8s is a small, fast, single-package Kubernetes for datacenters and the edge. - Issues · canonical/microk8s