# Bug JIM-171 - Imprecise error for invalid address of Jira Server/Data Center URL when testing Jira connection

Project: Stream Jira to OpenProject data Migrator
Status: rejected
URL: https://community.openproject.org/work_packages/JIM-171

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module |  |
| Target versions | 17.8.0 |
| Observed in versions | 17.7.0 |
| Sprint |  |
| Backlog bucket |  |
| Bug found in version (deprecated) | 17.7.x |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

### Steps to reproduce

1.  Have a Jira DC installed on a private IP address, and have a DNS name pointing to that IP address;
    

*   IP addresses (as seen from DNS on the server) where added to OPENPROJECT\_SSRF\_\_PROTECTION\_\_IP\_\_ALLOWLIST
    
*   tested with one Jira DC instance only accessible in VPN and one Jira DC that is publicly accessible
    

1.  Go to the Jira migrator and add a configuration
    
2.  Add the URL and token - URL was tried with or without trailing "/"
    
3.  Click "Test configuration"
    

### What is the buggy behavior?

*   Cryptic error message "An unexpected error occurred while testing the connection: invalid address" is displayed
    
*   Logs do not give you more of a clue: "Unexpected error testing Jira configuration: IPAddr::InvalidAddressError - invalid address:" - that's it
    

### What is the expected behavior?

1.  The application should give a more helpful error message disclosing what was wrong
    
2.  The log entries should provide information that allows the admin to actually figure out what _could_ be going wrong
    
3.  Improvement: Display a checklist, detailing which steps are undertaken in the connection test and which were successful IOT facilitate to determine where it failed
    

*   Bonus: Documentation for SSRF protection exists in /installation-and-operations/jira-migration/README.md should be added to the and the Jira migrator documentation
    

### **Logs**

*   no errors in the browser console (
    
    *   though seemingly unrelated "secure.gravatar.com/avatar/9d6395e4531ace90021df7a670bde8ae?default=404&secure=true:1 Failed to load resource: the server responded with a status of 404 ()" was spotted
        
*   OP logs can be provided - but as mentioned they were not very telling
    

### Screenshots and other files

*   Screenshot of error will be attached
    

### Environment information

**OpenProject installation type**

*   Packaged installation on Ubuntu 22.04 LTS
    

**OpenProject version**

OpenProject 17.7.1

**Browser**

*   [x] Chrome
*   [x] Firefox
*   [ ] Safari
*   [ ] Mobile Safari
*   [ ] Other (please specify)

**Operating System**

*   [ ] Windows
*   [ ] Mac OS X
*   [ ] Mobile iOS
*   [ ] Mobile Android
*   [x] Linux (Ubuntu 22.04 LTS)
*   [ ] Chrome OS
*   [ ] Other (please specify)

**Language**

English and German