Skip to content
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

Using domain name in ROOT_URL cause websocket issue #119

Open
minyixiecc opened this issue Mar 18, 2016 · 4 comments
Open

Using domain name in ROOT_URL cause websocket issue #119

minyixiecc opened this issue Mar 18, 2016 · 4 comments

Comments

@minyixiecc
Copy link

I have an issue on using the cluster which cause websocket handshake failing.

I set the ROOT_URL = "http://domain-name" (example, http://www.xyz.com.au), and set endpoint in a options object in code before cluster.register:

var options = { endpoint: "ip-address:port"}

For example, endpoit:"192.168.2.1:80".

After I run meteor, the websocket handshake fails. If I use ip address to ROOT_URL, everything works fine.

I also tries ROOT_URL = "http://domain-name:port" but no luck.

If you have any clue, please let me know. Thank you for your help.

@MasterJames
Copy link

Endpoint has an N missing you have endpoit maybe that is the issue?

@minyixiecc
Copy link
Author

@MasterJames Thank you but that is "point" in my code.

@MasterJames
Copy link

Ah good. So can you access the port from the target machine?
You can use SSH or even docker exec with bash or even curl directly to see if it's blocked by firewall rules or something?

@minyixiecc
Copy link
Author

Yes, i can access it using SSH. My server is on aws, ec2 instance. I set
the port, 80 to be open to all traffic.
On 18 Mar 2016 1:41 pm, "Master James" notifications@github.com wrote:

Ah good. So can you access the port from the target machine?
You can use SSH or even docker exec with bash or even curl directly to see
if it's blocked by firewall rules or something?


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#119 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants