You need to make sure your site is loading assets over the same protocol as the initial request (i.e. HTTPS). Those errors are complaining because your site is trying to make HTTP requests while the site is loaded over HTTPS (see in your address bar, https://localhost)
No. The HTML must either use // or https:// as the scheme (the former will make the browser make the requests with the same scheme as the originating page). The browser is preventing the request from even happening, because the HTML contents are trying to load insecure content.