-
ERROR: failed to bind Omnis Server Socket
Dear $all,
I’m trying to set up an Omnis server on AWS according to TecNotes
https://www.omnis.net/developers/resources/technotes/tnjs0007.jsp
and
https://www.omnis.net/developers/resources/technotes/tnjs0003.jsp#content
So far, so good – but when I try to run Omnis on the Windows Server, I get the error that it ‘failed to bind Omnis Server Socket’.
What’s wrong here?
Thanks for your help!
Uwe
-
4 Replies
-
Hi Uwe,
looks like the socket for the node interface is already in use. It should not matter if you are not using the javascript worker object.
Best,
Andreas
-
Hi Andreas,
Thank you for your prompt answer!
So the error message refers to the Node.js port on 6102, and not the Omnis Server port which I put on 5902?
I’m not using the worker object, but where could I change Node.js port on 6102?
Thanks a lot & have a great weekend!
Uwe
-
-
Hello Uwe,
you can change this in remote_debug_server_config.json, located in the folder clientserver/server/remotedebug in the data folder of the Omnis installed tree.
Best,
Andreas
-
Great, thanx Andreas!
-
Log in to reply.