-
Notifications
You must be signed in to change notification settings - Fork 147
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
"Could not connect to LiveReload server." #110
Comments
Weird because there's |
@thibaudgg Yeah, I use the Web Store version (2.0.9), is this really the last version ? https://chrome.google.com/webstore/detail/livereload/jnihajbhpnppcggbcgedagnkighmdlei |
Hmm, what the url of your assets in your browser? Because with |
The assets got link without http at the beginning (things like "/images/image.png"). If you wanna try on my projet, you can clone http://github.com/eramdam/LBSRF and try for yourself, as I'm a complete noob in Ruby/Guard 😁 |
Sadly I haven't much time this week, maybe you could try to ask on support@livereload.com, thanks! |
Don't worry, I can wait ;) |
Any solution to this issue? |
@alexpchin no idea, please try to contact support@livereload.com. |
For others with this problem try changing the host to '127.0.0.1' I also had to upgrade to the most recent version or there would be an error when it actually tried to connect. |
@tristil That did the trick for me—thanks so much for the tip! |
While testing out Grunt operations, livereload servers were started and (assumedly) stopped consecutively 5 of 6 times - Then this issue started happening. I tried all the posted solutions to resolve and even saw them still running as node commands using: |
Same thing is happening for me. I also see an error in the console:
This started happening after I tried out a Node project that uses tiny-lr to watch for changes in the file system. After using that, Node processes are able to watch for changes but Ruby processes are not able to anymore. |
I'm getting this error as of a couple days ago host was already defined as '127.0.0.1'
same in browser pop-up error |
when I add the livereload js to the browser it outputs the following in console
and guard doesn't report any attempts to connect hoping someone with more Ruby experience can take a stab at this 👍 |
tinkering with this a bit more seems similar to issues #37 the following was run after try to connect with a browser -- IP has been defined as 127.0.0.1
this comes back when I restart the server and connect with telnet first
uggg... |
I switched to using gulp-livereload. It works pretty well. This is my Gulpfile, in case anyone is interested. |
I'm experiencing the same problem using Ruby 2.1.1 with RVM on OSX 10.9.5. Both Firefox and Chrome show this issue. I've noticed that after initial connection port closes. Tried connecting both through 'localhost' as well as through IP127.0.0.1. |
Any progress with this issue? I have the same problem. |
there are numerous reports of this same issue, yet you closed it without any notice of an update or request for testing? come on.... poor project management 👎 |
@eramdam isn't the project owner. He probably wanted to stop the notifications coming from this issue, not to close it. He should have unsubscribed from it instead. |
Having the same issue now |
changing 0.0.0.0 to 127.0.0.1 solved the issue for me try it |
the localhost thing did not fix it for me:
I also get:
|
If anyone here is having connection issues, I urge you to first try: #150 and let me know if work (or not!). |
I can confirm that #150 is much better now I am running a decent version of Ruby ;) |
It could be that you have a new setup and haven't installed Livereload extension in your Text Editor. |
When I try to connect guard-livereload to the LiveReload Chrome extension I get this error in Chrome. I'm under Mac OS 10.9.3 with Ruby 2.0.0-p247 using rbenv.
Here is the content of my Guardfile
And this is the output of guard in the terminal
The text was updated successfully, but these errors were encountered: