# Node-red-contrib-web-page-screenshot "Your connection is not private" Error

**URL:** <https://discourse.nodered.org/t/node-red-contrib-web-page-screenshot-your-connection-is-not-private-error/27512>\
**Category:** General\
**Created:** [29 May 2020 20:58 UTC](https://discourse.nodered.org/t/node-red-contrib-web-page-screenshot-your-connection-is-not-private-error/27512 "2020-05-29T20:58:52Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mgarito](https://avatars.discourse-cdn.com/v4/letter/m/a88e57/32.png) [@mgarito](https://discourse.nodered.org/u/mgarito)\
**Post date:** [29 May 2020 20:58 UTC](https://discourse.nodered.org/t/node-red-contrib-web-page-screenshot-your-connection-is-not-private-error/27512/1 "2020-05-29T20:58:52Z")

</div>

The tool "node-red-contrib-web-page-screenshot" has worked on every webpage I have tried it on, except the ones that throw a "Your connection is not private" certificate error.

I've tested http, https, http with atypical ports, https with atypical ports... all fine.. unless there is a cert error..

Directly from command line to a local machine that doesn't have a signed cert...  
/usr/bin/chromium-browser --disable-gpu --headless --window-size=1920,1080 --ignore-certificate-errors --screenshot=/tmp/image2.png [https://10.128.128.14/](https://10.128.128.14/)

I receive the following error:  
[0529/205143.150969:ERROR:cert\_verify\_proc\_nss.cc(998)] CERT\_PKIXVerifyCert for 10.128.128.14 failed err=-8179

A file is still created, but it is just the site's background image and nothing else...  
[0529/205143.409172:INFO:headless\_shell.cc(619)] Written to file /tmp/image2.png.

The questions are:

1. Any idea on how to bypass the "Your connection is not private" click to proceed error via the command line. With this I can work round the issue in the near term...

2. Can the fix to the previous question be incorporated into this screenshot node?

As I said it works on most everything I've tested so its pretty solid, minus this certification issue.

Thanks!  
MGarito

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [30 May 2020 05:21 UTC](https://discourse.nodered.org/t/node-red-contrib-web-page-screenshot-your-connection-is-not-private-error/27512/2 "2020-05-30T05:21:37Z")

</div>

I read that there is an option (version dependent):

```auto
--allow-insecure-localhost 

```

---

<div class="post-metadata">

**Author:** ![ristomatti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ristomatti/32/5857_2.png) [@ristomatti](https://discourse.nodered.org/u/ristomatti)\
**Post date:** [30 May 2020 07:15 UTC](https://discourse.nodered.org/t/node-red-contrib-web-page-screenshot-your-connection-is-not-private-error/27512/3 "2020-05-30T07:15:01Z")

</div>

This would only help if the web server was running on the same system.

---

<div class="post-metadata">

**Author:** ![ristomatti](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ristomatti/32/5857_2.png) [@ristomatti](https://discourse.nodered.org/u/ristomatti)\
**Post date:** [30 May 2020 07:18 UTC](https://discourse.nodered.org/t/node-red-contrib-web-page-screenshot-your-connection-is-not-private-error/27512/4 "2020-05-30T07:18:55Z")

</div>

@mgarito As it's a local machine, would it be out of the question to configure it to use plain http (only for local connections if it's also accessed externally)?

---

<div class="post-metadata">

**Author:** ![mgarito](https://avatars.discourse-cdn.com/v4/letter/m/a88e57/32.png) [@mgarito](https://discourse.nodered.org/u/mgarito)\
**Post date:** [1 June 2020 13:19 UTC](https://discourse.nodered.org/t/node-red-contrib-web-page-screenshot-your-connection-is-not-private-error/27512/5 "2020-06-01T13:19:33Z")

</div>

Hi @ristomatti ,

- Node-Red is running on an Ubuntu Server I manage.
- The server I'm trying to generate a screenshot from is a Windows Server I also manage.
- The services running on the Windows Server are mission critical so our security policy prevents me from running open-sourced tools local on the windows server.

The goal is to display the screenshots on a remote smart display in a sudo-public setting. Thus the topology is: Smart Display: request page \<-\> Node-Red: convert to screenshot \<-\> Windows Server

Unfortunately, allowing direct access between the smart display and the Windows server creates a security vulnerability, so this is the best work around I've been able to come up with so far. And I said it works for all sites that don't have the "Your connection is not private" certificate error.

Thanks!  
MGarito

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [31 July 2020 13:19 UTC](https://discourse.nodered.org/t/node-red-contrib-web-page-screenshot-your-connection-is-not-private-error/27512/6 "2020-07-31T13:19:52Z")

</div>

Closed on 31 July 2020 13:19 UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.