Cloudron Forum

Another thing if you activate codebase memmory on repos the search with graphql is instant and sometimes I thought models are hallucinating even Fable 5.1. But it wasn’t the case, whole repo loaded and schemas loaded in ram and results are at least 4 times faster then normal windows based same tooling and usage as no overhead of windows filesystem nor Microsoft defender

i am using that its way better then DGX spark which i had to return as full of bugs this machine is way better with x86 architecture and come preloaded with most of the toys. i am using it with claude code beta and results are too good with local models as sub agents in docker as windows based OS are hitting limits and creating problems for some legacy php applications support

@girish its working thank you

https://forum.cloudron.io/post/128802
Offline
Package Updates
wrote about 13 hours ago
last edited by
#491
[4.40.0]

Update n8n to 2.36.8
Full Changelog
core: Allow a domain-restricted credential to work in its own node (#37248 )
API: Adapt binary data endpoint (#36994 )
API: Remove offset query param from list workflow history endpoint (#36952 )
core: Normalize env values before schema-based parsing (#36731 )
core: Avoid restarting task runners that are only slow (#36609 )
Google Ads Node: Migrate from sunset v21 API to v25 (#36255 )
core: Deprecate Array.merge from expressions, and add Array.mergeIntoObject (#36161 )
core: Make n8n User Auth (OAuth2) generally available (#35900 )
Schedule Trigger Node: Add "If Execution Is Missed" option (#35626 )
Discord Node: Add member moderation actions (#33486 )

this update is breaking the application

@umnz same thing happened with me i updated and n8n when into broken state i restarted and it worked

@umnz this is the exact reason i am looking for alternative and i narrow down to windmill but i am too clumsy to get started on it. i have almost 200 plus workflows

@umnz hi for me i didn't notice anything for me the bug was wait node which is firing properly. i am on

App title & version: n8n 2.17.7
Package version: io.n8n.cloudronapp@4.19.3
Installed: 3 years ago
Last updated: 2 days ago

@james this is resolved

https://forum.cloudron.io/post/123862

[4.19.1]

Update n8n to 2.17.5
Full Changelog
core: Enforce credential access checks in dynamic node parameter requests (#28861 ) (9aadc28 )
Alibaba Cloud Chat Model Node: Add credential-level url field for AI gateway compatibility (#28746 ) (60b61ef )
Make Wait node fully durable by removing in-memory execution path (#28574 ) (a4bdc80 )

i can confirm that the above version has fixed the wait node issue

Make Wait node fully durable by removing in-memory execution path (#28574 ) (a4bdc80 )

I think current release will solve that i will try to update in non production hours and let you guys know

@umnz you are rite i had to revert my 6 n8n instances on n8n 2.15.1 version..... at least i have backups and i disabled the auto updates for the time being

@Package-Updates please do not update yet as 2.16.1 has a bug as wait node does not work

upstream issue was already created by someone https://github.com/n8n-io/n8n/issues/28632

@james @joseph i found a potential issue. this only happen to Windows OS where microsoft ID is not connected and System only works with local account

@james please check my DM

@james do you want me to share a screen recording ? Or share any logs i have 4 cloudron instances and i faced the same. I use Dashlane for credential management all my passkeys stored in that

@james said:

Hello @dualoswinwiz
What Cloudron version are you currently using where this issue is present?

9.1.5

Subject: Passkey verification failed on desktop, login failure, and 2FA "Confirm" button disabled

@girish Hi, I updated to the latest version, but I'm unfortunately still running into issues with the Passkey feature. Here are the full details of what I'm experiencing across my devices, along with the relevant logs.

1. Initial Setup & Mobile Success:
   I successfully set up a passkey using the Dashlane app on iOS. The initial login worked perfectly, and the passkey login continues to work fine whenever I use that specific phone.

2. Desktop Login Issue & Fallback Failure:
   The next day, I tried to log in via the web on my Windows desktop PC using the passkey, but the login failed. I then tried to fall back to a standard password login. However, when I reached the 2FA screen, the "Confirm" button was greyed out/disabled, leaving me locked out on my PC.

3. Desktop Passkey Setup Error:
   Thinking I needed to reconfigure it, I tried to set up the passkey again directly from my Windows desktop using the Dashlane extension. When I do this, it throws an error stating: "passkey verification failed".

Troubleshooting I tried:

Tested across multiple desktop browsers (Firefox, Chrome, and Edge) — both the 2FA button issue and the setup error happen on all of them.

Double-checked my desktop's time and date settings to ensure everything was properly synced for 2FA.

My Workaround:
I ended up logging into Cloudron via my phone (where the passkey still functioned perfectly) and removed the passkey from my account entirely. Once the passkey was deleted, I was able to successfully log in on my desktop using my normal password + 2FA.

Logs:
I pulled the logs from when I attempted the setup on the desktop, and it looks like it's failing on the user verification step:

Plaintext
Mar 27 14:16:17 passkeys: getRegistrationOptions: generated for user uid-xxxxxxx-xxxx-46a5-80e5-d95d5451d588
Mar 27 14:16:19 passkeys: verifyRegistration: verification failed for user uid-xxxxxxx-xxxx-46a5-80e5-d95d5451d588: Error: User verification was required, but user could not be verified
Mar 27 14:16:19 at verifyRegistrationResponse (file:///home/yellowtent/box/node_modules/@simplewebauthn/server/esm/registration/verifyRegistrationResponse.js:119:15)
Mar 27 14:16:23 apphealthmonitor: app health: 10 running / 1 stopped / 1 unresponsive
Let me know if there's anything else I can test or provide to help track this down!

Please check my DM

@jypelle I am planning for Sovereign / Business license due to AES Secret encryption for credentials before purchasing can i apply that on a cloudron application instance?

When a user is disabled on the Cloudron user page, the disable icon does not appear. However, for any user who was disabled prior to version 9.x, the icon appeared as normal.

Cloudron version
9.0.17
Ubuntu version
Ubuntu 24.04.2 LTS Linux 6.8.0-101-generic