jhuckaby
commented
3 months ago 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:
- https://github.com/jhuckaby/Cronicle/issues/456
- https://github.com/jhuckaby/Cronicle/issues/723
- https://github.com/jhuckaby/Cronicle/issues/27
You may have better luck with @mikeTWC1984's fork: https://github.com/cronicle-edge/cronicle-edge
steeldomejeff
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.