Grzegorz Siewruk
Grzegorz Siewruk
Lot of problems here probably. to start what is Your docker/docker-compose version? Just checked and tried to run it with: ``` gs:mixeway gs$ docker-compose version docker-compose version 1.29.2, build 5becea4c...
can You paste Your dockerfile? I would like to reproduce the problem and propose a solution
For some reason I am unable to reproduce Your error. However there are few things that are worth to mention: * Your change in ports is incorrect. `docker-compose` ports syntax...
I will try to run it on kali
Running out of ideas :( * [x] Checked on kali * [x] used docker-compose in v2.1.1 as You mentioned and here is my output: ``` ┌──(root㉿31ff41f925af)-[/tmp/mixeway] └─# docker-compose up [+]...
automatically closed due to inactivity
Hey, fast fix is to run OpenVAS jar with additional parameter ‘—server.ssl.key-alias=localhost’ I will introduce PR to fix this issue in few hours
And btw enable `--spring.profiles.active=noauth` to bypas mTLS auth (not recommended at prod instance)
@neginsadeghi this problem is somehow related with SSL/TLS configuration Can You confirm that: 1. You have generated key pair eg with `openssl req -new -newkey rsa:2048 -days 365 -nodes -x509...
That's for sure correct validation, problem is that most poms I am validating for my dev teams don't specify version in Pom and depend on the version maven will serve...