Open mbeaudru opened 8 years ago
Weird, but changing the listening port of my app solved the issue (from 9000 to 3000 in my case) while all these didn't:
I've been having a similar problem on OSX since a couple of days ago. Firefox is fine, but for me it won't connect to the websocket if I use localhost:8181 in Chrome anymore. Using 127.0.0.1 or 0.0.0.0 seems to be ok.
It looks like this may be related to either HMR or engine.io. I assume you've tried it without HMR enabled?
I had the same issue after toying with authentication and https. I think clearing the localstorage was the fix that worked (I don't have the issue now) but I can't tell for sure because I got a bit angry and did a lot of stuff in parallel like removing the rethinkdb folder.
I was working fine for hours with chrome and it suddently stopped working, but thanks to @Taximan advice I tried to clear localstorage and it worked like a charm ! :smile:
@deontologician I didn't tried without HMR but with these two info maybe you can connect the dots ?
We just removed engine.io, so if this persists past 2.0, we can see if it's still happening
One more data point, I also was getting this on Chrome on OSX (not on Firefox), started seemingly randomly, inspecting some of the network calls showed message about expired token, clearing local storage fixed it.
I'm late to the party but this will disable checking for the token in the first place so you don't have to keep clearing the local storage.
var horizon = Horizon({host: 'hostname', authType: 'unauthenticated'});
Hi,
I am currently developping an SPA on chrome and everything was working fine. But the issue is that now my hz client cannot connect to hz server and it seems to come out of nowhere counting that I changed nothing since the last time.
So I tried to launch the app on Firefox, and it worked just fine, even if some errors are occuring.
Here are the console logs that appear on Chrome (not working):
and there are the one on Firefox (working):
As you can see, I have not installed React (nor Redux) devTools on Firefox. I tried to deactivate them in chrome to check if it was related to them, but there aren't any differences.
If it solves by itself just like it breaks by itself (apparently), I'll tell here right away.
Info: When I run hz serve --dev, I have many logs in the terminal that I don't understand but it seemed without consequences (at first, I guess). It may be a clue to understand whats going on, so here there are: