Jira Issue Updater插件配置遇连接拒绝错误，求技术支持

I’ve seen this exact issue pop up a few times in Jenkins-Jira integration setups, so let’s walk through the most common fixes to get your connection working.

• First, verify basic network connectivity between Jenkins and Jira servers
  Log into your Jenkins server (via SSH if it’s a remote instance) and run a simple test like ping <your-jira-domain> or curl -v <your-jira-rest-url> (e.g., curl -v https://your-jira-instance/rest/api/2/issue). If this fails, the problem is at the network level—either the servers can’t reach each other, or there’s a firewall blocking traffic.

• Double-check your Jira URL configuration in the plugin
  Make sure the URL you entered in the Jira Issue Updater build step is correct. Common mistakes include:

  • Missing the protocol (http:// or https://)
  • Typing the wrong domain/IP
  • Using an internal port that’s not accessible from Jenkins (e.g., if Jira is running on port 8080 internally but exposed via a reverse proxy on 443)
    Also, confirm that the REST endpoint is enabled—Jira’s REST API is usually at /rest/api/2/, so your base URL should end with that or the plugin will fail to hit the right endpoint.

• Check for firewall or proxy restrictions
  If Jenkins is behind a corporate proxy, you’ll need to configure Jenkins to use that proxy for outbound requests to Jira. Go to Manage Jenkins > Manage Plugins > Advanced and set up the proxy settings there. Also, ensure that the firewall between Jenkins and Jira allows traffic on the port you’re using (80 for HTTP, 443 for HTTPS, or your custom port).

• Verify Jira’s service status and REST API accessibility
  Make sure your Jira instance is up and running—try accessing the Jira UI directly from a browser using the same URL you entered in Jenkins. If the UI works but the REST API doesn’t, check Jira’s logs for any errors related to the REST service. You can also test the REST endpoint from a machine that can reach Jira to confirm it’s responding.

• Check plugin compatibility and credentials
  Even though the error says "connection refused", sometimes outdated plugins can cause unexpected issues. Ensure you’re using the latest version of the Jira Issue Updater plugin. Also, double-check that the credentials (username/api token) you’re using have permission to access the Jira REST API—though this usually throws an authentication error, not connection refused, it’s worth ruling out.

As for getting support on Stack Overflow, absolutely—this is a common enough issue that you’ll find plenty of existing threads. When searching, use keywords like Jenkins Jira Issue Updater Connection refused, Jenkins unable to connect to Jira REST service, or java.net.ConnectException Jenkins Jira. If you don’t find a solution that fits, you can post a new question with:

• The full error log you shared
• Screenshots of your plugin configuration (redact any sensitive info like credentials)
• The results of your network connectivity tests (ping/curl output)
• Details about your Jenkins and Jira environments (versions, server setup, network topology)

内容的提问来源于stack exchange，提问作者Rohan K