Open hectorthiele opened 9 years ago
I have a similar issue. Faye is running in the same place as my application, so when I set faye's address as the public address, my rails app can't acess it. If I set it to localhost the cliente browser will no access it. I know I can fix it using iptables, but doesn't seem a clean solution.
@foadmk how do you fix it using iptables? did you manage to find a solution?
I can't run the program in production mode.
When I open a view in localhost, it work fine, but when I run the project in 192.168.0.100:3000, it's not work and the message that appear is "connection refused". My firewall is out and I don't have idea of what is the problem.
My public_pub.yml file has this contain.
development: server: "http://192.168.0.100:9292/faye" secret_token: "secret" test: server: "http://192.168.0.100:9292/faye" secret_token: "secret" production: server: "http://192.168.0.100:9292/faye" secret_token: "secret" signature_expiration: 3600 # one hour
the ip 192.168.0.100 is a address in a internal network.
This IP is a server.
Note: when I run with the server address in localhost:9292/faye, it work fine.