This is valid HSTS ( HTTP Strict Transport Security ). It obliges to make access to the site through a trusted secure connection, not trusting the decision to the user.
Specifically, google-analytics.com , moreover, is located in the HSTS preload list of Chrome , a kind of “white list” of domains for which HSTS is acting on the initiative of the browser , and not the server.
Having control over your own system, you can generate a self-signed Certificate Authority (CA), install it into the system [1] , and then use it to generate your own certificate for the domain you need (specifying it in the Common Name during generation) and issue it to the web server. Then the browser, applying for validation in the system certificate store, will consider the connection with this server to this domain as trusted.
But keep the generated keys safe, because your system certainly trusts them. If an intruder gets to them, he can make your system believe in almost anything.
- [1] Or use Firefox , which uses its own bundle of certificates, not the system one. In this case, CA is enough to install only in Firefox and the rest of the system will not believe the certificates of this CA. So, probably, calmer.
Chrome always uses system storage . He does not wean.