Nmap fails to connect to targets

In our attempts to get Greenbone to operate via https, we were able to get the gui accessible, but the scanning capabilities of the system were broken - no scans would return any data. The scans would run, but they would not return any information.

After quite a bit of troubleshooting, we have completely removed all of the containers and returned to the default configuration. We are still seeing the same behavior, so I’m back to troubleshooting and think I’ve found something useful to ask here.

The simplest way to describe it is that I can run nmap from the host, but nmap run from opsd-openvas fails. We thought that this was related to the firewall on the host, but stopping the firewall doesn’t appear to have an effect on our tests.

I presume it’s an issue with the host / docker and not the containers themselves (since they were literally recreated from scratch), but I’m hoping for some suggestions regarding where we should be looking at the communication between host and containers.