search

tabeyti / jenkins-jack

Jack into your Jenkins to execute Pipeline scripts, provide Pipeline step autocompletions, pull Shared Library step documenation, run console groovy scripts across multiple nodes, and more! Honestly, not that much more.
Other
97 stars 32 forks source link

"Jenkins Jack: Could not connect to the remote Jenkins" #5

Closed ishepherd closed 4 years ago

ishepherd commented 5 years ago

How do I troubleshoot "Could not connect"?

  1. Jenkins-jack > Jenkins: Uri = https://myhost

Developer tools console:

Using the following URI for Jenkins client: http://myusername:mytoken@https://myhost

Seems it doesn't support URIs in the Uri setting

  1. Jenkins-jack > Jenkins: Uri = myhost

Developer tools console:

Using the following URI for Jenkins client: http://myusername:mytoken@myhost

Still the same notification "Could not connect to the remote Jenkins"

When I try that URI in a web browser, the company Jenkins server sends back a 307 redirect to the https:// version. Maybe the extension doesn't like the redirect?

tabeyti commented 4 years ago

Latest version 0.1.4 now supports better parsing for URIs and should fix this issue.

There is also a setting to disable strict TLS for endpoints without valid certs.

kamalbaldawa commented 1 year ago

I am also facing the above issue

rror running command extension. Jenkins-jack.tree.connections.refresh: Cannot read properties of undefined (reading 'connection'). This is likely caused by the extension that contributes extension.jenkins-jack.tree.connections.refresh.