Updating the LDAP Import Tool to v3.12.0, I'm getting the below error when running it (I've just marked out the InstanceID and APIKey):
2022/02/22 13:46:45 [MESSAGE] ---- LDAP Import Utility v3.12.0 ----
2022/02/22 13:46:45 [MESSAGE] Flag - config ldap-import
2022/02/22 13:46:45 [MESSAGE] Flag - logprefix
2022/02/22 13:46:45 [MESSAGE] Flag - dryrun false
2022/02/22 13:46:45 [MESSAGE] Flag - instanceid ****************
2022/02/22 13:46:45 [MESSAGE] Flag - apikey ****************
2022/02/22 13:46:45 [MESSAGE] Flag - apitimeout 60
2022/02/22 13:46:45 [MESSAGE] Flag - workers 1
2022/02/22 13:46:45 [MESSAGE] Flag - forcerun false
2022/02/22 13:47:06 [ERROR] Unable to check utility version against Github repository: Get "https://api.github.com/repos/hornbill/goLDAPUserImport/tags": dial tcp 140.82.121.6:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2022/02/22 13:47:06 [MESSAGE] Loading Configuration Data: ldap-import
2022/02/22 13:47:27 Error Loading Zone Info File: Get "https://files.hornbill.com/instances/miltonkeynescouncil/zoneinfo": dial tcp 78.129.173.124:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2022/02/22 13:47:48 Error Loading Zone Info File: Get "https://files.hornbill.co/instances/miltonkeynescouncil/zoneinfo": dial tcp 83.126.54.45:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2022/02/22 13:47:48 [ERROR] 107: Unable to read your instance information from Hornbill. Check your connectivity to Hornbill and/or command line proxy access: Get "https://files.hornbill.co/instances/miltonkeynescouncil/zoneinfo": dial tcp 83.126.54.45:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
---------------
Replacing back to our previous version 3.9.0 runs the import successfully.
Am I missing something?
Thanks,
Salman