The connection was reset - ERR_SOCKET_NOT_CONNECTED

142 views
Skip to first unread message

Marc

unread,
Jun 20, 2022, 8:05:26 AM6/20/22
to Enterprise Web Developer Community
Hi,
trying out the qewd-baseline, I do not get it working. When I point the browser to http://localhost:3001/helloworld (I chose the port 3001), I get the respons :
"the connection was reset" (firefox) or "site can't be reached - ERR_SOCKET_NOT_CONNECTED" (chrome)

It seems QEWD is running succesful, these are the last lines of my docker log (docker logs -f qewd) :
...
%YDB-S-JNLSUCCESS, Show successful
%YDB-I-MUJNLSTAT, End processing at Mon Jun 20 09:59:30 2022
* Starting internet superserver xinetd
...done.
Starting QEWD
Double ended queue max length set to 20000
Custom Body Parser has been loaded
webServerRootPath = /opt/qewd/mapped/www/
route /jsdb will be handled by qx.router
route /qewd will be handled by qx.router
Worker Bootstrap Module file written to node_modules/ewd-qoper8-worker.js
========================================================
ewd-qoper8 is up and running. Max worker pool size: 2
========================================================
========================================================
QEWD.js is listening on port 3001
========================================================
Anyone an idea what is happening here?
Kind regards,
Marc

Marc

unread,
Jun 20, 2022, 9:07:23 AM6/20/22
to Enterprise Web Developer Community
Ok,
apparently it works when I'm using http://172.19.0.2:3001/helloworld/ so the IP of the container.
(Which I found when examinating the docker status : systemctl status docker)

Is there some bridging to do?

Marc
Op maandag 20 juni 2022 om 14:05:26 UTC+2 schreef Marc:

Marc

unread,
Sep 5, 2023, 11:15:54 AM9/5/23
to Enterprise Web Developer Community
I figured out my mistake.

The start.sh script specifies host and container port as follows :
docker run -d --name qewd --rm --network qewd-net -p 3001:8080 -v /mnt/cache.dsk/qewd/qewd-baseline:/opt/qewd/mapped  rtweed/qewd-server

So since docker port assignement is : -p host_port:container_port the host maps 3001 to 8080 in the container.

Yet for my instance it works with -p 8080:3001 since the server in the container is listening to port 3001.

I guess the reason for that is that I added a "port" line in the /qewd-baseline/configuration/config.json file (at least I think I did, can't remember) :
{
  "qewd_up": true,
  "qewd": {
    "bodyParser": "body-parser",
    "port": "3001"
  }
}

Marc
Op maandag 20 juni 2022 om 15:07:23 UTC+2 schreef Marc:
Reply all
Reply to author
Forward
0 new messages