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.

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

[Bug]: chrome version win64-127.0.6533.88 doesn't work with localhost #13527

Closed
UchihaYuki opened this issue Jan 20, 2025 · 1 comment
Closed
Labels

Comments

@UchihaYuki
Copy link

Minimal, reproducible example

I opened the `chrome.exe` downloaded by `puppeteer` package in directory `C:\Users\xxx\.cache\puppeteer\chrome\win64-127.0.6533.88\chrome-win64` manually, and entered `http://localhost:3000/test`, it didn't work. But it works for version `win64-126.0.6478.182`.

Background

No response

Expectation

I hope it can work with localhost.

Reality

It can't open the page under localhost.

Puppeteer configuration file (if used)

Puppeteer version

22.15.0

Node version

20.14.0

Package manager

npm

Package manager version

10.7.0

Operating system

Windows

@UchihaYuki UchihaYuki added the bug label Jan 20, 2025
@OrKoN
Copy link
Collaborator

OrKoN commented Jan 21, 2025

Could you please provide a complete minimal reproducible example? By default, Chrome does not start any servers on localhost:3000 so I do not expect anything to be there. If you run some other app, make sure it is really accessible on that port and localhost resolves to the IP address that the app actually listens on.

Generally, not reproducible: started a server with python3 -m http.server 3000, able to open it in Chrome launched by Puppeteer.

@OrKoN OrKoN closed this as not planned Won't fix, can't repro, duplicate, stale Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants