Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Unveils New Agentic Capabilities Across Analytics, Data Engineering, and Trust: Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
Jeff_Robbins_ORI
Partner - Contributor II
Partner - Contributor II

Salesforce Connection from Qlik Data Integration - "site can't be reached"

Could anyone please provide any guidance on creating a Salesforce connection in QDI?

  1. I have used the instructions on Qlik Help to set up a Connected App on Salesforce with a callback URL, Consumer Key and Consumer Secret.
  2. In  Qlik Data Integration, I am attempting to create a connection to that Connected App using that Key and Secret. However, when I click “authenticate” in QDI, the pop-up window in Salesforce shows “this site can’t be reached.

Thanks,

Jeff

JR_ORI_2-1771382317288.png

 

1 Solution

Accepted Solutions
Hein_Schultz
Partner - Contributor II
Partner - Contributor II

OK! I was able to figure it out. What you need is:

 

Data Gateway: Your Gateway

Salesforce Instance: orgfarm-**e*cab***-dev-ed.develop.my  (get it from your login URL)

Client Id & Secret: from the created salesforce API 

Login Domain: login.salesforce.com

 

Then do the Authenticate, Copy & Paste the code, and then Validate successfully 🙂

View solution in original post

6 Replies
Debbie219Adams
Contributor
Contributor

Hello!  greenskyonline com

That error usually means the callback URL or domain doesn’t match between Salesforce and Qlik. Make sure the callback URL in your Salesforce Connected App is identical to what Qlik expects (including https and slashes), and use your org’s My Domain URL instead of the generic login.salesforce.com. Also confirm the Consumer Key/Secret are copied exactly and that your QDI environment can reach Salesforce endpoints. In most cases, fixing the callback URL or switching to the correct Salesforce domain resolves the “site can’t be reached” issue. 

Jeff_Robbins_ORI
Partner - Contributor II
Partner - Contributor II
Author

as an update: 

I have gotten one step farther, but am still blocked. If you could please provide any further guidance, I’d be much obliged!

suggestion> If you're using a dev account, you need to use the dev tenant Login Domain (URL when logged into Salesforce). 

So, today I re-built everything, from the ground up, making sure to get everything exact: I have specified

  1. the correct Salesforce Instance:                  CAN98
  2. the correct Login Domain:                            orgfarm-4e2a373d1b-dev-ed.develop.my.salesforce.com

 

Today, the Authenticate button succeeded (where it was previously failing), and the authentication code  was generated: code=aP…=&state=…&version=3

 

However, upon clicking Verify, the following error is generated:

  1. Please edit source, provide correct instance then reload this dataset. Please note all steps in this document to find correct instance https://help.salesforce.com/s/articleView?id=000384755&type=1 Please note you may be using Salesforce "My Domain" or Salesforce "Edge" which changes the relevant instructions. Your instance name may be "companyname.my".
  2. Error code: DATA-APP-DESIGN-FAILED-TO-CREATE-EXTERNAL-DATA-PROVIDER-CONNECTION-ERROR
    Trace ID: 00-f60...-01
 
 

QDI SalesForce Connection newer redacted.png

Hein_Schultz
Partner - Contributor II
Partner - Contributor II

I have the exact same issue. I can Authenticate and get a code, but Verify gives that issue. Also on a DEV Salesforce account

Hein_Schultz
Partner - Contributor II
Partner - Contributor II

OK! I was able to figure it out. What you need is:

 

Data Gateway: Your Gateway

Salesforce Instance: orgfarm-**e*cab***-dev-ed.develop.my  (get it from your login URL)

Client Id & Secret: from the created salesforce API 

Login Domain: login.salesforce.com

 

Then do the Authenticate, Copy & Paste the code, and then Validate successfully 🙂

JeffPieCart
Contributor II
Contributor II

Thanks Hein! Your solution worked! Did you find this solution by trial-and-error, or is there some documentation or other resource from which you obtained the solution? Is so, could you please share that documentation?  To provide a visual for everyone, here is a screenshot comparing working and non-working configurations: 

SAlesforce auth solution.png

Hein_Schultz
Partner - Contributor II
Partner - Contributor II

Hello. I'm glad the solution worked for you 🙂

It was trial and error. I tried working with Copilot, but even there I wasn't able to get the exact solution.