thalesgroup-cert / Watcher

Watcher - Open Source Cybersecurity Threat Hunting Platform. Developed with Django & React JS.
https://thalesgroup-cert.github.io/Watcher
GNU Affero General Public License v3.0
856 stars 123 forks source link

Watcher does not respond to the configuration change for the host address in the .env file. #54

Closed Ral-A closed 2 years ago

Ral-A commented 2 years ago

Describe the bug Hello, I don't know if it is a general bug, or a particular case; but when starting the Watcher containers, the application server is initialized with the address http://0.0.0.0:9002/ by default. However, the installation guide refers that it can be modified, placing the new address in the "ALLOWED_HOST =" section of the .env file; then run the commands: docker-compose down docker-compose up When performing these actions, the Watcher server continues to raise with the default address. In the same way the changes are not applied when the mail server is configured.

Screenshots Address after changing in config file .env: image

image Docker version on which it runs: image

Desktop (please complete the following information):

Please I accept any recomendation to solve this problem. Thanks

Felix83000 commented 2 years ago

Hello Ral-A,

There is no issue. 0.0.0.0 is totally normal. It means that Watcher container will use your server IP address. For instance, if your server IP is 172.3.X.X Watcher will be available at http://172.3.X.X:9002

In the meantime, you need to set the ALLOWED_HOST to your server IP address or FQDN, for instance 172.3.X.X This settings is necessary to prevent security issues.

For the SMTP server, please check manually that the Watcher server can access it. (e.g. curl)

I hope it helps.

Regards,