vscode-live-server icon indicating copy to clipboard operation
vscode-live-server copied to clipboard

Published 20 hours ago • verified publisher icon ritwickdey

Not Opening In browser when open with live server

Open NIKADI opened this issue 3 years ago • 9 comments

We have written the needed data into your clipboard because it was too large to send. Please paste.

NIKADI avatar Feb 09 '22 14:02 NIKADI

Can you please explain with example?

ritwickdey avatar Feb 11 '22 16:02 ritwickdey

Having the same issue. I'm on Windows 11 running VS Code in a WSL Ubuntu environment. I can right-click on a file like index.html in VS Code's Project Explorer, or click on the Go Live button on the taskbar and Live Server does seem to start, showing Port: 3000 in the VS Code status bar. The issue is it doesn't automatically launch my default browser and I have to manually launch my browser and enter localhost:3000 in the address bar and things are fine from then on.

The question is whether the inability to auto-launch my default browser or create a new browser tab if a browser is already open is due to a Windows 11 system setting, a WSL setting, a VS Code security setting or a Live Server extension setting. I suspect it's a WSL and/or Windows 11 setting because if I run VS Code outside of WSL, Live Server does launch my default web browser but I'm stumped as to how to configure Live Server to work in WSL as it does outside of WSL :/

Seefer avatar Feb 11 '22 17:02 Seefer

Having the same issue. I'm on Windows 11 running VS Code in a WSL Ubuntu environment. I can right-click on a file like index.html in VS Code's Project Explorer, or click on the Go Live button on the taskbar and Live Server does seem to start, showing Port: 3000 in the VS Code status bar. The issue is it doesn't automatically launch my default browser and I have to manually launch my browser and enter localhost:3000 in the address bar and things are fine from then on.

The question is whether the inability to auto-launch my default browser or create a new browser tab if a browser is already open is due to a Windows 11 system setting, a WSL setting, a VS Code security setting or a Live Server extension setting. I suspect it's a WSL and/or Windows 11 setting because if I run VS Code outside of WSL, Live Server does launch my default web browser but I'm stumped as to how to configure Live Server to work in WSL as it does outside of WSL :/

Found a solution for those of you running VS Code in WSL. Add the following to your VS Code settings:

"liveServer.settings.AdvanceCustomBrowserCmdLine": "/mnt/c/Program Files (x86)/Google/Chrome/Application/chrome.exe"

This informs Live Server where to find the Windows native executable for the browser you wish to auto-launch. /mnt/c is how you tell WSL to navigate to your Windows file system rather than looking inside the Linux file system.

Seefer avatar Feb 11 '22 17:02 Seefer

I'm having the same issue. I'm on Ubuntu 21.10 and tried with Firefox, Chrome and Brave browsers.

lnabesima avatar Feb 12 '22 20:02 lnabesima

Problem solved

On Sun, Feb 13, 2022, 1:33 AM Lucas Nabesima @.***> wrote:

I'm having the same issue. I'm on Ubuntu 21.10 and tried with Firefox, Chrome and Brave browsers.

— Reply to this email directly, view it on GitHub https://github.com/ritwickdey/vscode-live-server/issues/2346#issuecomment-1037437440, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIF2CUC7Q5KLSN5LQX3HBJLU224JNANCNFSM5N5UBJ7A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

NIKADI avatar Feb 12 '22 20:02 NIKADI

Problem solved path problem clear

On Sun, Feb 13, 2022, 2:15 AM NIKADI THIRUPATHI @.***> wrote:

Problem solved

On Sun, Feb 13, 2022, 1:33 AM Lucas Nabesima @.***> wrote:

I'm having the same issue. I'm on Ubuntu 21.10 and tried with Firefox, Chrome and Brave browsers.

— Reply to this email directly, view it on GitHub https://github.com/ritwickdey/vscode-live-server/issues/2346#issuecomment-1037437440, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIF2CUC7Q5KLSN5LQX3HBJLU224JNANCNFSM5N5UBJ7A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

NIKADI avatar Feb 12 '22 20:02 NIKADI

I did a full reinstall of VSCode and Live Server, and it worked. Problem solved.

lnabesima avatar Feb 13 '22 19:02 lnabesima

Having the same issue. I'm on Windows 11 running VS Code in a WSL Ubuntu environment. I can right-click on a file like index.html in VS Code's Project Explorer, or click on the Go Live button on the taskbar and Live Server does seem to start, showing Port: 3000 in the VS Code status bar. The issue is it doesn't automatically launch my default browser and I have to manually launch my browser and enter localhost:3000 in the address bar and things are fine from then on. The question is whether the inability to auto-launch my default browser or create a new browser tab if a browser is already open is due to a Windows 11 system setting, a WSL setting, a VS Code security setting or a Live Server extension setting. I suspect it's a WSL and/or Windows 11 setting because if I run VS Code outside of WSL, Live Server does launch my default web browser but I'm stumped as to how to configure Live Server to work in WSL as it does outside of WSL :/

Found a solution for those of you running VS Code in WSL. Add the following to your VS Code settings:

"liveServer.settings.AdvanceCustomBrowserCmdLine": "/mnt/c/Program Files (x86)/Google/Chrome/Application/chrome.exe"

This informs Live Server where to find the Windows native executable for the browser you wish to auto-launch. /mnt/c is how you tell WSL to navigate to your Windows file system rather than looking inside the Linux file system.

I am also facing the same issue but I'm not running VSCode in a WSL Ubuntu environment. what changes should be made to this settings if needed?

nurize avatar Nov 24 '23 12:11 nurize

Linux Mint 21.3 (based on Ubuntu 22.04.3) Having switched my browser for the Live Server extension, from Firefox to Chrome, the extension now only shows the port, so I have to manually navigate to http://localhost:5500.

UPDATE: I managed to fix this by uninstalling the Ftalhub version and installing the debian package from Google.

avalon60 avatar Apr 30 '24 10:04 avalon60