Why pusher javascript client can not subscribe when application is running on localhost.
vetal20600 opened this issue · 5 comments
I have Rails application and I want to us posa. I think it's beautiful software
However I am having issues using Posa and I am trying to figure out why it happened.
When I try to put settings in my Rails application which allow to connect to http://poxa.herokuapp.com/ it shows me next log:
As you see there are no API Messages above.
But when I am deploy and run release version on localhost I see no subscription from clients (I see only API Messages).
I am not sure what is reason. (May be it is not even Posa related)
Ok what I know now. For some reason javascript pusher client works (connect/subscribe and so one) if I put:
Host: http://poxa.herokuapp.com
App key: "app_key"
App id: "app_id"
App secret: "secret"
Port: 80
but my Rails application does not produce any api messages.
At the same time if I run on localhost, it produces messages but pusher javascript client does not work. Can't figure out what happens. Maybe this is server security related so I have to check router and open some ports?
Yeah maybe some browser security because of the host difference? If you could give me a way to replicate this issue (a simpler version of your use case?) I could help debugging
I am trying to connect Posa with peatio which uses Pusher service by default.
__
One more thing. I did more tests with Peatio and Posa.
That software connected with your instance of Posa (poxa.herokuapp.com) and deployed on server with dedicated IP works as expected.
At the same time that software deployed on machine which is put in router does not generate API Messages, only javascript pusher client works in this case
Did anyone get this working?
I am facing the same problem with some domains. When I point the same docker to a different domain it works.
Not sure what it has to do with the domain. Can someone point out what might be wrong?