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.

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

[Feedback]Document update with "http: server gave HTTP response to HTTPS client" error. #4762

Open
anilkumar1619 opened this issue Jan 21, 2025 · 3 comments
Assignees
Labels

Comments

@anilkumar1619
Copy link

anilkumar1619 commented Jan 21, 2025

Could you add below error to below document?

Error from server: Get https://aks-node-IP:10250/containerLogs/namespace/pod-name/container-name: http: server gave HTTP response to HTTPS client

I received above error and the solution from below document worked and it seems both are related. So, request you to review and update the document if possible.

https://learn.microsoft.com/en-us/troubleshoot/azure/azure-kubernetes/connectivity/tunnel-connectivity-issues

@anilkumar1619 anilkumar1619 added the Feedback General feedback label Jan 21, 2025
@kthakar1990 kthakar1990 self-assigned this Feb 4, 2025
@kthakar1990
Copy link

@anilkumar1619 - thank you for raising this. Our team will look into this and make necessary updates.

@buysoft
Copy link

buysoft commented Feb 27, 2025

@anilkumar1619 , What part of the tunnel connectivity issues worked for you to resolve this? I am experiencing the same at the moment.

@gideondk
Copy link

Same here, a clean install in west-europe through Terraform results in a cluster that doesn't support Kubectl properly on most nodes (giving the above error), also, metrics servers don't work / Azure Portal also can't reach the nodes when using additional node pools.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants