# Troubleshooting Traefic Errors In kubernets

**URL:** <https://community.traefik.io/t/troubleshooting-traefic-errors-in-kubernets/25520>\
**Category:** Traefik v3 (latest)\
**Tags:** kubernetes-ingress\
**Created:** [December 11, 2024, 10:34am UTC](https://community.traefik.io/t/troubleshooting-traefic-errors-in-kubernets/25520 "2024-12-11T10:34:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![LearningNetrunner](https://avatars.discourse-cdn.com/v4/letter/l/eada6e/32.png) [@LearningNetrunner](https://community.traefik.io/u/LearningNetrunner)\
**Post date:** [December 11, 2024, 10:34am UTC](https://community.traefik.io/t/troubleshooting-traefic-errors-in-kubernets/25520/1 "2024-12-11T10:34:47Z")

</div>

Hello,  
I got those logs from the traefik pod:

```auto
ERR Cannot create service error="service port not found" ingress=app-ingress namespace=default providerName=kubernetes serviceName=app-frontend servicePort=&ServiceBackendPort{Name:app-fro-port,Number:0,}
ERR Cannot create service error="service port not found" ingress=app-ssl-ingress namespace=default providerName=kubernetes serviceName=app-frontend-service servicePort=&ServiceBackendPort{Name:app-fro-port,Number:0,}

```

I am trying to undestrand what I am missing to do with Traefik.  
I got a test app that is reachable on port 3000.  
I would like to have people reaching the app via https, so port 443 passing trough Traefik and using a ssl certificate issued with cert manager.  
What are the steps that I should implement?  
Am I understanding the log correctly if I read that it says that traefik can not find the port app-fro-port or is it something else?  
Is this a good guide to achieve that [Configure HTTPS in Traefik with cert-manager and Let’s Encrypt | by Faturrahman | Medium](https://medium.com/@faturrahmanmakruf/configure-https-in-traefik-with-cert-manager-and-lets-encrypt-db60960e2283)

---

<div class="post-metadata">

**Author:** ![LearningNetrunner](https://avatars.discourse-cdn.com/v4/letter/l/eada6e/32.png) [@LearningNetrunner](https://community.traefik.io/u/LearningNetrunner)\
**Post date:** [December 11, 2024, 1:07pm UTC](https://community.traefik.io/t/troubleshooting-traefic-errors-in-kubernets/25520/2 "2024-12-11T13:07:38Z")

</div>

I am getting more errors.

```auto
ERR Skipping service: no endpoints found ingress=app-ingress namespace=default providerName=kubernetes serviceName=app-frontend servicePort=&ServiceBackendPort{Name:app-frontend,Number:0,}
ERR Skipping service: no endpoints found ingress=app-ssl-ingress namespace=default providerName=kubernetes serviceName=app-frontend servicePort=&ServiceBackendPort{Name:app-frontend,Number:0,}

```

i'm using traefikv3.2.1 and Certificate Manager 1.16.1

---

<div class="post-metadata">

**Author:** ![LearningNetrunner](https://avatars.discourse-cdn.com/v4/letter/l/eada6e/32.png) [@LearningNetrunner](https://community.traefik.io/u/LearningNetrunner)\
**Post date:** [December 13, 2024, 8:11am UTC](https://community.traefik.io/t/troubleshooting-traefic-errors-in-kubernets/25520/3 "2024-12-13T08:11:50Z")

</div>

As [qurro\_007](https://serverfault.com/users/1139499/qurro-007) said: Something miss in your deployment and service Your Deployment uses the following label: io.kompose.service: app-frontend But your Service selector is: app: app-frontend This mismatch prevents the service from finding the pods created by the deployment. Fix the Service selector to match the Deployment label: Update 010-app-service.yml: spec: selector: io.kompose.service: app-frontend. it seems now the service can find the pods.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/containo/original/2X/b/bd81ebdb578656e76e56ff3cc3eed021d3ba132d.png) [@system](https://community.traefik.io/u/system)\
**Post date:** [December 16, 2024, 8:12am UTC](https://community.traefik.io/t/troubleshooting-traefic-errors-in-kubernets/25520/4 "2024-12-16T08:12:20Z")

</div>

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.