Skip to main content
Solved

"kubectil get nodes "getting error Unable to connect to the server: net/http: TLS handshake timeout

  • January 23, 2024
  • 3 replies
  • 1217 views

Forum|alt.badge.img+8

hello experts,

getting below error while trying  to check the status with kubectl...any clue will be appreciated.

"kubectil get nodes "

getting error Unable to connect to the server: net/http: TLS handshake timeout

 

Regards

Sujeeth S

Best answer by Sujeet Saxena

Thanks all for your help. we have identified the issue.

Since we were not using the default port 22 hence we have to update the .Json and .Psm1file..

where we put -Port 22022 instead of -P 22022 on Common.psm1 file ,after fixing this we were able to resolved the issue.

Below is the line which we fixed in common.psm1file

“ ssh -t -i $pvtKeyFilePath  "-p 22022 “

 

View original
Did this topic help you find an answer to your question?

3 replies

paguin
Sidekick (Partner)
Forum|alt.badge.img+11
  • Sidekick (Partner)
  • 140 replies
  • January 23, 2024

Check if internet in enabled on middle tier/kubernetes 

regards 

pankaj 


Forum|alt.badge.img+14
  • Superhero (Employee)
  • 158 replies
  • January 23, 2024

Hi Sujeet,

Please check that port 16443 is open between your IFS Windows Management server and the IFS Remote server.

Test-NetConnection -ComputerName <ifs-remote> -Port 16443

If it is being blocked by a firewall, please check with your network administrator to allow the connection. While you are at it, please also check port 22 (SSH) as well.

Best regards -- Ben


Forum|alt.badge.img+8
  • Author
  • Hero (Partner)
  • 11 replies
  • Answer
  • February 1, 2024

Thanks all for your help. we have identified the issue.

Since we were not using the default port 22 hence we have to update the .Json and .Psm1file..

where we put -Port 22022 instead of -P 22022 on Common.psm1 file ,after fixing this we were able to resolved the issue.

Below is the line which we fixed in common.psm1file

“ ssh -t -i $pvtKeyFilePath  "-p 22022 “

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings