We may assume that the problem occurs if you are using an outdated version of Chrome that lacks the necessary security mechanisms to facilitate connection to the CA. Also, some Chrome cookies may be responsible for this behavior when you try to connect to the CA server via HTTPS.