Hi,
I installed Greenbone’s container security scanner on Debian 12 by following the steps on the link below:
Everything works as expected, feeds update successfully and I can scan hosts. The issue occurs when I reboot my Debian 12 machine, NVT feed fails to update with message “Synchronization issue: Could not connect to scanner to get feed info”
SCAP, CERT and GVMD_DATA feeds update successfully.
Can you assist?
Thank you!
I posted this a month ago and have not gotten any replies. am I the only one having this issue?
Hi, I have identical issue on Ubuntu 22, anyone can please explain the solution?
Hi. Same error message after last update on January 17, 2025. Docker version being used for months.
Ubuntu 22.04.3 LTS.
Synchronization issue: Could not connect to scanner to get feed info
Now I can’t run the scanner because “Feed is currently syncing. Please try again later”.
Any clue? Thanks.
2 posts were split to a new topic: Dependency changes and workaround/build script
A post was merged into an existing topic: Dependency changes and workaround/build script
I have exact the same problem on debian 12.
Any Ideas how to fix that. Many thanks.
Hi, I am sorry but I can’t reproduce your issue with the latest container images from today. Maybe you are still using an old compose file?
Hi,
So if I want to resolve this issue, I have to remove the old container and install the latest one? If yes, is there a way to export the entire configuration (targets and scans) and import it to the new one?
Thanks!
We also have this problem with newest composer file and container images.
Synchronization issue: Could not connect to scanner to get feed info
It is also on NVT, the rest works.
No. The data is stored in docker volumes which are independent of the container images. Just download the newest compose file and run a compose up.
okay. I will figure out how to do that. Thanks!
so maybe I shouldn’t try to change the composer file then lol
@bricks thanks for your advice. I downloaded the latest compose file by:
curl -f -O -L https://greenbone.github.io/docs/latest/_static/docker-compose.yml --output-dir "$DOWNLOAD_DIR"
and then:
docker compose up
and now the feed is working correctly.
Thanks!
I did the same and it worked fine, until the machine was rebooted and the issue then returned. This is not fixed.
This is only a temporarily fix, the feed breaks again after some time.
yeah same here lol so I do the procedure I posted every time I reboot lol
correct. This issue has not been resolved.
Same here. Devs think they have resolved this and have closed the issue in GitHub, but it is very much NOT resolved.
Does anybody know if there is any update on this? Has any been able to resolve it? I would believe everybody has this issue…
We have tried with new installation 3 times now, ofc with the newest composer file. We follow the documentation on deploying the community containers. But everytime it give us the error “Synchronization issue: Could not connect to scanner to get feed info” on the NVT feed. We don’t even try to update the feed it just happens after some days… and as long as this error is there the scan will always fail or not run.