Certificate details of internal load balancer
written-by
Rishabh Agrawal
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
legacy-article
learn-legacy-article-disclaimer-text
Issue
- There are few static IPs for private S2S connectivity, over different services like webserver and database.
- However, for webserver whose static IP is 172.xx.xx.xx, the certificate is updated at the external load balancer level and shared the same certificates with the integrated application to import them.
- When this is being called using a private static IP, it is giving certificate errors. But the same issue is not being faced over public IP.
- Are there are any certificates that needs to be added or updated at the internal load balancer whose IP is 172.xx.xx.xx?
Resolution
- There are 2 different types of Load Balancer for each case:
1. The external HTTPs Load balancer (also known as ingress) that has a public IP 34.xxx.xxx.xx to receive external connections from customers and supports SSL termination.
2. The internal passthrough network load balancer that is used to receive inbound connections privately inside a Site to Site VPN for specific services like the webserver 172.xx.xx.xx. This kind of load balancer is used for layer 4 (TCP/UDP) connections and does not support SSL termination.
- Moreover, it is not possible to add or update the internal load balancer (172.xx.xx.xx) once this is not supported by design.
did-this-article-resolve-your-issue