Vscode-live-server: The Parameter is incorrect

[deanhtid]

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ x] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[ ] Other: <!-- Please describe: -->

Current behavior

When i try to launch the live server i get a pop up box saying http://127.0.0.1:5500/02.html

Expected behavior

I expect the browser to launch with some live reloading

Environment

Browser:

- [x ] Chrome (desktop) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:

- Live Server: 4.1.0
- Platform:  Windows
- Visual Studio Code: 1.24.0

Others

[rjoydip]

Where you getting the pop-up?
Is it inside vscode?

[deanhtid]

Nah it’s seperate from VScode. I would share a screenshot but I don’t have access to my laptop right now

[rjoydip]

That's will be better if you share screenshot

[deanhtid]

I have also tried randomising the port and same issue

[ritwickdey]

Okay, basically same as #120 #65

Set "liveServer.settings.CustomBrowser":"chrome"

[deanhtid]

Now i get this. This is the correct file path

[ritwickdey]

Is chrome installed at this location?

[rjoydip]

Or you can try with other browser as custom browser. To check whether other browser has same error or not

[deanhtid]

Yep installed exactly there. Would rather not give up on using Chrome. Thanks

[deanhtid]

Tried Firefox as a test and exactly the same error

[gijoe50000]

I've been having the same problem now for a week or so on my home machine. No problem on my machine in class. Tried the "chrome" solution above but still the same. Also tried reinstalling VSCode and the extensions.
The Open-In-Browser extension gives the same error, so it doesn't seem to be related to Live Server, and I also get the exact same error in Atoms live server, so I'm not sure if it's a VSCode problem either.

I'm running Windows 10 insider build so maybe it's a problem there?
I'm also running MAMP but uninstalling it didn't help, and I've got MAMP on my class machine and it's fine.

[davimdantas]

I'm having the same problem.
Using VSCode Insider and running windows 10.
This solution didn't work:
Set "liveServer.settings.CustomBrowser":"chrome"
neither change to another browser.

[rjoydip]

I am not sure that whether is this happening by the firewall !

[gijoe50000]

Nope. I tried turning off my firewall, and everything security related I
could find. Didn't make any difference. But it could still very well be
something in the network config. It's a pity the error message isn't even a
little more helpful.

On Thu, 14 Jun 2018 at 18:31, Joydip Roy [e-mail] wrote:

I am not sure that whether is this happening by the firewall !

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ritwickdey/vscode-live-server/issues/152#issuecomment-397376208,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AR147KuH22rmNCr8xEga1EszS_hjnZSZks5t8p4KgaJpZM4UiMf-
.

[ritwickdey]

Just for a confirmation, after getting this error, if you manually open the site (127.0.0.1:5500) ,

Is the server working fine? Or server is also not working!!!

[gijoe50000]

Yea, it works fine after you open the html file manually. I'm using random port numbers so it's not always 5500, but yea.

[gijoe50000]

Tried a lot of things like copying and pasting the address from the addressbar into settings, and localhost instead of 127.. too. I'm thinking it must be a Windows issue, since the error is generated by Windows (I assume) and I've seen people get the same error with server misconfigs too.. It's very vague. Could b some config change that Microsoft have in the pipeline, since I'm using the insiders build. Don't know if other people with the error are insiders too?

[davimdantas]

I don't think it's a windows problem. I have no problem opening the chrome through vscode Task command, works like a charm. I'm using this code:
{ "taskName": "Open in Chrome", "isBuildCommand": true, "command": "Chrome", "windows": { "command": "C:/Program Files (x86)/Google/Chrome/Application/chrome.exe" }, "args": [ "http://localhost:5500/${relativeFile}" ] }

I got this from @RickStrahl's blog

[ritwickdey]

okay, I think, all of you using Windows Insider Version? We are using OPN npm library to open a browser. This saw an issue request on OPN with the same title. https://github.com/sindresorhus/opn/issues/95

[gijoe50000]

Yep, confirmed, thanks.
Live server opens fine in Edge when it's the default browser. Microsoft at their shenanigans again.. :-)
I wonder if it's just an error or a new upcoming feature?.. Or a way of forcing people to use Edge for a while in the hopes they'll adapt to it?

[Nirnturt]

I also encountered the same problem when using Webstorm, and I think the problem is in the windows10 preview system itself, hoping to get more information

[edumazzucco]

Same here :(
Probably is related to the last update of W10 Insider...
I'm using build 17692 btw.

[deanhtid]

Yep i am also running the insiders build. Any updates?

[petercr]

Yes I've got the same issue, and am running Windows 10 Build: 17692.rs_prerelease_flt.180625-1624 myself and I get the same error message when trying to open _Live Server_
Error occurs on both VS Code stable build and Insider's Edition.

However it does work just fine if you open it in the browser
Thanks @ritwickdey your the man!! 👍 🏅 👏 😎

[patroza]

Same here on 17713, only works when Edge is default browser.
Some background https://github.com/sindresorhus/opn/issues/95#issuecomment-393469429

[MCanterel]

Why is this issue considered closed? It's still happening in Insider Preview (build 17692) with all browsers except Edge.

[krnlde]

Build 17723 fixed it for me.

[andymabb]

I get exactly the same error trying to run browser-sync after updating to W10, build17713 (Firefox default browser) which prevents all my NPM & Gulp build processes working automatically.
Rolled back to earlier version (17134) and problem solved.

[MCanterel]

@andymabb You can also upgrade Win10 to 17723. That fixed it for me.