Cloudron Forum

I reproduced the issue. The issue seems to be that in old installations that started before the stable package, the email is not marked as verified. The API calls are failing with the error that email is not verified. To fix:

• Open a web terminal and click on the Postgres button on the top
• Then, run below. The email has to be replaced with the email in your linkwarden settings page:

UPDATE "User" SET "emailVerified"='2024-09-17 14:53:36.194' WHERE email='email@example.com';

That's it. Refresh linkwarden and things reappear.

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

Absolutely. I had the same gripe and reported it to the team. This will be fixed soonish.

I am active there . r/selfhosted is self hosting enthusiasts and tinkerers. There was a survey a while ago about the users and a veyr big chunk was mostly people trying to learn devops/k8s and it doesn't matter if thigns break and you have to start over. Given the personal and education use space, it has a bias for "free" as in beer stuff. Nothing wrong with all this, just giving some context around that sub . It's a great sub for discovering new projects and getting some tips here and there (off late, the technical users have dried up a lot though) . Depending on the mood of the day, you might even get downvoted if suggesting using a VPS btw It's because they are much in the homelab and hosting with laptops on a private lan .

An anomaly in all this is that they are vehemently against selfhosting email (you can search for various threads)

@timconsidine Our condolences from the Cloudron team, sorry for your loss.

Can probably run as a normal user here - https://git.cloudron.io/timconsidine/cloudron-memorial/-/blob/main/start.sh?ref_type=heads#L35 . (as in, exec gosu cloudron:cloudron node.js app)

@baris thanks !

chat is re-enabled now. For those who don't want it , there is a setting in the profile:

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

The tika error seems to be because tika was down . I think a UI button to rebuild index will help a lot.

@canadaduane thanks for the heads up . https://docs.openwebui.com/license/#open-webui-license-explained has an ELI5 of sorts

@avatar1024 said in Email search not working properly:

What's tika?

tika is this - https://tika.apache.org/ . it converts the pdf/docs attachments in emails to text to make them searchable

@charlesnw I think the best approach is to do a restore yourself to understand how it all works . See https://docs.cloudron.io/backups/#restore-cloudron .

For backup frequency, see https://docs.cloudron.io/backups/#schedule

To overall explain backups:

Cloudron Backup = Box backup + Email backup + App backups

The box backup has many things including users, domains, profiles, settings, apps installed, backup i.e everything you do in the dashboard . Email backup is the emails (just that) . App backups is each app backed up separately. Together, all these backups form a single Cloudron backup.

We are yet to hit a situation to restore user database separately. Not sure why this is needed but you can restore the full cloudron from Cloudron backup if your server hard disk crashes . You can also restore individual apps. This is needed often when an app update went wrong.

There is no UI to restore an individual email account. Not sure why this is needed (can someone even delete all their emails by "accident" ?) But you can just copy that single mailbox from the email backup into the live cloudron instance to restore. There is no magic here, you can just open the backups and see what's inside them.

@robi I investigated this. There was a blob like this in .bashrc - https://paste.cloudron.io/zunuqadabi.lua and the ps output had a lot of sus things - https://paste.cloudron.io/xajicujoxe.apache . With some luck , I found that /etc/ld.so.conf had a preload of libprocesshider.so inside it

@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

When you find some time, we can also put this into the community guides - https://docs.cloudron.io/guides/community/

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

Librechat got acquired - https://clickhouse.com/blog/librechat-open-source-agentic-data-stack . Incoming ....

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).

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

The last time I brought this up, the idea was to bring to the list view (but not Grid view). Especially updating multiple apps is a pain if you are updating manually.

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