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

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

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi there,
It looks like the load balancer isn’t actually picking up the certificate, since both ports 80 and 443 are still showing as plain TCP with no cert attached.
I’m not 100% sure, but a couple of things you could check: make sure the Service is of type LoadBalancer, try only specifying either the certificate ID or the certificate name (not both), and confirm that port 443 is exposed and mapped correctly in the Service spec.
If that doesn’t work, it might be worth reaching out to the DigitalOcean support: https://do.co/support
Heya, @marekray
It sounds like the load balancer isn’t attaching the certificate because the Service isn’t fully configured for HTTPS termination.
Make sure the Service is type LoadBalancer and that the certificate is referenced either by name or by ID, not both.
Hope that this helps!