-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Critical and self-signed certificates #171
Comments
I found this in
But putting this
Reference: admc/wd#358 |
Here's the error I'm seeing (not sure if it's the same as you):
This is actually an error from request. A quick and dirty hack is to replace line
The |
I didn't see any errors output at all. What I did for a temporary fix is to allow the website to run both http and https in local dev. I'd ideally like to be able to pass params down to Penthouse/PhantomJS via Critical. I can see it being useful for this, as well as other issues. |
I managed to fix this by putting this at the top of my javascript. process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0" |
Thanks for reporting and sorry for the late response. We'll adding a fix for this in the next release. |
v1.0.0 Released. |
First, many thanks for critical -- I've been using it for years, and love it.
I've run into an issue recently where I have SSL enabled on local dev, which is also where I build the critical css using
gulp
andcritical
. It took me a bit to figure out what was going on, because I'd runcritical
and no output at all would appear (no errors, no critical css written out).It turns out that because the https certificate is self-signed, it's failing to render the page in PhantomJS. I google'd a bit, and found that something such as this needs to be added:
But is there a way to pass this down to phantomjs via critical?
The text was updated successfully, but these errors were encountered: