Skip to content

Rsync failing behind proxies #324

@huornlmj

Description

@huornlmj

After spending some time following the guidance here (https://securecompliance.gitbook.io/projects/gvm_image) and observing the feeds failing to download due to RSYNC proxy issues, I wanted to share some feedback here. The documentation should contain a section for those operating behind proxies. I found that feeds only updated if I provided environment variables, specifically:

--env RSYNC_PROXY="proxy.internal.local:3128"

Note the omission of the protocol before proxy.internal.local

So in total, the working command for behind a proxy was:

docker run --detach --publish 8080:9392 --publish 5432:5432 --publish 2222:22 --env HTTP_PROXY="http://proxy.internal.local:3128" --env HTTPS_PROXY="http://proxy.internal.local:3128" --env RSYNC_PROXY="proxy.internal.local:3128" --env DB_PASSWORD="postgres DB password" --env PASSWORD="webUI password" --volume gvm-data:/data --name gvm securecompliance/gvm

By the way - thank you for making it so easy to deploy GVM! manual installation has become somewhat of an unnecessary 'rite of passage'.

Metadata

Metadata

Labels

documentationImprovements or additions to documentation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions