Can't see web interface of openvas

Community Containers
1

Hello. After update openvas to version “v26.14.0” can’t see web interface of openvas (502 error). What logs should I provide?

1 Like
2

Hallo bhr2o,
Version 26.14.0 works for me. Have you already added the new configuration to the docker-compose.yml file?
gsa:
gsad:
gvm-config:
nginx:

3

Hello TRai12. I downloaded and launched the container containers using a new Docker Compose File. OpenVAS located behind nginx reverse proxy which forward requests to openvas 9392 port and in logs of nginx I’ve got 111: Connection refused. This behaviour happend when we update openvas.

Update:

If I remove 127.0.0.1 and leave only ports 9392:9392 I can get response from web servers, but can’t load web interface because of “to many redirects”.

nginx:
image: ``registry.community.greenbone.net/community/nginx:latest
ports:
- 127.0.0.1:443:443
- 9392:9392

4

Hello bhr2o,

if you are using your own Nginx reverse proxy, you can completely omit or comment out the

nginx:

section.

bjoernricks has described the crucial settings for this here:

You need to use the following in

gsad:
environment:
GSAD_ARGS: “–listen=0.0.0.0 --http-only -f”
volumes:
- gsa_data_vol:/usr/local/share/gvm/gsad/web:ro

if the nginx and openvas containers are not on the same Docker network, you also need

ports:
- 9392:9392

Hope this helps
Best regards

3 Likes
5

Thank you TRai12! This helped! Web interface is available via nginx proxy.