Sudden “connection timed out” issues on n8n (Cloudron on Hostinger VPS) since Sept 9

[alexftth]

Hello everyone,

Since September 9th, all my n8n automations hosted on a Hostinger VPS with Cloudron started to hang for several minutes and then fail with:

"The connection timed out"

This happens on:

API calls to Teamtailor (previously worked fine for months),

API calls to Google Drive (same issue).

Key points:

My setup had been running smoothly for over 2 months.

On Sept 9th, both my n8n apps started failing simultaneously.

Tests inside the container show:

curl -6 https://api.teamtailor.com → host cannot be resolved (IPv6 fails).

curl -4 and node -e https.get(...) → immediate response over IPv4 (expected 404).

I added the environment variable NODE_OPTIONS=--dns-result-order=ipv4first and restarted containers.

Confirmed with printenv → variable is applied.

However, workflows in the n8n UI still hang for ~10 minutes before timing out.

Hostinger support says:

They cannot intervene directly (self-managed VPS),

Suggested disabling IPv6 at VPS level or restoring a backup from before Sept 9.

My questions:

Has anyone else on Cloudron/n8n experienced similar issues since Sept 9 (especially related to IPv6)?

Is it safe/recommended to fully disable IPv6 on the VPS (via sysctl) to force IPv4 only?

Could a recent update of Cloudron/n8n explain this behavior (workflows waiting on IPv6 instead of quickly switching to IPv4)?

Any feedback or advice would be greatly appreciated

[james]

Hello @alexftth and welcome to the Cloudron forum

Some questions so we can bet a better picture.

• Did any app updates happen in the timeframe of this issue arising
• Did you restart the server since then? If no, please restart the server once

When restarted, please ssh into your server and as root run:

cloudron-support --troubleshoot

Check if it is working now. If not, share the output of this command and also run:

cloudron-support --send-diagnostics

This will generate a URL with details about your server, share this URL with us here as well. (this also includes IPs and DNS names, if you don't wish to post this publicly, send this with a DM to me)

Also re-run the commands you used inside the container and run them from root.