Salman
-
Posts
7 -
Joined
-
Last visited
Content Type
Profiles
Forums
Enhancement Requests
Posts posted by Salman
-
-
49 minutes ago, Keith Stevenson said:
@Salman
That looks like your local firewall or network firewall (Guess would be Windows firewall) blocking and you only allowed the OLD exe
Kind RegardsThanks Keith.
I could not see anything within Windows Firewall to be blocking.I've also checked with our network team and all the below URLs are whitelisted:
- https://files.hornbill.com/instances/INSTANCENAME/zoneinfo
- https://files.hornbill.co/instances/INSTANCENAME/zoneinfo
- https://eurapi.hornbill.com/INSTANCENAME/xmlmc/
- https://api.github.com/repos/hornbill/goLDAPUserImport/tags
When I rename v3.9.0 to ldap_user_import.exe and run, it imports fine but when I rename v3.12.0 to ldap_user_import.exe, I get the connection error.
Do you know what's changed in v3.12 which will help me look into this further?
Many thanks,
Salman -
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 12022/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 -
Seems to be fixed for us
-
Good morning,
We're seeing the same issue as well. -
Thank you for your response.
Seems like I have to then set a higher expiry value like you did.
Thanks,
Salman
-
Hello,
I'm trying to implement the Star Rating facility for Customer Feedback with no expiry.https://wiki.hornbill.com/index.php?title=Customer_Feedback
I have turned ON Enable Star Rating and set Feedback Expiry to 0.
Customers are not requested with feedback upon call closure.
However, when I set Feedback Expiry to 1 or above, customers get the feedback request.Has anyone seen this or know how to implement Star Rating with no expiry days?
Thanks,
Salman
IMPORTANT - LDAP Data Import Tool - Supported Versions
in Integration Connectors, API & Webhooks
Posted
*** FIXED ***
Morning Keith,
Thank you for your response. Had a further look this morning and it was the proxy settings that was blocking our connections.
I noticed in the change log regarding the change in version 3.9.5:
- Rebuilt using latest version of goApiLib, to fix possible issue with connections via a proxy
Previously we used to point to the http proxy but needed amending to point to the https proxy. Once I did that and used the LDAP Import tool, the imports ran fine.
Thanks again for your advise.
Kind regards,
Salman