Cloudron Forum

Currently, tika ia only part of the mail server but we can make it a service/addon - https://docs.openwebui.com/tutorials/integrations/apachetika/

There is an initial package at https://git.cloudron.io/cloudron/owntracks-app . It will get published eventually .

@jdaviescoates said in Nextcloud OIDC integration:

I wonder if @staff could rename the provider to something more generic like "Open ID Connect" or "OIDC"?

Those terms are just generic technology terms. One should always have "Login with <provider>" . Like Login with gmail, Login with Github etc. Login with OIDC doesn't actually mean anything (unless it's providing some dropdown of providers after clicking the button). I think we should open a bug report upstream, seems easy to fix

@umnz it opens a new tab for me . Which browser are you using?

@q__nt_n we are looking into implementing this for the next release as part of 8.1 .https://forum.cloudron.io/topic/9975/what-s-coming-in-8-1 . As for the API, indeed, it seems to be missed in the API docs. But you can just call /api/v1/apps/<appid>/backup POST . This will return a taskId to track as well (similar to other API calls).

LDAP uses a custom port and won't be compatible with Cloudflare. Cloudflare only proxies HTTP. OIDC should be compatible with Cloudflare though .

@simon might be worth reporting upstream . Closest I found similar to your issue is https://github.com/louislam/uptime-kuma/issues/3276

I guess you are on an internal network? If so, port 40000 has to be port forwarded as well. On a public network, you have to make sure 40000 is open in any Cloud firewall.

The Cloudflare warning exists because Cloudflare only forwards http (port 80, 443).

@hpz24 said in Best practice for migrating apps from one Cloudron to another?:

Now I'm curious: does an app actually survive the move to another cloudron instance with a different domain?

In most apps, yes. The federated apps like mastodon and matrix are a special case. They don't support changing the domain . Even though the app itself will work after changing the domain, expect bad things to happen (tm) after domain change. For example, not seeing proper history of old message etc. I haven't tried this much, so this is just a warning really.

There's no uninstall procedure as such since the installation script doesn't keep a copy of all the things it changes. It's best to just reimage ubuntu.

Cloudron is developed like a platform/OS and it touches everything - docker, nginx, dns configuration, systemd services, iptables, nodejs etc.

@AartJansen said in Email sending broken after updating to 8.2.x (due to IPv6 issues):

So with a self hosted install I would need to ask the ISP to set up the ipv6 PTR like they ip4 record ?

yes

The syncthing user runs as "cloudron" user which is uid 1000 in docker base image. https://git.cloudron.io/cloudron/syncthing-app/-/blob/master/supervisor/syncthing.conf?ref_type=heads#L7 . Does the volume have permissions for uid 1000 ? You might have to adjust permissions via SSH for this.

I haven't tried it but in theory, you can just clone the app and run inside some /app/data/whiteboard of nextcloud . Run the app itself as a cron service - https://docs.cloudron.io/apps/#cron

Alternately, please make an app request

@umnz the basic idea would be to use the clone or the import functionality .

• Install WP. Configure it as needed. This is your base instance
• Take a backup of the app.
• Stop this app.
• When you want a new install, clone from the backup

You can always start the app again and update your base template.

Another idea is that you can use the new archive feature to archive the base app and then "restore" to create new app instances.

@andreasdueren if we take that error at face value, it's unable to connect to my.domain.com . Can you check from web terminal of nextcloud, if you are able to curl https://my.domain.com/.well-known/openid-configuration ?

Also, do other oidc apps work?

@firmansi the auth mechanism is chosen at install time. if you go behind cloudron's back and make changes to the app configuration, this will eventually not work. in your situation, you have installation nextcloud without LDAP/OIDC and then later configuring it inside the app manually. This won't work and is not supported. The way to fix this is like this:

• take backup of your nextcloud. download the backup configuration of this new backup
• install new nextcloud with cloudron user management
• import the backup from setup 1 . app -> backups -> import

It will work after this.

This is in our TODO list. I think currently the latest Leantime does not work on Cloudron which we are fixing first.

@igaudette I would go about the importing like this:

• Install a fresh NocoDB on Cloudron. Make sure the version of NocoDB on Cloudron PikaPods matches!

• Then, upload and import the db dump from PikaPods into Cloudron. See https://docs.cloudron.io/guides/import-postgresql/ on how to do this .

• If you had set up some custom configuration from https://docs.nocodb.com/getting-started/installation/#environment-variables in pika pods, then you have to put those in Cloudron in /app/data/env using File manager .

Let us know how it goes!

This was sorted out on support. Discourse has a database table called javascript_caches which holds on to some old theme assets. Just removing the entries in that table makes the site load again.

I got this hint from various threads.

• I think this was a bug in some old releases. https://github.com/discourse/discourse/pull/16669 is the fix upstream
• https://meta.discourse.org/t/uncaught-in-promise-error-could-not-find-module-discourse-widgets-search-menu-imported-from-discourse-theme-70-widgets-search-banner/300297 is the browser error
• https://meta.discourse.org/t/using-safe-mode-to-troubleshoot-issues-with-themes-and-plugins/53504 (there is a /?safe_mode=no_themes,no_plugins )

@krumel yes. new installations on noble will work.