[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Error: connect ECONNREFUSED 127.0.0.1:xxxxx #65

Open
0rangebananaspy opened this issue Jul 1, 2023 · 4 comments
Open

Error: connect ECONNREFUSED 127.0.0.1:xxxxx #65

0rangebananaspy opened this issue Jul 1, 2023 · 4 comments

Comments

@0rangebananaspy
Copy link

I'm running on my local virtual server on Proxmox with Ubuntu 22.04 LTS, Node.js v18.16.1. Everytime npm run test-pages give me this error.

> speedlify@1.0.0 test-pages
> node run-tests

There are no known last run timestamps
Skipping fakultas (you told me to in your site config)
First tests for sample.
Testing 6 sites:
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

Error: connect ECONNREFUSED 127.0.0.1:41941
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 41941
}

Node.js v18.16.1

any clue to make it run?

Screenshot: https://imgur.com/bIZDTte
@colinmo
Copy link
colinmo commented Dec 1, 2023 •
edited
Loading

You'll have to add chromium/chrome browser to your repository. The tool puppets Chrome in order to run the user-experience browser.

ADDED: Note that if you're running as Root, you'll also need to add --no-sandbox to the options in the run-tests.js file.

@fienen
Copy link
fienen commented Dec 2, 2023

You'll have to add chromium/chrome browser to your repository. The tool puppets Chrome in order to run the user-experience browser.

ADDED: Note that if you're running as Root, you'll also need to add --no-sandbox to the options in the run-tests.js file.

@colinmo Can you go into a bit more detail on this? I've got Chrome and Chromium both installed on the server, but I'm also getting this same error. When you say "add it to the repo," is that implying something like NPM should be installing it there, because that doesn't seem totally right.

@colinmo
Copy link
colinmo commented Dec 4, 2023

Sorry for delay.

I found that I had to add chromium/ chrome (either) AND set the environment variable "PUPPETEER_EXECUTABLE_PATH" that tells puppeteer where to run - /usr/bin/chromium-browser in my case. Does that help?

@colinmo
Copy link
colinmo commented Dec 11, 2023

@colinmo Can you go into a bit more detail on this? I've got Chrome and Chromium both installed on the server, but I'm also getting this same error. When you say "add it to the repo," is that implying something like NPM should be installing it there, because that doesn't seem totally right.

Sorry, in addition to the above answer you don't need to add it to the actual repo. You're right, it's just it needed to be installed where your code can access it. Much more accurate description.

@Akashic101 Akashic101 mentioned this issue May 4, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fienen @colinmo @0rangebananaspy