Getting the desired certificates error when docker install wazuh

[begize]

HI everyone:
I installed docker according to the document and it is running normally, but an error occurs when getting the desired certificates. Can help me solve it?
The Linux version is ubuntu2404

---

mis@tguard:~/wazuh-docker/single-node$ sudo docker-compose -f generate-indexer-certs.yml run --rm generator
[+] Running 1/1
⠿Network single-node_default Created 0.9s
[+] Running 0/1
⠿ generatorError 1.8s
Error response from daemon: Head "https://registry-1.docker.io/v2/wazuh/wazuh-certs-generator/manifests/0.0.1": Get "https://auth.docker.io/token? scope=repository%3Awazuh%2Fwazuh-certs-generator%3Apull&service=registry.docker.io": read tcp 192.168.28.184:56392->34.226.69.105:443: read: connection reset by peer

---

[rauldpm]

Hello @begize , sorry for the late response.

Do you still have the problem?

Apparently, this problem is related to a connectivity issue, please make sure that your firewall is configured correctly to allow the connection, in case you are using a proxy, you will need to configure it as follows, as we state in the documentation https://documentation.wazuh.com/current/deployment-options/docker/wazuh-container.html#single-node-deployment (this also applies for a multi-node deployment)

# Wazuh App Copyright (C) 2017, Wazuh Inc. (License GPLv2)
version: '3'

services:
  generator:
    image: wazuh/wazuh-certs-generator:0.0.1
    hostname: wazuh-certs-generator
    volumes:
      - ./config/wazuh_indexer_ssl_certs/:/certificates/
      - ./config/certs.yml:/config/certs.yml
    environment:
      - HTTP_PROXY=YOUR_PROXY_ADDRESS_OR_DNS

I see that you are trying to pull revision 0.0.1, when the current version of 4.8.0 is 0.0.2, what version of Wazuh are you using? Did you update the repository as indicated in the documentation to maintain custom files? I couldn't reproduce your problem using 0.0.2 and 0.0.1, so it must be a connection issue.

I opened this issue so the Wazuh documentation can be updated wazuh/wazuh-documentation#7512

[begize]

Hi: After I tried to change the network environment and virtual platform, the installation could be normal, but I confirmed that the problematic network environment and firewall did not block any communication. This is a very strange problem, and I will continue to do so. Give it a try, thanks for your help~~ Raul Del Pozo Moreno ***@***.***> 於 2024年7月11日 週四 下午8:38寫道：

…

Hello @begize <https://github.com/begize> , sorry for the late response. Do you still have the problem? Apparently, this problem is related to a connectivity issue, please make sure that your firewall is configured correctly to allow the connection, in case you are using a proxy, you will need to configure it as follows, as we state in the documentation https://documentation.wazuh.com/current/deployment-options/docker/wazuh-container.html#single-node-deployment (this also applies for a multi-node deployment) # Wazuh App Copyright (C) 2017, Wazuh Inc. (License GPLv2) version: '3' services: generator: image: wazuh/wazuh-certs-generator:0.0.1 hostname: wazuh-certs-generator volumes: - ./config/wazuh_indexer_ssl_certs/:/certificates/ - ./config/certs.yml:/config/certs.yml environment: - HTTP_PROXY=YOUR_PROXY_ADDRESS_OR_DNS I see that you are trying to pull revision 0.0.1, when the current version of 4.8.0 is 0.0.2, what version of Wazuh are you using? Did you update the repository as indicated in the documentation to maintain custom files? I will open an issue to change the 0.0.1 reference in the documentation but I couldn't reproduce your problem using 0.0.2 and 0.0.1, so it must be a connection issue. — Reply to this email directly, view it on GitHub <#1415 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGLJEUPBWTUDZMABTL6JPA3ZLZ4DRAVCNFSM6AAAAABKLB67JSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRSHAZDONBTGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[rauldpm]

I'm glad it works, this may have been a temporary issue on the part of the Docker servers, in any case, feel free to create an issue if you encounter another problem!

[Rebits]

The issue seems to be solved. Closing