Report this

What is the reason for this report?

Lets Encypt ssl certificate is not working

Posted on September 9, 2025

Hello. I have domain registered and pointing at my load balancer. I can access my app using domain name: http://mydomain.com -> this works. Now I would like to add ssl cert for my domain. What I did:

  1. in Settings - Security I added Let`s encrypt certificate for my domain
  2. in yaml file I have
apiVersion: v1
kind: Service
metadata:
  name: clinic-serv
  annotations:
    service.beta.kubernetes.io/do-loadbalancer-certificate-id: "3dda0252-5b19-45e7-9922-b00a6ea29a35"
    service.beta.kubernetes.io/do-loadbalancer-name: "clinic-load-balancer"
    service.beta.kubernetes.io/do-loadbalancer-protocol: "https"
    service.beta.kubernetes.io/do-loadbalancer-certificate-name: "rubinowa"
    service.beta.kubernetes.io/do-loadbalancer-disable-lets-encrypt-dns-records: "false"
    service.beta.kubernetes.io/do-loadbalancer-redirect-http-to-https: "true"

Output: http://myDomain.com/ > WORKS

https://myDomain.com/ > DOESNT WORK - I get PR_END_OF_FILE_ERROR in my browser. When I run:

doctl compute load-balancer get 2ebd2163-43b6-43d6-934b-3a9c87cd026e

I get

entry_protocol:tcp,entry_port:80,target_protocol:tcp,target_port:80,certificate_id:,tls_passthrough:false entry_protocol:tcp,entry_port:443,target_protocol:tcp,target_port:443,certificate_id:,tls_passthrough:false

It looks like annotations from my yaml file weren`t applied. What am I missing?

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.