New version notifications not working

Describe the problem/error/question

I noticed that I stopped getting new version notifications. I have N8N_VERSION_NOTIFICATIONS_ENABLED and N8N_VERSION_NOTIFICATIONS_ENDPOINT set to the defaults, but I notice this:

GET /versions/ HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
User-Agent: HTTPie/3.2.2

HTTP/1.1 404 Not Found
    "data": null,
    "error": {
        "details": {},
        "message": "Not Found",
        "name": "NotFoundError",
        "status": 404

So, it looks to me like n8n’s version checking feature has become unavailable?

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Welcome to the community @man8 !

We had some issues recently, and a user opened the following two GitHub issues, which got resolved in the meantime:

One issue was with the endpoint. But I do not know if we ever supported the generic parent one, rather is the current version part of the path, and the endpoint returns then all the versions that have been released since. So, for example:

What version are you on? The second issue got resolved in [email protected]

1 Like

Hi @jan, happy 2024 :slight_smile:

Thank you - I searched for forum posts on this but clearly didn’t check GH issues properly.

I was indeed running [email protected] and not getting notifications of new versions, then while investigating my own appearance of N8n schedules never run, under any configuration, I realised that there have been several updates since.

I upgraded to [email protected], so I’ll still be affected by but I’ll wait for the next mainstream release before upgrading. I’ve thrown together a quick workflow for notifying me of new mainstream releases, as an interim workaround.

Ah yes, sorry. I did not meant to say you should also have looked on GitHub, but rather for your and other people’s information that see problems.

Because of Christmas & New Year we are sadly a little bit slower right now with releasing new versions and setting them to stable. But great to hear that you found a workaround.

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