My A/V threw a wobbly this morning, seems there is some callback to public.n8n.cloud when using the self-hosted version that has an expired certificate. Might want to have a look at this.
Hi @RedPacketSec, I am so sorry for this. Looks like we overlooked something here 
The team is currently looking into this. This subdomain would be used for telemetry, so it shouldn’t impact n8n’s core functionality.
Ah, my Bitdefender is also crying about it.
Hope it resolved soon. would otherwise be a very annoying day of Bitdefender complaining. 
