Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: [N8N] Timezone not being followed #4603

Open
dsfdev opened this issue Dec 16, 2024 · 0 comments · May be fixed by #4598
Open

[Bug]: [N8N] Timezone not being followed #4603

dsfdev opened this issue Dec 16, 2024 · 0 comments · May be fixed by #4598
Labels
🐞 Confirmed Bug Verified issues that have been reproduced by the team.

Comments

@dsfdev
Copy link

dsfdev commented Dec 16, 2024

Error Message and Logs

I have n8n app running, tried both n8n & n8n with postgres, and the timezone inside the app does not appear to be set to what i want.

I have set environment variables to Europe/London in the docker config and all across Coolify along with the server (which is Hetzner Germany) but both n8n apps report the timezone as Europe/Berlin.

I have n8n running on another Hetzner server in the same DC with not timezones changed (server showing as UTC) but I have set the timezone inside the docker config to Europe/London and it appears inside n8n as Europe/London as expected.

There must be something going on with the Coolify app / integration / implementation where it is either not passing in the environment variables from the apps into the containers or it is being overwritten somewhere along the way.

I have not tried Coolify in another DC in another location as yet. The default n8n timezone is America/New York so n8n cannot be using the defaults. It is being changed somewhere along the way to Europe/Berlin ( in my instance at the mo)

Steps to Reproduce

  1. Add n8n app in Coolify, either with or without postgres
  2. Set GENERIC_TIMEZONE & TZ environment variables to Europe/London
  3. Start n8n
  4. Add a schedule node to a workflow and test
  5. Check to see if timezone equals what should be set as GENERIC_TIMEZONE & TZ environment variables.
  6. In my case it is Europe/Berlin always (possible due to server location, even though server TZ is set to Europe/London too)

Example Repository URL

No response

Coolify Version

v4.0.0-beta.379

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04.1 LTS

Additional Information

No response

@dsfdev dsfdev added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Dec 16, 2024
@github-actions github-actions bot removed 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Dec 19, 2024
@peaklabs-dev peaklabs-dev added the 🐞 Confirmed Bug Verified issues that have been reproduced by the team. label Dec 19, 2024
@peaklabs-dev peaklabs-dev added this to the v4.0.0 Stable Release milestone Dec 19, 2024
@peaklabs-dev peaklabs-dev linked a pull request Dec 19, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 Confirmed Bug Verified issues that have been reproduced by the team.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants