Skip to main content

6 - Open in a new browser instance

For the purposes of local installation, you need to open the HCMS Client in a separate browser instance, with lowered security settings. The squid proxy can be configured in any browser and many other clients. For Google Chrome, the most convenient way is to start a new instance with the proxy passed via commandline option --proxy=<hostOrIP>:2138

  • Mac OS X (the data-dir directory is just an example):

    CODE
    open -n -a Google\ Chrome --args --proxy-server=localhost:3128 --disable-web-security --allow-running-insecure-content --user-data-dir=/tmp/chromeDev
    
  • Windows:

    CODE
    [PATH_TO_CHROME]\chrome.exe"  --proxy-server=localhost:3128 --disable-web-security --allow-running-insecure-content  --user-data-dir=~/chromeTemp
    

Then the portal domain can be opened (https://<domain>). This is the same domain you specified while preparing your Docker host

Please note that the self-signed certificate is not accepted and the security error must be overridden by typing special secret keyword: thisisunsafe (note that lack of spaces). When you open the portal domain and land on the warning page, just click somewhere on the white area on that page and then type the secret keyword.

If this does not help, you can quit the browser and re-open it using the following command. The additional --ignore-certificate-errorsmust solve the problem.

CODE
```bash
open -n -a Google\ Chrome --args --proxy-server=localhost:3128 --disable-web-security --allow-running-insecure-content --user-data-dir=/tmp/chromeDev --ignore-certificate-errors
```

Additionally, this can be worked around by importing the certificate (exact procedure depends on the OS) or completely solved by having a proper CA-signed certificate.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.