Signaling Server Error

Post reply

❤Follow Topic(3)

0 favourites

From the Asset Store

$21.99 USD

The official Scirra Multiplayer Signalling Server for helping peers find and connect to each other

- adddog
- - Joined 16 May, 2015
  - 1 topics • 4 posts
- 1
- 23 Jul, 2016
- Quote
run sigsegv.js I got these errors, someone help me?

events.js:141

throw er; // Unhandled 'error' event

^

Error: listen EADDRNOTAVAIL 182.61.38.18:80

at Object.exports._errnoException (util.js:873:11)

at exports._exceptionWithHostPort (util.js:896:20)

at Server._listen2 (net.js:1237:19)

at listen (net.js:1286:10)

at net.js:1395:9

at nextTickCallbackWith3Args (node.js:453:9)

at process._tickCallback (node.js:359:17)

at Function.Module.runMain (module.js:443:11)

at startup (node.js:139:18)

at node.js:968:3
- gumshoe2029
- - Joined 4 Mar, 2014
  - 31 topics • 1,416 posts
- 1
- 23 Jul, 2016
- Quote
Which server are you pinging? What is the domain URL?
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- adddog
- - Joined 16 May, 2015
  - 1 topics • 4 posts
- 1
- 23 Jul, 2016
- Quote
I am using a cloud server is assigned a public network IP, has no binding domain
- Whiteclaws
- - Joined 14 Feb, 2011
  - 197 topics • 2,234 posts
- 1
- 24 Jul, 2016
- Quote
Oh, you can't bind port 80 and 443 on public cloud servers, most of them have proxies that redirect http and https content to your application port, basically instead of 182.61.38.18:80, you gotta bind the port that is provided by your webservice (8080 maybe), (edit it in sigserv.js) so that you bind to 182.61.38.18:8080