Can't access web interface. No feed version available yet. OSPd OpenVAS is still starting

Hello! I’m trying to deploy the vulnerability scanner on my Ubuntu server via containers. I followed the instructions from the official site, and it looks like docker containers are running, but when I try to use the web interface, it is not working.

Logs:

notus-data-1           | files copied.
gvmd-1                 | md manage:   INFO:2024-08-07 13h10.23 utc:61: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
gvmd-1                 | md manage:   INFO:2024-08-07 13h10.33 utc:62: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
gvmd-1                 | md manage:   INFO:2024-08-07 13h10.43 utc:63: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
openvas-1              | libgvm util:MESSAGE:2024-08-07 13h10.43 utc:32: Updated NVT cache from version 0 to 202408070608
ospd-openvas-1         | OSPD[7] 2024-08-07 13:10:43,427: INFO: (ospd_openvas.daemon) Finished loading VTs. The VT cache has been updated from version 0 to 202408070608.
gvmd-1                 | md manage:   INFO:2024-08-07 13h10.53 utc:64: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
gvmd-1                 | md manage:   INFO:2024-08-07 13h11.03 utc:65: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting
gvmd-1                 | md manage:   INFO:2024-08-07 13h11.13 utc:66: osp_scanner_feed_version: No feed version available yet. OSPd OpenVAS is still starting

Hi sipikq, You will have to explain what is “not working” exactly. :slight_smile:

1 Like

I have an Ubuntu server at my local network. I have deployed docker containers (following these instructions ) by connecting to this server via ssh. The IP address I used for the deployment is 127.0.0.1 (default one). But when I’m trying to access the web interface from my laptop (and being connected to the VPN) typing the internal IP address (like 192.168..) of this server in my network, it shows that it refused to connect.

Hope this helps

You can see some suggestions on the error page itself. These are valid things to verify. Also note that Docker containers are assigned an IP address on a separate subnet than the host. By default, Docker uses the 172.17.0.0/16 subnet for its default bridge network, but this can be customized.

This means that GSA would not be available on the same public IP address as the host machine you installed them on via SSH as you expected. The Enterprise Trial VM may be an easier sword to weild from the perspective that using a bridged network interface will result in an IP address on the same standard local network subnet (typically 192.168.1.0/24).

2 Likes