Connection is not secure

[e-dolan]

Thanks for building this theme, it's been great so far but I am working in the dark as the workflow is new to me and the documentation is quite patchy/light so apologies for asking the obvious.

I've pointed the site to a domain and the site no longer loads. I get the below error message in Chrome:

'Your connection is not private
Attackers might be trying to steal your information from sitename.co.uk (for example, passwords, messages or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID'

I also have the below console error when previewing via Shopify:

'slater - connection to server at 4000 failed'

I can't see in the docs how I set this up properly or indeed what I should be reasearching here. I don't want to use the livereloading or localhost (as I'm sure this is the issue) but just want this to load properly on a live domain. Any advice on how to fix these issues would be great.

[zacksmash]

Bump ^^

[seandogg]

I see this message anytime I've been developing and stop/kill slater watch, I believe you could run a slater build or npm run deploy:development if you're not running slater and that would work in these cases?

[iamkevingreen]

@untetheredcollective sounds like you're not building the site? You should only see the connect isn't private in development mode, which needs to be the case to enable live reloading in dev. You should have a development theme and a production them in your Shopify experience. Your production theme should always be the build version of the site and not what slater watch is pushing up.

Additionally while running Dev you need to accept the ssl cert on 4000 in order to enable live reloading.