This is my first try with the product and I’ve installed the whole stack following the official documentation for Docker (https://greenbone.github.io/docs/latest/22.4/container/index.html). Everything went fine at first shot (which is always surprising ) but when I try to connect to the service (first connection with default user/password), I just get an error message “The Greenbone Vulnerability Manager service is not responding.”.
Using Portainer, I can see that all of the “data containers” are flagged as “exited” and the stack regularly returns error message “Failed loading environment”. I wanted to have all data grouped into a dedicated folder, so slightly modified the provided compose file as follow:
All volumes have been updated: vt_data_vol:/mnt → ~./Applications/openvas/data/vt_data_vol
GSA port has been changed (don’t think it has any impact)
Finally found out that the software firewall running on my VPS was preventing me from accessing the proper port… By the way, I tried to run a simple scan on my system and the scan was stuck at 8% for days (I even forgot I ran it ), so I once again suspect the firewall is playing tricks (on outgoing ports now).
Is there any documentation that lists the requested in/out ports I should authorize with the firewall to get normal behavior?
Do not run any firewall, that will impact your scan results. As well you should not enable any firewall components, like session tracking, that can overflow your internal tables as well and impact your results as well.
Using an Oracle VPS, I’m not sure I have the choice over activating the firewall or not… Hence my question: is there any way to know which ports are used by the solution, so I can “clear them the way”?
I am sorry there is no way to know which ports need to be allowed. This depends on the to be run Vulnerability Tests and can change daily with new Vulnerability Tests in the feed.