Starting with Chrome 50, Chrome no longer supports obtaining the user’s location using the HTML5 Geolocation API from pages delivered by non-secure connections. This means that the page that’s making the Geolocation API call must be served from a secure context such as HTTPS.
Starting in Safari 10.0, unencrypted websites can no longer access Geolocation APIs. You must use a secure connection in order to access Geolocation APIs.
Sites that don’t use SSL can no longer access Geolocation APIs to determine a user’s physical location.
You can fix this by asking your host to install an SSL certificate, or by disabling the “Attempt to auto-locate the user” option on the settings page.
If a mixed error shows up in the browser console, then the error itself often points to the file that causes the problem.
If it’s content you added yourself, then simply replacing http:// with https:// in the content will fix it. If it’s a remote file that triggers the error, then first make sure the external site supports https before replacing http:// with https://