Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems adding nmap engine #16

Open
emilva opened this issue May 10, 2019 · 8 comments
Open

Problems adding nmap engine #16

emilva opened this issue May 10, 2019 · 8 comments
Assignees
Labels
bug Something isn't working

Comments

@emilva
Copy link

emilva commented May 10, 2019

Hi, cool project you have made, it looks really useful!

I am trying to follow the docs on how to add a new scan-engine, but it always fails. Any pointers on what might be wrong?

Details:

This is one of the many configurations I have tried:
Screenshot 2019-05-10 15 54 24

The result is always Error:
Screenshot 2019-05-10 15 54 33

When I visit http://localhost:5101/engines/nmap/ I get a simple json object {page: "index"}. So the URL in the config must be correct?

@MaKyOtOx MaKyOtOx self-assigned this Jun 5, 2019
@MaKyOtOx
Copy link
Contributor

MaKyOtOx commented Jun 5, 2019

Hi !
How do you start the PatrowlManager ? if you've started with the docker-compose, the python application won't be able to reach the 'localhost'. You'd rather have to set the host address (host.docker.internal, ip address of docker0 iface, ...)

@MaKyOtOx MaKyOtOx added the bug Something isn't working label Jun 5, 2019
@guiguiabloc
Copy link

Hi,

Same problem for me.
launch PatrowlManager with start-server :

./start-server.sh
postgres db started. Nothing to do
supervisord started. Nothing to do
No changes detected
Operations to perform:
Apply all migrations: admin, assets, auth, authtoken, contenttypes, django_celery_beat, django_celery_results, engines, events, findings, rules, scans, sessions, settings, users
Running migrations:
No migrations to apply.

0 static files copied to '/data/PatrowlManager/staticfiles', 209 unmodified.
[2019-06-12 09:14:54 +0000] [125644] [INFO] Starting gunicorn 19.9.0
[2019-06-12 09:14:54 +0000] [125644] [INFO] Listening at: http://0.0.0.0:8000 (125644)
[2019-06-12 09:14:54 +0000] [125644] [INFO] Using worker: sync
[2019-06-12 09:14:54 +0000] [125649] [INFO] Booting worker with pid: 125649

Launch engine-nmap 👍

env/bin/python engine-nmap.py

  • Serving Flask app "engine-nmap" (lazy loading)
  • Environment: production
    WARNING: Do not use the development server in a production environment.
    Use a production WSGI server instead.
  • Debug mode: off
  • Running on http://0.0.0.0:5001/ (Press CTRL+C to quit)
    127.0.0.1 - - [12/Jun/2019 10:32:19] "GET /engines/engine-nmap/status HTTP/1.1" 200 -

But in console, stay in error :/

nmapengine

@guiguiabloc
Copy link

guiguiabloc commented Jun 12, 2019

ok find the error.
the correct url for engine is : http://127.0.0.1:5001/engines/nmap/

But in remote not working :/

nmapengine

The "info" work

info

@MinhNamNguyen
Copy link

Hi, i have the same problem,
I can launch Patrowl and nmap, the servers are running, can display the results, but when i create an engine, it's in error state. I tried both ip 0.0.0.0 and 127.0.0.1, also i can't display the engine info.

@Fireless2013
Copy link

Hello,

It is the same for me, have you a solution for this problem ?

Thank you.

@LukeDInfosec
Copy link

Same problem

@mharisss
Copy link

Same problem for me too. I've tried both ip 0.0.0.0 and 127.0.0.1 as well :-/

@roelstorms
Copy link

I notice that you run your scanners in docker using:

usr/bin/python3 /usr/bin/gunicorn engine-nmap:app -b 0.0.0.0:5001 --access-logfile -

which makes it hard to debug the issue. Maybe gunicorn is writing an error log. Maybe it's better to write to a file? Also for the error log.

gunicorn docs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

8 participants