This article covers these possible issues:
- Server URL issues
- 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.
Make sure your server is secure over HTTPS, and not just HTTP. Here's how you can check this:
- Access your tool in a browser and login
- Ensure the address bar indicates a secure connection over HTTPS
- If not, contact your server administrator to have them secure your server.
Here's some more info our HTTPS requirements and setup tips.
Make sure your server is accessible over the public Internet:
- 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.
- If the server is not reachable, contact your server administrator to discuss how it can be exposed to Unito's server.
Make sure your server SSL/TLS certificate is correctly configured:
- 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.
- If the diagnostics report a problem (often a missing "intermediate certificate"), contact your server administrator with the diagnostics results.
Note: while browsers can be more tolerant of incorrect SSL configurations, Unito's server enforce strict security constraints.
Both GitHub Enterprise and Jira servers require an in-app setup before they can be connected to Unito.