I have found the way to enable the chat hub, just go to filemanager in Cloudron, open env.sh file and add this "export N8N_ENABLED_MODULES=chat-hub" and you will see the chat module in left sidebar
firmansi
Posts
-
Announcing n8n version 2.0 - coming soon! -
Announcing n8n version 2.0 - coming soon!I already upgraded n8n to the latest version, it went smooth and no significant issues, but one feature that i look for n8n chat hub dont appear in this upgrade,anyone experience differently than mine?
-
Announcing n8n version 2.0 - coming soon!Is there any update regarding to this major next update?I see in Cloudron git the update is already started but remain on hold
-
Cloudflare Zero Trust Issue with Cloudron OpenIDIt works now
-
Cloudflare Zero Trust Issue with Cloudron OpenIDI have tried the best I can according to Cloudron documentation when setting up Cloudron OpenID with Cloudflare Zero Trust, even I delete and create new Client ID but always i got this message
"Failed to verify oidc token with fresh keys
undefined"What Should I do ?
-
Cloudron install but many services stop working on alibaba serverhai @guacadmin , are you using ubuntu in Alibabacloud?
-
Cloudron 9.0 (beta) bug reports@nebulon I’ve actually suggested this before: what if cloudron team added a field so that Cloudron admins like me could include a link or instructions for users on how to reset their LDAP password at the location where their user data is stored? I assume not everyone using Cloudron uses Cloudron itself as their LDAP server—some may use a separate external LDAP server. While adding an extra API to trigger password changes or resets on the external LDAP server is indeed a good idea, it might take some time to implement. So, I was just thinking of a more practical, immediate solution: letting each admin using Cloudron take responsibility for providing their own reset link or instructions.
-
Cloudron 9.0 (beta) bug reports@girish awesome, i believe this will be included in next update.
-
Cloudron 9.0 (beta) bug reports@jdaviescoates thanks for the citation, yes i refer to that. So, I’ve already upgraded to the latest Cloudron version, 9.07. Now, Cloudron A pulls its user data from Cloudron B via LDAP. I tested the password reset function on Cloudron A by clicking “Reset Password.” After clicking, the password reset window did open as expected. However, after entering the email and clicking the reset button, I never received the password reset email—even though the interface displayed a success message stating that the email had been sent.
Previously, in Cloudron version 8, when I clicked the “Reset Password” button for a user authenticated via LDAP, the system correctly responded with an error message indicating that the user’s authentication source is external (e.g., “The authentication provider for this user is not managed by this Cloudron instance”). Now, in version 9.07, that check seems to be missing or bypassed—instead of rejecting the request early, it proceeds and falsely reports success, even though no email is actually sent.
-
Cloudron 9.0 (beta) bug reports@nebulon Please don't forget bugs in reset password for LDAP sign in too yah
-
Cloudron 9.0 (beta) bug reports@nebulon I’m still encountering an issue with the latest Cloudron update: when I try to reset a password for a user who actually resides on Server B (connected to—let’s say—Server A, where I’m attempting the password reset via LDAP), the reset process appears to succeed, and I get a notification stating that the password will be sent to the user. However, after waiting for a long time, the email never arrives.
-
What's coming in Cloudron 9I also experience the same like only two servers can be updated, and otherhs dont get update when i click check update button
-
N8N - Unlock Paid Features for Free!! - TIME LIMITED OFFERJust hoping that N8N wont end up like Minio case, it really sucks
-
Ollama is now availableEventhough it's out of context of this thread but i see that the Cloudron team already start the detachment process of Ollama and OpenWebui
-
Ollama is now availableFinally...hopefully it can be detached with openwebui in next update
-
Connecting Cloudron Nextcloud to Cloudr CollaboraMy comment to this thread maybe out of context, but as your information, I have tried for the last 1 year till today, Collabora as Nextcloud Office with Nextcloud Community Edition ,since I have no idea how good Collabora running on NC Enterprise Edition, is not reliable, i've been using onlyoffice and seems onlyoffice is much mature in stability and reliability especially running with NC Community Edition
-
Nextcloud update pushed too early?So far I have no issues as mentioned above with latest update, my stack running with onlyoffice, nextcloud assistant, team folder, draw.io, groupware. My NC running with more than 100 users with Cloudron
-
Accessing Nextcloud App Store following 32.0.0 update@osobo I don't think it's possible to run this with Cloudron Docker unless you run it in dedicated machine without docker. It simply can't install docker on top of docker
-
Update OpenWebUI without Ollama@girish ya, i think this is a good approach because in real use case, I think most people prefer to run inference models not in the same machine with openWebUI instance. OpenWebUI is good enough bundled with chromadb , sql lite or postgressql database and redis as one package and the inference models (including ollama) running in different servers.
-
Update OpenWebUI without OllamaActually it is possible to have Open Webui without Ollama, but it means that there's gonna be two version of OpenWebui in Cloudron, one with Ollama and one without Ollama, and I am not sure this technique will be favourable by Cloudron team since it means the team should maintain two versions