Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ncp ingress not accessable when internal tls enabled #641

Open
heww opened this issue May 11, 2021 · 0 comments
Open

ncp ingress not accessable when internal tls enabled #641

heww opened this issue May 11, 2021 · 0 comments
Assignees
@heww
Labels
blocked-by-upstream component/ingress kind/bug Something isn't working known-issue Issues we have known but no solution or plan to introduce fix yet

Comments

@heww
Copy link
Collaborator

heww commented May 11, 2021 •
edited by bitsf

curl -k https://core.harbor.domain get the following response when using ncp(NSX-T Container Plugin) ingress with internal tls enabled.

<html>
<head><title>400 The plain HTTP request was sent to HTTPS port</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<center>The plain HTTP request was sent to HTTPS port</center>
<hr><center>nginx/1.16.1</center>
</body>
</html>
@steven-zou steven-zou added kind/bug Something isn't working release/1.0.1 component/ingress known-issue Issues we have known but no solution or plan to introduce fix yet blocked-by-upstream and removed release/1.0.1 labels May 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@heww heww

Labels
blocked-by-upstream component/ingress kind/bug Something isn't working known-issue Issues we have known but no solution or plan to introduce fix yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@heww @steven-zou