This issue is caused when a user has cookies from other sites blocked in his browser, in case of subcontracting between two XTM instances in different domains this has to be allowed. Please go to chrome://settings/content/cookies?search=cookie and add


entry in the "Allow" section (as on the screenshot):

If the steps above are not sufficient, please try using another browser. If that also yields no positive results, please take a screenshot of the "Console" tab in your browser's Dev Tools (hit F12 when attempting to connect).

In the link below you can find a brief how-to on Dev Tools' usage:


Troubleshooting for XTM Suite admins

If your users do experience "refused connection" errors, then there are a few places you can check if your configuration is correct:

  1. Check if X-Frame-Options is added on your webserver or proxy. If yes, please disable this option.
  2. Check if X-Frame-Options is added as a header to your Nginx:
    curl -v localhost:8080/project-manager-gui/version_number.txt


    curl -v https://test.your_server.com/project-manager-gui/version_number.txt

    where you invoke URL to your XTM instance.
    If your Nginx has the following entry, then this is causing this issue:
     X-Frame-Options: SAMEORIGIN