ECS with ALB and SSL certificate issue: net::ERR_CERT_COMMON_NAME_INVALID
up vote
0
down vote
favorite
I have an aws ECS setup and using ALB for the load balancer. The container task is running on port 8080. I have also added an HTTPS listener
with SSL Certificate from ACM, which forwards the requests to the container.
Now I have one issue here. When using curl or postman to contact the load balancer's DNS name, I get the response from the app perfectly. But when using the very same DNS name in my frontend and running in frontend app locally (localhost:3000), and the request is generated from Chrome I get the following error:
net::ERR_CERT_COMMON_NAME_INVALID
How can I resolve this issue?
I also tried deploying the app to my test env, so instead of localhost
, I have https://example.com
which now matches the Domain name of the Certificate (*.example.com)
. But still same results.
amazon-web-services google-chrome docker amazon-ecs aws-alb
add a comment |
up vote
0
down vote
favorite
I have an aws ECS setup and using ALB for the load balancer. The container task is running on port 8080. I have also added an HTTPS listener
with SSL Certificate from ACM, which forwards the requests to the container.
Now I have one issue here. When using curl or postman to contact the load balancer's DNS name, I get the response from the app perfectly. But when using the very same DNS name in my frontend and running in frontend app locally (localhost:3000), and the request is generated from Chrome I get the following error:
net::ERR_CERT_COMMON_NAME_INVALID
How can I resolve this issue?
I also tried deploying the app to my test env, so instead of localhost
, I have https://example.com
which now matches the Domain name of the Certificate (*.example.com)
. But still same results.
amazon-web-services google-chrome docker amazon-ecs aws-alb
Can you post the complete output of curl -vvv "URL" here?
– Mohit Kumar
Nov 8 at 20:22
I get this now: curl: (35) schannel: SNI or certificate check failed: SEC_E_WRONG_PRINCIPAL (0x80090322) - The target principal name is incorrect.
– shwz
Nov 9 at 8:51
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have an aws ECS setup and using ALB for the load balancer. The container task is running on port 8080. I have also added an HTTPS listener
with SSL Certificate from ACM, which forwards the requests to the container.
Now I have one issue here. When using curl or postman to contact the load balancer's DNS name, I get the response from the app perfectly. But when using the very same DNS name in my frontend and running in frontend app locally (localhost:3000), and the request is generated from Chrome I get the following error:
net::ERR_CERT_COMMON_NAME_INVALID
How can I resolve this issue?
I also tried deploying the app to my test env, so instead of localhost
, I have https://example.com
which now matches the Domain name of the Certificate (*.example.com)
. But still same results.
amazon-web-services google-chrome docker amazon-ecs aws-alb
I have an aws ECS setup and using ALB for the load balancer. The container task is running on port 8080. I have also added an HTTPS listener
with SSL Certificate from ACM, which forwards the requests to the container.
Now I have one issue here. When using curl or postman to contact the load balancer's DNS name, I get the response from the app perfectly. But when using the very same DNS name in my frontend and running in frontend app locally (localhost:3000), and the request is generated from Chrome I get the following error:
net::ERR_CERT_COMMON_NAME_INVALID
How can I resolve this issue?
I also tried deploying the app to my test env, so instead of localhost
, I have https://example.com
which now matches the Domain name of the Certificate (*.example.com)
. But still same results.
amazon-web-services google-chrome docker amazon-ecs aws-alb
amazon-web-services google-chrome docker amazon-ecs aws-alb
asked Nov 8 at 11:03
shwz
7111
7111
Can you post the complete output of curl -vvv "URL" here?
– Mohit Kumar
Nov 8 at 20:22
I get this now: curl: (35) schannel: SNI or certificate check failed: SEC_E_WRONG_PRINCIPAL (0x80090322) - The target principal name is incorrect.
– shwz
Nov 9 at 8:51
add a comment |
Can you post the complete output of curl -vvv "URL" here?
– Mohit Kumar
Nov 8 at 20:22
I get this now: curl: (35) schannel: SNI or certificate check failed: SEC_E_WRONG_PRINCIPAL (0x80090322) - The target principal name is incorrect.
– shwz
Nov 9 at 8:51
Can you post the complete output of curl -vvv "URL" here?
– Mohit Kumar
Nov 8 at 20:22
Can you post the complete output of curl -vvv "URL" here?
– Mohit Kumar
Nov 8 at 20:22
I get this now: curl: (35) schannel: SNI or certificate check failed: SEC_E_WRONG_PRINCIPAL (0x80090322) - The target principal name is incorrect.
– shwz
Nov 9 at 8:51
I get this now: curl: (35) schannel: SNI or certificate check failed: SEC_E_WRONG_PRINCIPAL (0x80090322) - The target principal name is incorrect.
– shwz
Nov 9 at 8:51
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53206421%2fecs-with-alb-and-ssl-certificate-issue-neterr-cert-common-name-invalid%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you post the complete output of curl -vvv "URL" here?
– Mohit Kumar
Nov 8 at 20:22
I get this now: curl: (35) schannel: SNI or certificate check failed: SEC_E_WRONG_PRINCIPAL (0x80090322) - The target principal name is incorrect.
– shwz
Nov 9 at 8:51