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

Using self-signed certificates on master and peer nodes prevents peers from joining cluster #773

Open
steeldomejeff opened this issue Jun 8, 2024 · 2 comments

Comments

@steeldomejeff
Copy link

Summary

Generating self-signed certificates on master and slaves prevents slaves from joining cluster when adding servers through the WebUI.

Message returned is:
Error: Failed to contact server: Error: Self-signed certificate.

Steps to reproduce the problem

Generate certs using openssl writing cert files to: /opt/cronicle/conf/ssl.key and /opt/cronicle/conf/ssl.crt

Your Setup

according to install instructions.

Operating system and version?

Rocky 9.4

Node.js version?

v20.14.0

Cronicle software version?

0.9.52

Are you using a multi-server setup, or just a single server?

Multi-server

Are you using the filesystem as back-end storage, or S3/Couchbase?

Local file systems storage

Log Excerpts

No log entries indicating an issue.

@steeldomejeff steeldomejeff changed the title Usig self-signed certificates on master and peer nodes prevents peers from joining cluster. Using self-signed certificates on master and peer nodes prevents peers from joining cluster. Jun 8, 2024
@steeldomejeff steeldomejeff changed the title Using self-signed certificates on master and peer nodes prevents peers from joining cluster. Using self-signed certificates on master and peer nodes prevents peers from joining cluster Jun 8, 2024
@jhuckaby
Copy link
Owner

jhuckaby commented Jun 9, 2024

I'm so sorry to say this, but Cronicle v0 doesn't support HTTPS / SSL. That is coming in v2 (out later this year).

Some people have hacked it to work, but only barely. Live Log Watching is a no go, and I have no idea how people are hacking multi-servers to communicate over HTTPS.

See previous issues on this topic:

You may have better luck with @mikeTWC1984's fork: https://github.com/cronicle-edge/cronicle-edge

@steeldomejeff
Copy link
Author

Thank you for the info... I removed the HttpForce parameter and it works now. I can't wait to see v2. Excellent job.

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

2 participants