[3.89.0]
Update n8n to 1.100.1
Full Changelog
Fix insights loading on FE (#16677) (99ce1d2)
Incorrect parameter names (#16408) (dd2ed90)
Add Dingbat emojis to expressions grammar (#16545) (ddd3908)
Ensure updatedAt field exists on folder object for source control (#16437) (81dd215)
Fix module path resolution for Docker (#16623) (b5ba655)
Fix pdf extract for arm64 docker images (#16522) (20e2d8e)
Fix pdf extract not working (#16463) (c480d3c)
Handle dynamic webhook edge cases (#16554) (1573ae6)
Incorrect data returned by the node when using retry on error + continue on error (#16516) (f598b3b)
Prevent unauthorised workflow termination (#16405) (29752ea)
@Ian4life yes, only one of the manifest or appStoreId has to be provided. The docs are slightly wrong. Try something like:
'{"appStoreId":"io.n8n.cloudronapp@3.87.0", "skipBackup": true, "force": false}' (The appStoreId also requires the version)
NM, I just read the docs and it says production doesn't display data like with test. It's in the executions only.
https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.webhook/?utm_source=n8n_app&utm_medium=node_settings_modal-credential_link&utm_campaign=n8n-nodes-base.webhook#webhook-urls
Just chiming in here because I ran into a CORS error as well. Solution was not a missing env var, it was activating the workflow - because without that, the URL didn't exist yet and threw the various errors.
I posted this in the evening and in bed that night I remembered that I hadn't even looked at the documentary (where it was demonstrably described) - no joke.
Regarding your question: It might have helped if somewhere when creating the post - especionally in the support section (preferably BEFORE you hit the big send button), there had been another note about whether you had already looked at the documentation.
Hello @arta you can use the n8n cli to reset all users.
See: https://docs.n8n.io/hosting/cli-commands/#user-management
You can reset user management using the n8n CLI. This returns user management to its pre-setup state. It removes all user accounts.
Use this if you forget your password, and don't have SMTP set up to do password resets by email.
Go into the Cloudron n8n web terminal and run:
gosu cloudron /app/code/node_modules/.bin/n8n user-management:reset
Hope this solves your problem
Yes, I've been doing this for years, you just have to make /app/data friendly enough for apps to find what they need. This generally involves setting a few env variables:
HOME
PATH (including NODE_PATH avoiding npm i -g)
LD_LIBRARY_PATH (less common)
other app specific ENVs
All of these changes do not affect the running app since it's already running with its own ENVs.
So these are great for additional services.
Nice work @djxx
@basiliolp the forum search is a powerfull tool
Welcome to the Cloudron Forum
https://forum.cloudron.io/topic/13654/could-not-connect-to-your-mcp-server/
@ValueShopperUSA This appears to be the SaaS version where you are on Trial plan.
I think you need the self-hosted version (like on Cloudron) for this to work.
@BrutalBirdie said in I turned off cloudron and turned it on again and my workflows disappeared and now I can no longer use n8n:
if we continue in spanish
wow - cloudron forum knows no bounds
In order to help you, please provide app logs and as much other information as possible. Which credentials are you referring to and also where is the logo replaced? In the Cloudron dashboard or somewhere else?
You can often install things to the /app/data location manually if you can set the right env variables.
try:
export HOME=/app/data
then run the pip install
