Cloudron Forum

Is it possible to change theinterval through Cloudron CLI?

Hi everyone, 

I have a question regarding the Dynamic DNS feature and how it behaves after a server reboot/startup. 

My current workflow involves shutting down the server periodically to take a full image backup. When the server boots back up, my ISP assigns a new public IP. However, I’ve noticed that Cloudron doesn't seem to update the DNS for the apps immediately upon startup, leaving them offline. 

To work around this, I currently have to manually edit /etc/hosts just to access the dashboard and force things through. 

Furthermore, I checked the dashboard's Event Log and couldn't find any information or logs related to DNS updates or the DDNS cron job execution. This makes it very difficult to verify whether the Dynamic DNS feature is actually running or failing. 

Could you please clarify: 

1. What is the current default interval for Cloudron to check for public IP changes?
2. Is there a way to manually customize this interval or force a DDNS check immediately upon server startup?
3. Where can I find the actual backend logs for Dynamic DNS syncs since they don't appear in the dashboard's Event Log?

Thanks in advance for the help!

@james Well, looking at the logs, it’s actually running fine. Even though the UI dashboard looks stuck at 5%, I managed to successfully update it to version 10.0.5

I'm trying to upgrade my Cloudron instance from version 10.0.3 to 10.0.4.However, the update process has been running for over an hour now, but the progress is stuck and hasn't gone past 5%.

How can I check what is going wrong? Which log files should I look into to see the error, and what commands should I run via SSH to troubleshoot this?

Any help or guidance would be greatly appreciated. Thanks!

@james hai, is there any update regarding to this, is it doable with Cloudron?

@james is there any update if this possible in N8N package in Cloudron, there's also a new development in N8N that there's a feature called Agent, but I also don't see how this can be done in Cloudron

@robi already done that, that's why i asked the question about the Service URL and API Key, since what i understand from the documentation that if it's already included in the instalation then the service url and api key already there in written in .env, but if i have to add manually then what should i fill in the .env configuration

It got me a bit confused since the documentation mention that it's already included in recent version, then i assume that the service already up and running in cloudron n8n, but even it's not there yet in latest n8n cloudron update, please advise how we can do manually in terminal

With the recent n8n upgrade that introduces the n8n AI Assistant feature, I am looking to set it up on my Cloudron instance.

However, I am a bit confused about the required environment variables or configurations, specifically the Service URL and API Key for the AI Assistant.

Could anyone advise on the following:

• Is this AI Assistant service automatically deployed and configured within the Cloudron n8n Docker package?
• If not, what are the correct steps or environment variables needed to configure the Service URL and API Key manually in the Cloudron dashboard?

Any guidance or examples from anyone who has successfully set this up would be greatly appreciated!

Thanks in advance!

@james These days i use Cloudflare Zero trust to protect certain domains from public access, for example like in wordpress, I protect the access to wp admin with cloudflare, not some kind of vpn that need another private layer to connect with (as far as I know that how VPN Works)

I have been using N8N for years, and frankly never had once the webhook of N8N exposed to public on front end code, always use only in backend.

What you explain is really nice , but to my understanding of VPNs is that they require a client for access and introduce overhead, which can reduce overall connection speed

I think a proxy firewall solution is more interesting, like what Cloudflare does. But when I first saw the article about using another domain for webhooks, I thought it was similar to Typebot's setup, where the console and the chat window use different domains.

@james somehow, it's deemed as a preview, not a stable one, but the documentation can be found here

https://docs.n8n.io/build/ways-of-building-workflows/ai-assistant

@james it might be out of topic, but in the latest update, i don't see AI assistant preview in n8n Cloudron, is it missing from the latest cloudron update or any env configuration need to be added?

@james ya, i can still secure it using proxy that will lock away user accesing UI login from main sub domain

@LoudLemur Yes, i dont see it either in any update from the author

@andreasdueren well, i think that's not what i expect LOL, it's still unsecured

@james that means the alias domain still can expose main login domain for example my n8n domain is abc.domain.com and the alias domain is xyz.domain.com then if someone point to xyz.domain.com then it still can open n8n login directly too?

@robi What do you mean another webhook provider?

@james is there any plan to implement this?

@james Is there any ETA plan for this addition in Cloudron?

@james Yes, this feature is highly necessary for our use case rather than just a convenience.

To give you an example, it works similarly to Typebot, where the domain for development and backend management is kept separate from the public-facing chat interface.

We see a similar need in n8n. When we build public-facing features like n8n Chat or Forms, keeping them on the same domain as the workflow development console creates a major limitation. As long as they share the same URL on Cloudron, we cannot fully utilize these public features natively for our users; our only workaround right now is embedding them (as an iframe).

Having full secondary domain support would allow us to host the admin console on one domain while securely serving the public forms and chats on another