HTTPS container

The HTTPS version they offer is for machine-to-machine deployment, but it doesn’t work with Telegram or WhatsApp. With the n8n container, the installation and everything else needs to work directly with HTTPS.

How can I enable it automatically so that it activates automatically on ZimaOS and all containers?

It would also be fantastic if you could set the containers to update automatically, without having to update them manually.

If you have a feature request, please describe your reasoning here using the template. Thank you.

:point_down:

https://community.zimaspace.com/new-topic?category_id=32&tags=open

:point_up_2:

Would you?

Look forward to your reply.

I’ve already created the request, but how can we resolve this now?

Telegram requires a public HTTPS URL with a valid certificate. Local HTTP or self-signed HTTPS from ZimaOS won’t work as a webhook.

The easiest and cleanest solution is to run n8n behind a Cloudflare Tunnel (cloudflared) to provide a real HTTPS endpoint without port-forwarding.

For container updates, Watchtower can be used to automatically update running containers on a schedule.

This combination provides fully automatic HTTPS + secure external access + automatic container updates on ZimaOS without extra complexity or manual certificate management.

1 Like