[EDIT] : This post doesn’t work anymore with the latest versions of nuclei, look instead at My bounty infrastructure with Docker

Recently, I teased on Twitter a new version of AutoRecon with a web interface :

AutoRecon panel

But it was without counting on the incredible work of Yogeshojha and if you haven’t seen it yet, I advise you to go take a look at Rengine which according to the repository is automated reconnaissance framework with a web interface and rather than starting from scratch, it is based on existing tools.

Rengine panel

I propose here to show you quickly how to install it and access it in HTTPS. Since the latest versions of Rengine, it also includes a Nginx container (with certificate generation) unfortunately this did not suit me, so I adapted the configuration to fit my current architecture.

In addition to removing the docker-compose.setup.yml file I made changes in the Makefile and docker-compose.yml file which you can find here.

Next, I created a small script that will install the different dependencies (Nginx, Docker, Certbot) and configure Nginx.

Prerequisites are to have a domain pointing to your server. Concerning this one, I recommend you to take a VPS with at least 2Gb of RAM because I had difficulties to install Rengine on a machine with 1Gb especially with the installation of some tools or without going into details, Go consumes too much memory to install them.

The script can be accessed here. The only thing to do is to modify the two variables at the beginning of the script to put your domain name and your email address.

this one can be used for two purposes :

  • You install Nginx and Docker (and thus Rengine) on the same machine.
  • You install Nginx and Docker (+Rengine) on two different machines.

Rengine Nginx usecase

But It is not specifically for Rengine and can be used for any other container or application … So once you’ve changed the two variables and run the script

./Auto_Nginx_Rengine.sh

If you are in case number 2, you will have to modify the file /etc/nginx/sites-available/{your_domain_domain.tld}.conf and modify the line proxy_pass by changing the IP to that of your second server.

All that will be left is to install Rengine :

git clone https://github.com/yogeshojha/rengine.git
cd rengine
make up

Then all you have to do is create an account on the application with the command :

make username

That’s it, all you have to do is access your domain. Rengine Nginx usecase

It’s possible that you don’t have an image / CSS on the login page, but once logged in everything is ok.