Replies: 1 comment 4 replies
-
I'm terribly sorry to say this, but Cronicle v1 doesn't support HTTPS. Several people have hacked it to sort of make it sort of work, but live log watching is a no-go, because it opens a secondary web socket directly to the worker server. The good news is, this is all fixed in Cronicle v2, which is coming this year (2024). Unfortunately it would be way too much work to backport full HTTPS support into v1. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
Need to create a custom domain in apache2 and in port 3013 which with ssl, and I update the config.json
here I am able to access the landing page but couldn't connect to web socket, in web socket it should take hostname, but it is taking sever username and I could not figure out why it is happening could you please help me with this.
Thank you!
Operating system and version?
Ubuntu 22
Node.js version?
V22
Cronicle software version?
Latest
Are you using a multi-server setup, or just a single server?
Single server
Are you using the filesystem as back-end storage, or S3/Couchbase?
Couchbase
Beta Was this translation helpful? Give feedback.
All reactions