[BUG] Cannot GET / - https://127.0.0.1:3001/ doesn't work + Packer start doesn't watch SCSS changes

[haroldao]

Describe the bug Cannot GET / - https://127.0.0.1:3001/ doesn't work + Packer start doesn't watch changes

To Reproduce Steps to reproduce the behavior:

1. npm install
2. npm run build
3. npm run deploy
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots

System (please complete the following information):

• Windows 10
• Last One
• Last One
• Vivaldi, Firefox Dev Edition

Packer (please complete the following information):

• 

Theme (please complete the following information):

• Shopify Packer theme [e.g. True]
• Version [e.g. 22]

[haroldao]

... So to work... I have to do => Packer Build, packer Deploy to see changes.

[haroldao]

?

[bstarr322]

@haroldao Were you able to fix this issue?

[haroldao]

@haroldao Were you able to fix this issue?

nope

[hayes0724]

@haroldao This looks like an SSL issue.

1. The website/server should load on port 3000
2. The assets (js/css) will load on port 3001 and require SSL working (otherwise you get the above error)
3. Not familiar with Vivaldi, typically though you get a warning icon next to the url lock icon if there is an SSL error (looks like the screenshot above)

Check this section out: Packer SSL docs

Also try the ssl:check or ssl:make command Packer SSL commands

[maks-afew]

@hayes0724 Hi, I have the same issue, and all I've done is just starting the basic project to see if it works. I've followed the docs and saved the cerfiticates, made ssl:make and ssl:check and everything seemed to be correct. But in the browser, when I try to get an asset, it says "Website is not available" instead of loading the assets or at least allow to proceed to the "unsafe" address.

I've noticed that if I type in the browser url "https://localhost:3001/template.index.js" instead of "https://127.0.0.1:3001/template.index.js", then I can get the file