Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

error running on live https server #50

Closed
ctf0 opened this issue Oct 3, 2016 · 13 comments
Closed

error running on live https server #50

ctf0 opened this issue Oct 3, 2016 · 13 comments

Comments

@ctf0
Copy link

ctf0 commented Oct 3, 2016

  • Laravel v5.3.15
  • laravel-echo-server v1.0.12
  • node v6.7.0
L A R A V E L  E C H O  S E R V E R

Starting server...

✔ Running at something.com on port 6001
✔ Channels are ready.
✔ Listening for redis events...
✔ Listening for http events...

Server ready!

events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL 104.31.85.98:6001
    at Object.exports._errnoException (util.js:1036:11)
    at exports._exceptionWithHostPort (util.js:1059:20)
    at Server._listen2 (net.js:1239:19)
    at listen (net.js:1288:10)
    at net.js:1398:9
    at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:62:16)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:81:10)

here is the init info aswell

{
    "appKey": "xxx",
    "authEndpoint": "/broadcasting/auth",
    "authHost": "",
    "database": "redis",
    "databaseConfig": {
        "redis": {},
        "sqlite": {
            "databasePath": "/database/laravel-echo-server.sqlite"
        }
    },
    "devMode": false,
    "port": "6001",
    "referrers": [],
    "verifyAuthPath": true,
    "verifyAuthServer": true,
    "host": "something.com",
    "protocol": "https",
    "sslCertPath": "/etc/nginx/ssl/something.com/server.crt",
    "sslKeyPath": "/etc/nginx/ssl/something.com/server.key"
}

and here is the console error

socket.io.js:3511 GET https://something.com:6001/socket.io/?EIO=3&transport=polling&t=LUD08rI net::ERR_CONNECTION_REFUSED
@tlaverdure
Copy link
Owner

Looks like an error with the port. You sure that you don't have an instance already running on the same port?

@ctf0
Copy link
Author

ctf0 commented Oct 7, 2016

nop :(, i double checked for the port number and this one is free

@jonnywilliamson
Copy link
Contributor

That ip address is a cloud flare ip address.

It's likely cloudflare is getting in the way of your connection in some manner.

@ctf0
Copy link
Author

ctf0 commented Oct 14, 2016

i stopped cf, and back to my public ip but nothing changed

@IamSwap
Copy link

IamSwap commented Oct 20, 2016

Any updates on this? Facing same issue!

@rorymcdaniel
Copy link

Just a thought, I had this same issue, I was trying to run laravel-echo-server on my computer, but instead I should have been running it on the Vagrant host. That resolved it for me.

@ctf0
Copy link
Author

ctf0 commented Oct 26, 2016

@rorymcdaniel its working fine on vagrant but on live https server sadly its not :(

@IamSwap
Copy link

IamSwap commented Nov 6, 2016

any updates on this?

@ctf0
Copy link
Author

ctf0 commented Nov 6, 2016

i started using pusher instead but it takes almost 10 seconds on each page load just to connect to the service 😢 .

@ctf0
Copy link
Author

ctf0 commented Nov 23, 2016

@tlaverdure any news over this ?

@ctf0 ctf0 changed the title error running on live server error running on live https server Dec 26, 2016
@markimpmc
Copy link

markimpmc commented Jan 6, 2017

Try to change host to 0.0.0.0.
I've had the same error, but it worked for me.

@tlaverdure
Copy link
Owner

This works perfectly fine for me with a similar configuration. Only thing that I ran to is that I needed to run the command to start with sudo since the certificate files are located in the etc directory.

@mahdi4187
Copy link

kill -9 $(lsof -t -i:PORT)

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

No branches or pull requests

7 participants