I’m using Sage with Local (by Flywheel) with a self-assigned SSL. I’d prefer testing the site in https.
The devURL loads just fine. https://mysite.local
I assume I set the proxyURL to https like "proxyUrl": "https://localhost:3000"?
My browser warns me then I can proceed, but the proxyURL never loads. It’s like stuck there. I tried in 3 different browsers.
In my CLI, I see:
(node:5737) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
What system is your workstation? Linux; Windows WSL 1/2; OS X?
The nodejs app (BrowserSync) needs network access (and resolution) to the flywheel site (devURL).
The nodejs app (BrowserSync) needs network access (and resolution) to the flywheel site ( devURL )
How do I do that?
Here’s the full return after yarn start:
❯ yarn start
yarn run v1.22.10
$ webpack --hide-modules --watch --config resources/assets/build/webpack.config.js
Webpack is watching the files…
You did not set any plugins, parser, or stringifier. Right now, PostCSS does nothing. Pick plugins for your case on https://www.postcss.parts/ and use them in postcss.config.js.
DONE Compiled successfully in 1771ms 7:29:55 PM
[HTML Injector] Running...
[Browsersync] Proxying: https://sage-gateway.local
[Browsersync] Access URLs:
--------------------------------------
Local: https://localhost:3000
External: https://192.168.1.23:3000
--------------------------------------
UI: http://localhost:3001
UI External: http://localhost:3001
--------------------------------------
[Browsersync] Watching files...
(node:6389) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
I reset the domain within Local. It took forever to provision. Something must have been stuck even though the WP site url and admin url were correct within the admin.
All good now, but is it not possible to run browsersync with https? BTW, there are no references to insecure assets on the page.
Still getting:
(node:9515) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use `node --trace-warnings ...` to show where the warning was created)
Running curl:
❯ curl https://sage-gateway.local
curl: (60) SSL certificate problem: self signed certificate
More details here: https://curl.haxx.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
Looks like it’s coming from wepback.config.watch.js.