Password or Bad cert?

[picasso566]

I hate to open another ticket here when I probably screwed up somewhere.

I tried to set this up 3 times and they all worked. This time, I finally have a permanent place for the container to run scans on a quarterly basis. It ran through all the updates, but now I cannot log in. All the other times I was able to do so just fine. Here is the docker command I used: sudo docker run --detach --publish 8080:9392 -e PASSWORD="admin" --volume openvas:/data --name openvas immauss/openvas

I try to log in with admin / admin I get this message: The Greenbone Vulnerability Manager service is not responding. This could be due to system maintenance. Please try again later, check the system status, or contact your system administrator.

There's also this message, but I don't care about TLS, this can only be viewed on localhost Warning: Connection unencrypted The connection to this GSA is not encrypted, allowing anyone listening to the traffic to steal your credentials. Please configure a TLS certificate for the HTTPS service or ask your administrator to do so as soon as possible.

Any help is welcome. TIA

Oh, and the latest logs:

==> /usr/local/var/log/gvm/redis-server.log <==
11:M 13 Sep 2022 12:49:28.118 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
16:C 13 Sep 2022 15:25:07.804 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
16:C 13 Sep 2022 15:25:07.805 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=16, just started
16:C 13 Sep 2022 15:25:07.805 # Configuration loaded
16:M 13 Sep 2022 15:25:07.807 # Server initialized
16:M 13 Sep 2022 15:25:07.808 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
16:C 13 Sep 2022 15:33:30.155 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
16:C 13 Sep 2022 15:33:30.155 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=16, just started
16:C 13 Sep 2022 15:33:30.155 # Configuration loaded
16:M 13 Sep 2022 15:33:30.158 # Server initialized

==> /usr/local/var/log/gvm/openvas.log <==
libgvm util:MESSAGE:2022-09-13 15h36.05 utc:587: Updated NVT cache from version 0 to 202209131016

[picasso566]

And the dreaded redis overcommit_memory warnings =(

[picasso566]

I found ticket 140 which gave me a slightly better understanding of the container and stopped my existing instance, and fired up a new one with the same mounted volume and did a manual update:

Original command: docker run --detach --publish 8080:9392 -e PASSWORD="Your admin password here" --volume openvas:/data --name openvas immauss/openvas

Then fire up a new one:

docker run --detach --publish 8087:9392 -e PASSWORD="admin" -e HTTPS=true -e GSATIMEOUT=60 -e SKIPSYNC=true --volume openvas:/data --name openvas2 immauss/openvas:latest

docker exec -it openvas2  /scripts/sync.sh

Thanks