- Newest
- Most votes
- Most comments
The first thing to check is to make sure that your DNS is working. You can do this with nslookup
or dig
or there are many third-party tools - just make sure that prod.mydomaine.org
resolves to staging.example.net
and then to the IP address of the ELB.
Next, if you're using HTTPS the ELB must offer both certificates. That's because the browser will try to connect to prod.mydomaine.org
but the ELB doesn't know that the connection has been redirected from there. If it is expecting the browser to connect to staging.example.net
that's the certificate that it will offer. And the browser doesn't know about staging.example.net
so it will throw an error about certificates being invalid.
This blog post covers multiple certificates using AWS Certificate Manager but it might help you with your custom certificate.
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Thank you very much . This work perfectly