rancher.zendesk.com refused to connect error

Follow
Table of Contents

Issue

"rancher.zendesk.com refused to connect." error when attempting to sign in to the Rancher Customer Support portal

zendesk-refused-to-connect.png

Root Cause

Third-party cookies are blocked in your browser settings.

Resolution

To fix this problem, third-party cookies will need to be enabled in your browser settings.

As a user, when you click on "SIGN IN", you will see the following message in the Sign in dialog box:

click-here-to-restart.png

Click on the link that says, "Click here to restart your sign in."

If this action does not address the problem, then the browser setting will need to be modified manually.

In Google Chrome

  1. Go to the Preferences menu under Chrome
  2. Click on Privacy & Security
  3. Click on Cookies and site data
  4. Toggle the option Block third-party cookies off

block_third-party_cookies-google-chrome-1-of-3.png

block_third-party_cookies-google-chrome-2-of-3.png

block_third-party_cookies-google-chrome-3-of-3.png

In Mozilla Firefox

  1. Go to the Preferences menu under Firefox
  2. Click on Privacy & Security
  3. Under the Enhanced Tracking Protection section, check if it is set to Custom
  4. If yes, check if "All third-party cookies (may cause websites to break)" is the selected value in the dropdown next to the Cookies checkbox.
  5. If yes, change it to "Cross-site and social media trackers".
  6. Click on the Reload All Tabs button

block_third-party_cookies-mozilla-firefox.png

In Microsoft Edge

  1. Go to the Preferences menu under Microsoft Edge
  2. Click on Site Permissions
  3. Go to Cookies and site data
  4. Toggle the option Block third-party cookies off

block_third-party_cookies-msft-edge.png

In Apple Safari

Per this Zendesk article, below is the suggested resolution:

The latest version of the Apple Safari browser, Safari 13.1, fully blocks third-party cookies. If you are using a host-mapped domain for your Help Center, agents and end users cannot sign on with a Safari 13.1 browser. The only workarounds are to use incognito mode or try another browser.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.