RE: Log Watcher Error #117

[jamie-cw]

Thanks for the reply.

I do have https set to false but I get the same error. Could it be that the load balancer I am using is https and therefore the connection from client machine assumes https?

Another thing I noticed - if i connect to the UI on the local IP (http) the log watcher successfully connects back to the sever in http. However I see no output until the job completes running, so no live logging, have you seen this before?

Thanks for all your help.

Originally posted by @jamiecwong in https://github.com/jhuckaby/Cronicle/issues/117#issuecomment-423967142

[jhuckaby]

Could it be that the load balancer I am using is https and therefore the connection from client machine assumes https?

Ah yes, this is probably what is happening. I do apologize, but Cronicle really doesn't work well with HTTPS at all at this point. It's still in alpha really. I have an open issue to implement HTTPS properly, which is on the TODO list: https://github.com/jhuckaby/Cronicle/issues/27

Another thing I noticed - if i connect to the UI on the local IP (http) the log watcher successfully connects back to the sever in http. However I see no output until the job completes running, so no live logging, have you seen this before?

Yeah, there are lots of open issues related to the live log watcher feature. It currently tries to open a secondary websocket connection directly to the server running the job, and is highly problematic for many people. A TODO item is on the major roadmap to completely redesign this.

[mikeboiko]

I'm using caddy as an HTTPS reverse proxy for cronicle and I am experiencing the same error:

cronicle Log Watcher: Server Connect Error: Error: websocket error (https://192.168.0.246:3013)