Tobi Schäfer

same issue, switching to `target: chrome.app` works. ```json "loki": { "configurations": { "chrome.laptop": { "target": "chrome.docker", "width": 1366, "height": 768, "deviceScaleFactor": 1, "mobile": false }, "chrome.iphone7": { "target": "chrome.docker", "preset":...

+1 This is a problem I just stumbled across, too.

same here using ubuntu 13.04

not for me, unfortunately :grimacing:

``` bash $ which node /usr/bin/node $ cat /etc/opt/chrome/native-messaging-hosts/com.dfilimonov.devtoolsterminal.json { "name": "com.dfilimonov.devtoolsterminal", "description": "Devtools Terminal", "path": "/usr/lib/node_modules/devtools-terminal/bin/nm-host.sh", "type": "stdio", "allowed_origins": [ "chrome-extension://leakmhneaibbdapdoienlkifomjceknl/" ] } ``` i tried it with the...

gnah now i feel stupid 😬

As of today I am still getting the error below as described in this issue with cf1b1b65ebe7ad73832e619f781b34684907b151 and POST: ```plain 2019-05-07T12:54:09.234201954Z events.js:183 2019-05-07T12:54:09.234227129Z throw er; // Unhandled 'error' event 2019-05-07T12:54:09.234232336Z...

_Update:_ Testing the same requests with the Docker container provided via [microbox/node-url-to-pdf-api](https://github.com/microbox/node-url-to-pdf-api) displayed a hint to a potential fix: ``` 2019-05-06T11:06:10.493951843Z (node:1) UnhandledPromiseRejectionWarning: Error: Protocol error (Network.deleteCookies): At least one...

any update on this?

hi @pfrazee thanks for your reply. i could test if it works on a local machine; on the production machine port 443 is already assigned… is there a sound reason...