This article covers these possible issues:

  • Server URL issues
  • HTTPS
  • Internet access
  • SSL/TLS Configuration
  • Application configuration

Double Check your Server URL

Sounds obvious but we've mistyped atAlassian and gitub so many times ourselves, we had to add this reminder.

HTTPS

Make sure your server is secure over HTTPS, and not just HTTP. Here's how you can check this: 

  1. Access your tool in a browser and login
  2. Ensure the address bar indicates a secure connection over HTTPS
  3. If not, contact your server administrator to have them secure your server.
     Here's some more info our HTTPS requirements and setup tips.

Internet access

Make sure your server is accessible over the public Internet:

  1. Use any online website testing tool such as https://tools.pingdom.com/ to test access to your server from outside your corporate network. Just enter the full URL you use to access your tool.
  2. If the server is not reachable, contact your server administrator to discuss how it can be exposed to Unito's server.

Here's some more info on connectivity for on-premise servers.

SSL/TLS configuration

Make sure your server SSL/TLS certificate is correctly configured:

  1. Use any online SSL diagnostics tool such as https://www.sslshopper.com/ssl-checker.html to test your configuration. Just enter the full URL you use to access your tool.
  2. If the diagnostics report a problem (often a missing "intermediate certificate"), contact your server administrator with the diagnostics results.

Here's some more info on how to enable SSL/TLS client certificates.

Note: while browsers can be more tolerant of incorrect SSL configurations, Unito's server enforce strict security constraints.

Application configuration

Both GitHub Enterprise and Jira servers require an in-app setup before they can be connected to Unito.

What's next?

If you're still getting errors, please reach out to us for help.
Learn about syncing Jira and GitHub.
Not a Unito user? Try Unito for two weeks free!
Already a user? Sign in here!

Did this answer your question?