Unable to Retrieve Connectors in Jama Connect Interchange™ Server Error

Kellen Fields
Kellen Fields
  • Updated

Published Date: May 23, 2025
Validated: Yes
Audience: Everyone
Products and Versions Covered: 

  • Jama Connect Interchange™

Summary

After installing Jama Connect Interchange™, users see a “Server Error (Unable to Retrieve Connectors)” message when attempting to add a connector in the Connector Pane.

This issue typically occurs when the license is not applied correctly or when the JCI host URL is misconfigured — specifically, when the host includes a port or an unnecessary

Resolution

  1. Confirm that the JCI license is applied correctly
    Follow the official documentation to validate the license configuration.

2. Check the JCI host URL configuration

Locate the application.properties file by running:

sudo docker cp config-svc-interchange:/static-files/application.properties .

This copies the configuration file to your current directory.

3. Review the host URL
Open the file and locate the value:

jci.host-url =

If the URL includes a port (for example):

jci.host-url = http://jamaconnectinterchangetest.com:8443

Remove the port so it reflects:

jci.host-url = https://jamaconnectinterchangetest.com/

4. Update the host URL
Run the following command to update it:

sudo docker exec -i config-svc-interchange sh -c "../update_host_url.sh 'https://<hosturl>/'"

5. Verify the fix
Restart the service if needed and confirm the connectors load successfully in the Connector Pane.

Prevention (Optional Best Practice)

  • Ensure the host URL does not include a port unless explicitly required by your deployment.

  • Validate configuration after installation or upgrades to prevent service communication issues.

Cause
The JCI application is bound to port 8443 internally, but Docker routes the default HTTPS port (443) to 8443. Therefore, explicitly defining the port in the host URL is unnecessary and causes connector retrieval failures.

Additional Resources 

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or improvement ideas below.

 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.