Live server not working with Chrome


#1

since I have windows 10 Pro insider preview evaluation copy.build 17692.rs_prerelease_flt. 180625-1624
Does Atom no longer work with Chrome. I get an error http://127.0.0.1:3000 The parameter is incorrect [OK]
That’s all.


#2

Atom has no bearing on this issue, since Atom has no live server capabilities. The atom-live-server package does not care what browser you use.

I get an error

Mind posting a screenshot of it?


#3

Atom-error
The server is running, what and where, I do not know.
003-Server%20is%20running

Update:
It works in Microsoft Edge. But in Internet Explorer, it does not work.
I do not have more browsers.

This problem has been resolved for the time being. Because I’m back to a previous version of Windows 10 Pro. (1803 Build: 17134.112). Otherwise I can not continue with my website :wink:


#4

That’s strange. A server running on your computer should work with every browser.


#5

Maybe Microsoft wants to make us so clear that we now have to switch to the browser Edge?


#6

I think that’s a bit dramatic and unlikely. Regardless, I agree with them. Anyone who was still using IE should switch to Edge at the very least, even though Chrome, Firefox, and Brave are better.


#7

Was only a joke. :wink:
But, I do not shoot much with your answers.
I still can not continue with Atom


#8

You could use an alternative like browsersync. It requires command-line instructions, but those can be automated with process-palette.


#9

It has always worked with Google Chrome.
Why now suddenly no longer? Can you explain that?
I really do not start with command-line instructions. it must remain workable and fast!


#10

I don’t thnk anyone except you knows what happened on your computer to make it stop working.

What’s faster than a keyboard shortcut?


#11

The only thing that happened is that I now have a new Windows version and
you know what in a few weeks you have this version too. Just think about it.
So if nothing changes you are with exactly the same problem as I have now!


#12

Me? I don’t use Windows. Nor do I see a problem with Atom, or use the atom-live-server package (or any kind of live server). To confirm it’s a problem with Atom itself, you would need to replicate the issue in safe mode (which disables all community packages and your init script).

It looks like the atom-live-server package is having issues though, so you might want to notify the people who wrote it by making an issue on it’s repository.