Certificate error on self hosted n8n, related to public.n8n.cloud

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 :see_no_evil:

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. :sweat_smile:

1 Like

public.n8n.cloud should now have a fresh certificate:

Sorry for the trouble everyone!

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.