Cloudron Forum

Nicely detailed docs here - https://www.axigen.com/documentation/axigen-auto-discovery-p49119962

@perler Have you seen https://docs.cloudron.io/apps/#cron already? This will run the job in the context of a container.

I am happy to add other "meta" patterns, if none of those fit your use case 🙂

@nebulon I was maybe not clear enough, the feature request is for sending out an HTTP request when a backup is successful, not reacting to an API request.

@perler said in support "featured" nextcloud apps:

I think as @WiseMetalhead that these featured apps are fairly stable

In fact, I've been using a fairly large set of apps (Music, Notes, Tasks, Calendar, Forms, etc.) for about a year now, but haven't experienced any problems, including major updates. But it's worth mentioning that all of this is far from a statistic, and maybe I'm just lucky 🙂

Regarding a helping hand for autodns:

acme.sh does support dnsapi cert generation for autodns maybe this code can help developing.
https://github.com/acmesh-official/acme.sh/blob/master/dnsapi/dns_autodns.sh

Also acme.sh has MANY more dnsapi supports:
https://github.com/acmesh-official/acme.sh/tree/master/dnsapi

@perler Wow, that is a very good catch!
The kind of; "huh, why have I not thought about this one before, yet it seems obvious"... As you say it, the idea comes from an instant need once in front of a specific situation which requires a solution that no one seems to have a previous need.

And while reading how you describe it, in pops in mind like; "yeah, that would be master piece to be able to restore the files only, in an app as Nextcloud". So true.

There could be others apps as well, but at first thought NC is the very first candidate for such desirable feature, because of the very nature of the app which holds files, and potentially team communications and email boxes as well. And this is where we can see that restoring the whole pack at once, especially for a well active NC app, could produce unexpected outcomes. Depending of course on how the app is used inside an organization.

I don't think it would be a required feature for all apps. But then, if it's easier to implement as a general backup feature then why not. I would vote for this.

Thanks for the heads-up.

@robi me stupid. I had two entries with allow_admin_panel, one was "On", one was "Off" 🙄

Yes, as far as I understand each Nextcloud would initiate a document edit session with its own document URL and token exchange, so those should be isolated from one another.

@girish done

@jdaviescoates said in dynamic ip - TTL/manual update?:

Never really got why so many people use Cloudflare, mostly seems to just add complications and break things, and contributes to massive centralisation of the internet

I'm using their DNS proxying to hide my home server IP address. I don't know of any alternatives. Especially one that has DNS proxying AND is already added to Cloudron (for automating DNS).

The solution is here:

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

@staff ought to update the docs to make it clearer

after enabling the admin panel you have to visit /?admin in order for the admin_password.txt file to be created

the admin username is admin

As @jdaviescoates said, we force small case for compatibility. I understand that in your specific context that being case sensitive might work though.

LDAP itself has a bunch of case sensitivity madness. See https://stackoverflow.com/questions/29897684/is-ldap-dn-case-insensitive and https://www.ibm.com/docs/en/oala/1.3.5?topic=SSPFMY_1.3.5/com.ibm.scala.doc/install/iwa_pinst_ldap_cnf_cse_sen_t.html . I remember we tried to make this case preserving but this causes lots of subtle very hard to debug failures.

There's a lot of things in play here 🙂 File systems, databases, frameworks, languages... each has their own level of case sensitivity support when it comes to usernames.

@fbartels ok, this makes sense, thanks!

@girish I did something slightly different (but maybe not SO uncommon). I created the server and put the clients domain into my own (developer) cloudflare account. After everything worked I created the domain in the client's cloudflare account and changed the NS entries (basically this: https://developers.cloudflare.com/fundamentals/get-started/basic-tasks/manage-domains/move-domain/).

the situation was now, that the API key was still valid but changed the wrong domain entries at cloudflare. so, I imagine cloudron creates the NS entry, checks if this works (which it doesn't) -> brain freeze. Something like this?

@girish ok, this was my mistake, I changed the cloudron admin name here in the forum for privacy reasons and then tried to use this name back on the server 🙄

@nebulon can you maybe have a look into the other thread, I am a bit stuck but it would be important to get this right for a porject of mine.

@perler We replied from support@ now, can you please check?

For future reference, the approach is:

Login to cloudron.io with your old account. Delete the cloudron instance there. This will disassociate your existing Cloudron from cloudron.io

Then, go to your Cloudron dashboard. If you refresh the page and go to Appstore view, it will ask you to relogin. Just relogin with your new cloudron.io account.

If your new account has a license, it will automatically get reassociated. If this doesn't, please send us a note on support@ and we can fix it up.

@murgero ah thanks, pushed a fix. Both nextcloud and collabora links were broken.