Internal Server Error when trying to get my service to direct to my pod

kube · June 29, 2022, 12:17pm

Hey all hope you can help me with this issue. It's driving me bonkers.
It just shows 'Internal Server Error' when I visit the site.

Here is my issue: (I have both my IngressRoute shown here)

github.com/bitnami/charts

[bitnami/ghost] Service Unavailable

opened 10:51PM - 28 Jun 22 UTC

jotcodeofficial

### Name and Version bitnami/ghost 19.0.6 ### What steps will reproduce th…e bug? When I visit my site I get: 'Internal Server Error' The blog pod is alive and fine with no errors. The https cert for the page is working fine too, the issue is getting the service pointing to right thing, which I think is https port issue. When I check the logs of the pod: ``` ghost 05:56:37.35 INFO ==> ** Ghost setup finished! ** ghost 05:56:37.56 INFO ==> ** Starting Ghost ** Love open source? We’re hiring Node.js Engineers to work on Ghost full-time. https://careers.ghost.org/product-engineer-node-js - Inspecting operating system ``` Here is the relevant part of my values file: ```yaml service: ## @param service.type Ghost service type ## type: ClusterIP ## @param service.ports.http Ghost service HTTP port ## @param service.ports.https Ghost service HTTPS port ## ports: http: 80 https: 443 ## Node ports to expose ## @param service.nodePorts.http Node port for HTTP ## @param service.nodePorts.https Node port for HTTPS ## NOTE: choose port between <30000-32767> ## nodePorts: http: "" https: "" ## @param service.clusterIP Ghost service Cluster IP ## e.g.: ## clusterIP: None ## clusterIP: "" ``` here is my ingress route: ```yaml apiVersion: traefik.containo.us/v1alpha1 kind: IngressRoute metadata: namespace: example name: example-ingress-route annotations: kubernetes.io/ingress.class: "traefik" cert-manager.io/issuer: example-issuer traefik.ingress.kubernetes.io/router.entrypoints: web traefik.frontend.redirect.entryPoint: https tls: - hosts: - example.com secretName: example-com-tls spec: entryPoints: - web routes: - match: Host(`example.com`) middlewares: - name: https-only,remove-www kind: Rule services: - name: example-blog-ghost namespace: example port: 80 ``` If I change the port in here to 80, I just get a 404 page not found when I visit the site here is my secure ingress route: ```yaml apiVersion: traefik.containo.us/v1alpha1 kind: IngressRoute metadata: namespace: example name: example-secure-ingress-route annotations: kubernetes.io/ingress.class: "traefik" cert-manager.io/issuer: example-issuer traefik.ingress.kubernetes.io/router.entrypoints: websecure traefik.frontend.redirect.entryPoint: https spec: entryPoints: - websecure routes: - match: Host(`example.com`) kind: Rule services: - name: example-blog-ghost namespace: example port: 443 tls: domains: - main: example.com options: namespace: example secretName: example-com-tls ``` I had this deployed before on version: v13.0.13 It instead had this (and worked for me) ```yaml ghostProtocol: https ghostHost: example.com ghostPort: 443 ghostPath: / service: type: ClusterIP ## HTTP Port ## port: 80 ``` my middleware is just: ``` apiVersion: traefik.containo.us/v1alpha1 kind: Middleware metadata: name: https-only namespace: example spec: redirectScheme: scheme: https permanent: true ``` Thanks for any assistance! ### What is the expected behavior? That when the user goes to https://example.com that it shows the ghost blog installation.

This is the issue that made me think it's a traefik issue:

github.com/bitnami/charts

Enabled ghostEnableHttps and traefik config

opened 05:29PM - 01 Jun 22 UTC

closed 07:40AM - 02 Jun 22 UTC

Mantany

### Name and Version bitnami/ghost ### What steps will reproduce the bug? … Steps: 1. using k3s with traefik 2. set ghostEnableHttps: true 3. visit the domain Try the same config without https enabled, works but produces "mixed content" errors - readinessProbe and startupProbe are good - The logs on the ghost pod looking fine - when I try to access the site via domain, I get an internal server error (traefik error site) - when I try to access the site via the IP address of the pod, firefox says "SSL_ERROR_RX_RECORD_TOO_LONG" I think it has something to do with the missing header information "x-forwarded-proto: https" Following the docs for [traefik](https://doc.traefik.io/traefik/v1.7/configuration/backends/kubernetes/) the additional annotations doesn't seem to do the trick. ``` ingress.kubernetes.io/ssl-proxy-headers: "X-Forwarded-Proto: https" ingress.kubernetes.io/ssl-redirect: "true" ``` Does anybody has the same issues? ### Are you using any custom parameters or values? ``` ghostHost: "example.com" ghostPath: / ghostEnableHttps: true ingress: enabled: true pathType: ImplementationSpecific apiVersion: "" hostname: examle.com path: / annotations: kubernetes.io/ingress.class: traefik cert-manager.io/cluster-issuer: letsencrypt-prod tls: true ``` ### What is the expected behavior? I should see the website, when I visit the domain ### What do you see instead? internal server error ### Additional information _No response_

The middleware was just:


apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  name: https-only
  namespace: example
spec:
  redirectScheme:
    scheme: https
    permanent: true

Topic		Replies	Views
Port : http inside IngressRoute => block all IngressRoute Traefik v2 kubernetes-crd	4	1048	September 29, 2020
Internal Server Error on all routes - are my routers and services configured properly? Traefik v2 docker	1	589	January 29, 2023
Please help -everything even HTTPS worked for minutes now internal server error on every backend Traefik v1 docker	1	933	September 16, 2019
Troubleshooting Traefic Errors In kubernets Traefik v3 (latest) kubernetes-ingress	3	219	December 13, 2024
Unable to route to HTTPS service Traefik v2 kubernetes-ingress	1	1240	October 19, 2022

Internal Server Error when trying to get my service to direct to my pod

Related topics