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.

Sign up for GitHub

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

Jump to bottom

SSL Clickhouse error: can't connect to clickhouse: x509: certificate signed by unknown authority #410

Closed
DipalPrajapati opened this issue Mar 9, 2022 · 2 comments · Fixed by #415 or #426
Closed

SSL Clickhouse error: can't connect to clickhouse: x509: certificate signed by unknown authority #410

DipalPrajapati opened this issue Mar 9, 2022 · 2 comments · Fixed by #415 or #426
Assignees
@Slach
Milestone
1.3.2

Comments

@DipalPrajapati
Copy link

I am not able to take the backup of containerised plus secure clickhouse. It is giving below error.

clickhouse-backup create
2022/03/09 17:45:53.501070 error can't connect to clickhouse: x509: certificate signed by unknown authority
@DipalPrajapati DipalPrajapati changed the title error: can't connect to clickhouse: x509: certificate signed by unknown authority SSL Clickhouse error: can't connect to clickhouse: x509: certificate signed by unknown authority Mar 9, 2022
@Slach
Copy link
Collaborator

Slach commented Mar 9, 2022

Currently, clickhouse-backup doesn't support custom CA and self-signed certs

as quick workaround, you can apply follow configuration:

clickhouse:
  skip_verify: true

@DipalPrajapati
Copy link
Author

DipalPrajapati commented Mar 9, 2022 •
edited
Loading

Worked , thanks. Please move to close.

@Slach Slach self-assigned this Mar 9, 2022
@Slach Slach added this to the 1.3.2 milestone Mar 9, 2022
@Slach Slach mentioned this issue Mar 16, 2022
Merged
@Slach Slach mentioned this issue Apr 19, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Slach Slach

Labels
None yet
Projects
None yet
Milestone
1.3.2
Development

Successfully merging a pull request may close this issue.

prepare release 1.3.2
Prepare 1.3.2
2 participants
@Slach @DipalPrajapati