DO Loadbalancer SSL termination multiple certificates

Posted May 14, 2018 4.2k views
Load BalancingHigh Availability


So i’m using the new DO Loadbalancer, works fine. But will it be possible in the future to use multiple certs per load balancer?

I have 2 app droplets with multiple vhosts/domains. Now i can only use ssl termination with one certificate, it would be nice to attach multiple certificaties.


  • Hello, did you manage to solve this issue? I have the same situation here…

  • hi Cadu,

    Solved this by buying a multi-domain cert, not ideal but it works. I hope DO will make this possible in the future.

  • Do DO load balancers support multiple SSL certificates yet? Are wildcard certificates still the only way to handle multiple domains?

  • YES!!! This is a weird restriction considering that one could have a load balancer pointing to a reverse-proxy that contains several sites/apps etc. Use case, nomad cluster with Fabio proxy! As well, I am referring to the autogenerated letsencrypt certs.

    Any updates on this matter would be great.

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.

Submit an Answer
3 answers

I just hit this issue too.

Already using Lets Encrypt i another setup, but thought using DO load balancer would ease management. Our webpage alone has 5 domains - running a load balancers for each domain is a weird restriction.

Your load balancer checks the health of its registered instances using either the default health check configuration provided by Elastic Load Balancing or a custom health check configuration that you specify. The health check configuration contains information such as the protocol, ping port, ping path, response timeout, and health check interval. An instance is considered healthy if it returns a 200 response code within the health check interval.

If the current state of some or all your instances is OutOfService and the description field displays the message that the Instance has failed at least the Unhealthy Threshold number of health checks consecutively, the instances have failed the load balancer health check. The following are the issues to look for, the potential causes, and the steps you can take to resolve the issues.


Health check target page error
Connection to the instances has timed out
Public key authentication is failing
Instance is not receiving traffic from the load balancer
Ports on instance are not open
Instances in an Auto Scaling group are failing the ELB health check

Bit of a disappointing answer; but they have resolved this problem on the Digital Ocean App platform. Where you can have loads of different domains connected with SNI Certificate selection.