Closed xme closed 5 years ago
It seems that sometimes the CertStream WebSocket service send FIN+PSH packet, this generates the "Error connecting to CertStream - Connection is already closed. - Sleeping for a few seconds and trying again..." message. The socket reconnect automatically after that.
Hi @xme , due to this code update (https://github.com/AssuranceMaladieSec/CertStreamMonitor/issues/13 ) we operate now our own CertStream server instance (in a docker) based on https://github.com/CaliDog/certstream-server . We have a far better stability of the connections to this engine than to the Calidog Security engine behind Cloudflare.
The option in the config file to point to your Certificate Transparency Aggregator server is : ACTServer. The format is : ACTServer = wss://hostname (Hostname under a FQDN format).
Tx for the followup. I just rebuild my new container with the newest code.
I'm running the tool in a Docker (standard docker-compose/dockerfile). I detected regular timeouts to the CertStream service: