You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Never mind.
I had to create a new user via runuser -u _gvm -- gvmd --create-user=name --new-password=pass.
Now it's (almost) perfect. Can't make it run on https. But hopefully I can figure that out.
Best,
Val
Hi,
sorry to bother you this way, but your docker version of OpenVAS/GVM seems to be promising - at least - I am almost there...
Just that I cannot login with your default credentials (admin:admin).
The logs seems to suggest that GVM is running OK, it even downloads feeds etc. But, whatever I do, e.g. creating my own user (via gvmd --create-user), I still cannot log in.
I'm not sure if the reason could be the GVM at the login page page complains the session is not encrypted (https), I guess not. I tried to publish it at port 443, but for that, I think I would GVM to have a certificate already created. It does not make any difference trying 443:9392.
Any suggestions?
Thank you!
VL
The text was updated successfully, but these errors were encountered:
I have the same problem. @dsc-vlds how where and when do you run that the gvmd create user command?
I've tried to run via docker container exec but it always fails
Never mind.
I had to create a new user via runuser -u _gvm -- gvmd --create-user=name --new-password=pass.
Now it's (almost) perfect. Can't make it run on https. But hopefully I can figure that out.
Best,
Val
Hi,
sorry to bother you this way, but your docker version of OpenVAS/GVM seems to be promising - at least - I am almost there...
Just that I cannot login with your default credentials (admin:admin).
The logs seems to suggest that GVM is running OK, it even downloads feeds etc. But, whatever I do, e.g. creating my own user (via gvmd --create-user), I still cannot log in.
I'm not sure if the reason could be the GVM at the login page page complains the session is not encrypted (https), I guess not. I tried to publish it at port 443, but for that, I think I would GVM to have a certificate already created. It does not make any difference trying 443:9392.
Any suggestions?
Thank you!
VL
The text was updated successfully, but these errors were encountered: