Importing from Fogbugz fails

Summary

We're currently running Gitlab on a local server, and as we're considering moving from Fogbugz to Gitlab, we'd like to import our old projects over. When I use the import tool, I can input my Fogbugz account information, map Fogbugz users to Gitlab users, and view the projects, but every time I try to import a project, it fails with An error occurred while importing project: Error: Request failed with status code 422.

When I check the logs, I found this: response":"{\"errors\":\"Import url is blocked: Host cannot be resolved or invalid\"

Steps to reproduce

  1. Choose new project
  2. Select the Fogbugz importer
  3. Enter fogbugz URL, Username, and Password
  4. Map users as desired
  5. Choose project and select "Import"

What is the current bug behavior?

The import button turns into text that says Failed, and a red banner is displayed that shows An error occurred while importing project: Error: Request failed with status code 422.

What is the expected correct behavior?

Properly importing Fogbugz data.

Relevant logs and/or screenshots

Unable to save project. Error: Import url is blocked: Host cannot be resolved or invalid

Completed 422 Unprocessable Entity in 2317ms (Views: 0.5ms | ActiveRecord: 135.5ms | Elasticsearch: 0.0ms)

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:         Ubuntu 18.04
Proxy:          no
Current User:   git
Using RVM:      no
Ruby Version:   2.6.3p62
Gem Version:    2.7.9
Bundler Version:1.17.3
Rake Version:   12.3.2
Redis Version:  3.2.12
Git Version:    2.21.0
Sidekiq Version:5.2.7
Go Version:     unknown


GitLab information
Version:        12.1.6-ee
Revision:       d05ee0a9c12
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     10.7
URL:            http://projects.tec-usa.local
HTTP Clone URL: http://projects.tec-usa.local/some-group/some-project.git
SSH Clone URL:  git@projects.tec-usa.local:some-group/some-project.git
Elasticsearch:  no
Geo:            no
Using LDAP:     yes
Using Omniauth: yes
Omniauth Providers:


GitLab Shell
Version:        9.3.0
Repository storage paths:
  • default: /mnt/repositories/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check 
Checking GitLab subtasks ...


Checking GitLab Shell ...


GitLab Shell: ... GitLab Shell version >= 9.3.0 ? ... OK (9.3.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK


Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful


Checking GitLab Shell ... Finished


Checking Gitaly ...


Gitaly: ... default ... OK


Checking Gitaly ... Finished


Checking Sidekiq ...


Sidekiq: ... Running? ... yes
Number of Sidekiq processes ... 1


Checking Sidekiq ... Finished


Checking Incoming Email ...


Incoming Email: ... Reply by email is disabled in config/gitlab.yml


Checking Incoming Email ... Finished


Checking LDAP ...


LDAP: ... Server: ldapmain
LDAP authentication... Success
LDAP users with access to your GitLab server (only showing the first 100 results)
User output sanitized. Found 15 users of 100 limit.


Checking LDAP ... Finished


Checking GitLab App ...


Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
2/5 ... yes
7/6 ... yes
8/7 ... yes
8/8 ... yes
7/9 ... yes
7/10 ... yes
7/11 ... yes
7/12 ... yes
7/13 ... yes
7/14 ... yes
7/15 ... yes
7/16 ... yes
7/17 ... yes
7/18 ... yes
7/19 ... yes
7/20 ... yes
7/21 ... yes
7/22 ... yes
7/23 ... yes
7/24 ... yes
7/25 ... yes
2/26 ... yes
10/28 ... yes
9/29 ... yes
9/30 ... yes
9/31 ... yes
9/32 ... yes
9/33 ... yes
9/34 ... yes
9/35 ... yes
9/36 ... yes
9/37 ... yes
9/38 ... yes
9/39 ... yes
9/40 ... yes
9/41 ... yes
9/42 ... yes
9/43 ... yes
9/44 ... yes
9/45 ... yes
12/47 ... yes
9/48 ... yes
9/49 ... yes
9/50 ... yes
9/51 ... yes
9/52 ... yes
9/53 ... yes
9/54 ... yes
9/55 ... yes
9/56 ... yes
9/57 ... yes
9/58 ... yes
9/59 ... yes
9/60 ... yes
13/61 ... yes
13/62 ... yes
13/63 ... yes
13/64 ... yes
13/65 ... yes
13/66 ... yes
13/67 ... yes
13/69 ... yes
13/70 ... yes
13/71 ... yes
13/72 ... yes
9/73 ... yes
12/74 ... yes
12/75 ... yes
16/77 ... yes
16/78 ... yes
16/79 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.6.3)
Git version >= 2.21.0 ? ... yes (2.21.0)
Git user has default SSH configuration? ... yes
Active users: ... 7
Elasticsearch version 5.6 - 6.x? ... skipped (elasticsearch is disabled)


Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)