0

My website doesn't generate any HTTP certs using LetsEncrypt, doesn't even return a response. This is for test purposes so is using a basic NGINX image that I want to serve over HTTPS.

I have an ingress type that looks like this:

   apiVersion: v1
kind: Service
metadata:
  name: nginxtest
  labels:
    app: nginx
spec:
  selector:
    k8s-app: traefik-ingress-lb
  ports:
    - name: http
      port: 80
      targetPort: 80
      protocol: TCP
  selector:
    app: nginx

---

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: nginx-ingress
  annotations:
    kubernetes.io/ingress.class: traefik
spec:
  rules:
  - host: nginx.example.com
    http:
      paths:
      - path: /
        backend:
          serviceName: nginxtest
          servicePort: http

My TOML Config Map looks like the below:

apiVersion: v1
kind: ConfigMap
metadata:
  name: traefik-conf
  namespace: kube-system
data:
  traefik.toml: |
    defaultEntryPoints = ["http","https"]
    debug = false
    logLevel = "ERROR"
    #Config to redirect http to https
    [entryPoints]
      [entryPoints.http]
        address = ":80"
        compress = true
        [entryPoints.http.redirect]
        entryPoint = "https"
      [entryPoints.https]
        address = ":443"
        compress = true
        [entryPoints.https.tls]
    [api]
      [api.statistics]
        recentErrors = 10
    [kubernetes]
    [ping]
      entryPoint = "http"
    [accessLog]
    [acme]
      email = "a@b.com"
      storage = "certs/acme.json"
      acmeLogging = true
      entryPoint = "https"
      OnHostRule = true
      #caServer = "https://acme-staging-v02.api.letsencrypt.org/directory"
      [acme.httpChallenge]
        entryPoint="http"

Any help is appreciated, please point out any errors.

Rutnet
  • 1,533
  • 5
  • 26
  • 48
  • 1
    Enable the Debug and check the logs, we need more details to locate the issue. – Crou Dec 21 '18 at 12:34
  • Turns out my the errors were to do with LetsEncrypt rate limiting my domain requests. Once I switched the domain name out this worked. Thanks for pointing me in the right direction with debug switch. – Rutnet Dec 22 '18 at 02:59
  • @Rutnet, Can you enclose your investigation within the answer for further community members research? – Nick_Kh Dec 28 '18 at 10:33
  • This wasn't actually an issue. I was sending too many requests to the chosen domain name and the LetsEncrypt rate limit kicked in. Once I changed the domain name to something else, HTTPS loaded fine. – Rutnet Jan 07 '19 at 16:56

0 Answers0