5000 does not listen

[AI0TSec]

I follow the steps to enterdocker run -d --net host --name osmedeus mablanco/osmedeus, but port 5000 does not listen I AM SO SAD.PLEASE HELP.thanks

[mohammed-sec2010]

also, the port is not working in google cloud

[AI0TSec]

also, the port is not working in google cloud

Starting the Docker, I found that the 5000 port is not being monitored. It has nothing to do with Google Cloud? How can I solve this?

[mablanco]

Hi. When you use the --net host parameter (host network mode), the Docker service directly exposes the container ports and therefore publishing them is not needed. That's why port 5000 doesn't appear in docker ps output. It doesn't mean that the port is not being exposed. You can check what ports are open using command netstat -plunt.

Your issue has nothing to do with Docker. It may be related to your local firewall, so check your rules (depends on your distro).

Best regards.

[Hax0rG1rl]

@mablanco

Hi,

I have pulled out the docker image. Scans seem to work okay, port 5000 is listening but no http connection is allowed.

Any ideas?

Thanks!

[mablanco]

Hi. As I said previously, check if your local firewall rules block incoming connections to port 5000. It would be helpful if you could get the logs from the container and see what exactly is provoking the connection reset.

[Hax0rG1rl]

Okay, so the trick is simple: https://127.0.0.1:5000 instead of http://127.0.0.1:5000. Thanks anyway.

[mablanco]

Oh yes, you're right, didn't notice you were using plain HTTP. I'll update the README to reflect this. Thx!