search

mikesplain / openvas-docker

A Docker container for Openvas
MIT License
762 stars 302 forks source link

Error: received handshake message out of context #107

Closed dec0dOS closed 5 years ago

dec0dOS commented 7 years ago

Hi! I'm getting "Error: received handshake message out of context" in /var/log/openvas/gsad.log after startup. logs.txt

Do you have any ideas about it?

udiromano commented 7 years ago

Same problem here...

mikesplain commented 7 years ago

Hmm how much memory do you have available? I've seen things like this when you're limiting docker's memory

lancelakey commented 7 years ago

I see the same error. I've configured Docker for Mac with 12 GB of memory.

mikesplain commented 7 years ago

@lancelakey can you provide your docker command to start the container and any logs?

udiromano commented 7 years ago

I solved the problem, i've stopped the gsad service and ran it manually like so: /usr/sbin/gsad --listen=0.0.0.0 --port=4000 --mlisten=127.0.0.1 --mport=9390 @mikesplain is there any chance you'll change the Dockerfile to support that?

mikesplain commented 7 years ago

@udiromano Can you try the new build once https://github.com/mikesplain/openvas-docker/pull/109 finishes building? That should fix it!

mikesplain commented 7 years ago

Closing due to inactivity. Please reopen if you're still seeing issues!

lexfrei commented 6 years ago

Same on the latest. Details in logs. Logs and creation: https://gist.github.com/lexfrei/4d8f4b994eadf886720fb3d479908d5d Container inspect: https://gist.github.com/lexfrei/483a26da33cf2c46c8fdc3dd8d75031b

lexfrei commented 6 years ago

@mikesplain I can't reopen this issue. Can you reopen it for me plz?

bjoernricks commented 6 years ago

Are you still able to connect to gsad or is the connection refused? Which browser do you use when accessing gsad? The problem should be on the client side of gsad aka your browser see https://lists.gnu.org/archive/html/libmicrohttpd/2011-09/msg00003.html

lexfrei commented 6 years ago 
sviridkin@mbp:~$ curl localhost:443
curl: (52) Empty reply from server
✗: 52 @ Wed Mar  7 18:51:16 MSK 2018

Same in latest Safari and Chrome

UPD: But it works with https prefix!

sviridkin@mbp:~$ curl https://localhost:443/  --insecure
<html><body>Code 303 - Redirecting to <a href="https://localhost/login/login.html">https://localhost/login/login.html<a/></body></html>
✓ @ Wed Mar  7 18:52:56 MSK 2018

UPD2: So, it's not a bug. You can close this issue again :)

bjoernricks commented 6 years ago

My bet is gnutls handles some tls stuff more strictly then others.

lexfrei commented 6 years ago

Worked as expected: there is no http handling on https port. It's not friendly, but correct.

fredairic[bot] commented 6 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.

fredairic[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.

juanluisbaptiste commented 4 years ago

Hi,

I'm getting this error but when running this image behind a reverse proxy like traefik.

Maybe it has to do with the fact that the proxy is terminating ssl ? I'm using letsencrypt certs in the traefik proxy, so there's no need to run openvas with ssl enabled. How can I disable https on this image to see if that's the issue?

thanks/

moxli commented 4 years ago

@juanluisbaptiste you need to pass --http-only as a startup parameter to GSAD I am not sure where to set it in this image. https://www.mankier.com/8/gsad