Please tag 1.30.0 as latest (if possible)

[systemaddict]

This bug is pretty critical. I see that it has been fixed in 1.30 but we can’t update (on Cloudron) because it’s tagged latest:

SOLVED: HTTP reqest node Zoom - ERROR: write EPROTO

Describe the problem/error/question After n8n Update i have error on a Zoom when in HTTP request node Follow redirect needed to get Zoom record Binary Data Ignore SSL - not fix the problem 1.22 works fine [Image 3622] [Image 3623] Newer HTTP request node - not fix, the problem still persist What is the error message (if any)? ERROR: write EPROTO 680BA26D9C7F0000:error:0A000410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:…/deps/openssl/openssl/ssl/record/rec_layer_s3.c:159…

[n8n]

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:

[systemaddict]

I realize that this version might be far from release ready, so I’ve just downgraded instead.

[Jon]

Hey @systemaddict,

Does Cloudron not allow you to input a release version manually?

[girishcloudron]

Hi, Cloudron founder here. We only package the latest stable releases. As of right now, this seems to be 1.29.1 per Release [email protected] · n8n-io/n8n · GitHub

[Jon]

Hey @girishcloudron,

It looks like 1.30.0 wasn’t tagged as it was not considered stable enough so the new release from today has been marked as latest.

Are users not able to select their own release so they can change between versions if there is a bug?

[systemaddict]

I don’t think that is possible (at least not easily). It’s really really easy to revert to a previous version though. But it would be nice to manually input a version in these (rare) cases.

I think a lot of users of N8N are using it through Cloudron (which is a fantastic platform).

[girishcloudron]

@Jon thanks! Already published 1.31.1. As @systemaddict said , it is not possible (currently) to run arbitrary version of n8n . We build our docker images pinned with a specific n8n version for predictability. Thanks again for the quick turnaround.

[Jon]

I know we do have a handful of users using Cloudron and similar tools like Coolify not sure which is most popular but for us we don’t officially support them.

In this case though we will only tag something as lastest if we are happy with how stable it is so if it does have a fix you need you would need to be able to manually set the version.