Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in generate-indexer-certs #728

Closed
SYRTI opened this issue Oct 14, 2022 · 2 comments
Closed

Error in generate-indexer-certs #728

SYRTI opened this issue Oct 14, 2022 · 2 comments

Comments

@SYRTI
Copy link

SYRTI commented Oct 14, 2022

Cant generate the Certificates with docker-compose -f generate-indexer-certs.yml run --rm generator
because the image image: wazuh/wazuh-certs-generator:0.0.1
seems to point at PACKAGES_URL=https://packages.wazuh.com/4.3/ which throws this message:
Cert tool does not exist in any bucket
ERROR: certificates were not created

@maxferrario-msf
Copy link

I have the same error when I run the command to generate the certificates

~/wazuh-docker/single-node$ sudo docker-compose -f generate-indexer-certs.yml run --rm generator
/snap/docker/2285/lib/python3.6/site-packages/paramiko/transport.py:33: CryptographyDeprecationWarning: Python 3.6 is no longer supported by the Python core team. Therefore, support for it is deprecated in cryptography and will be removed in a future release.
from cryptography.hazmat.backends import default_backend
Creating network "single-node_default" with the default driver
Pulling generator (wazuh/wazuh-certs-generator:0.0.1)...
0.0.1: Pulling from wazuh/wazuh-certs-generator
d7bfe07ed847: Pull complete
a6023cfa8265: Pull complete
6135753eefe9: Pull complete
9aaf0dae5d3f: Pull complete
Digest: sha256:6fc929d58d01b789d4a19c5da476c78cc267c0af07d1b22227ccae49acb084dc
Status: Downloaded newer image for wazuh/wazuh-certs-generator:0.0.1
Creating single-node_generator_run ... done

Cert tool does not exist in any bucket
ERROR: certificates were not created
ERROR: 1

@rauldpm
Copy link
Member

rauldpm commented Oct 25, 2022

Closed for being a duplicate of: #733

@rauldpm rauldpm closed this as not planned Won't fix, can't repro, duplicate, stale Oct 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants