Cloudron Forum

We now have a working LibreChat cloudron container set up. See: https://forum.cloudron.io/topic/12850/first-try-app-packaging-librechat-issue-with-postgresql-extention-pgvector/14?_=1749416165430

I have a working setup, based on @Valexico 's work here:

https://github.com/canadaduane/librechat-cloudron

The package has been updated to the latest version of LibreChat 0.7.8, and I fixed a few minor wrinkles such as OIDC login, write access to the public dir, and postgres support. I haven't yet tested it with all of the providers (this requires access keys in the .env file).

@firmansi Thanks! This worked. It would be better if the URL need not be configured inside the app, but just wanted to note that the solution/workaround is ok.

I have the same experience as @firmansi and can no longer log in. @nebulon

This is awesome progress @Valexico! Did pgvector make it in to the base Cloudron release, and were you able to then connect LibreChat's DB up?

BTW I'm very interested in this right now because Open WebUI (the only chat frontend currently supported by Cloudrain AFAIU) recently changed their license to something that is no longer open source (by OSI definition).

Open WebUI has changed their license to a not-strictly-open-source license (by OSI definition):

https://docs.openwebui.com/license/

https://www.reddit.com/r/LocalLLaMA/comments/1kg4avg/openwebui_license_change_red_flag/

I just noticed they have mattermost integration! From the .env.example file:

# Mattermost Integration
MATTERMOST_ENABLED=false                          # Enable Mattermost (true|false)
MATTERMOST_SERVER_URL=YourMattermostServerUrl     # Mattermost server URL
MATTERMOST_USERNAME=YourMattermostUsername        # Mattermost username
MATTERMOST_PASSWORD=YourMattermostPassword        # Mattermost password
MATTERMOST_TOKEN=YourMattermostToken              # Mattermost slash command token
MATTERMOST_COMMAND_NAME=/sfu                      # Mattermost command name
MATTERMOST_DEFAULT_MESSAGE=Here is your meeting room: # Mattermost default message

Coming from a Slack-at-work setup with huddles (video meetings) this is really cool.

Cloudron support mentioned here (but not implemented at time of writing):

https://github.com/activepieces/activepieces/issues/1277

Does PocketBase fill that gap?

PocketBase is interesting, but I wouldn't reach for it first for core application state. Postgres is "boring technology" which is great for reliability, well-known, well-understood etc. That said, I'm sure PocketBase fills an important niche.

Would love to see this. Self-hosted database makes n8n much more powerful.

It's been several months (perhaps more than a year) since I tried logging in to my Ghost installation. When I tried to log in, however, it didn't seem to recognize my email. A pop-up said, "No member exists with this e-mail address. Please sign up first."

When I logged in via MySQL I could tell that the email exists in the users table. In fact, it was the only user. However, it still didn't seem to recognize the email.

It turned out that I needed to add "/ghost" to the URL to log in to the Ghost backend. I had forgotten that there is a "member" login for email sign-ups, and the member login is the visible "sign in" button on the typical landing page.

I hope this helps someone else!

I'm having trouble with this as well. Our peertube didn't make the upgrade and is in a restart loop. Running npm run plugin:install -- -n peertube-plugin-auth-openid-connect -v 0.1.1 as cloudron user in recovery mode yields these errors:

err: Error: Command failed: yarn add peertube-plugin-auth-openid-connect@0.1.1
error /app/data/storage/plugins/node_modules/ffi-napi: Command failed.
...
/app/data/storage/plugins/node_modules/get-uv-event-loop-napi-h/include/get-uv-event-loop-napi.h:26:30: error: invalid conversion from ‘napi_status (*)(node_api_nogc_env, uv_loop_s**)’ {aka ‘napi_status (*)(const napi_env__*, uv_loop_s**)’} to ‘get_uv_event_loop_fn’ {aka ‘napi_status (*)(napi_env__*, uv_loop_s**)’} [-fpermissive]
   26 |   napi_get_uv_event_loop__ = &napi_get_uv_event_loop;
      |                              ^~~~~~~~~~~~~~~~~~~~~~~
      |                              |
      |                              napi_status (*)(node_api_nogc_env, uv_loop_s**) {aka napi_status (*)(const napi_env__*, uv_loop_s**)}
...
error: Cannot install plugin peertube-plugin-auth-openid-connect, removing it...

EDIT: In case the build info is useful:

gyp info using node-gyp@10.1.0
gyp info using node@20.15.1 | linux | x64
gyp info find Python using Python version 3.10.12 found at "/usr/bin/python3"

gyp info spawn /usr/bin/python3
gyp info spawn args [
gyp info spawn args '/usr/local/node-20.15.1/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args 'binding.gyp',
gyp info spawn args '-f',
gyp info spawn args 'make',
gyp info spawn args '-I',
gyp info spawn args '/app/data/storage/plugins/node_modules/ffi-napi/build/config.gypi',
gyp info spawn args '-I',
gyp info spawn args '/usr/local/node-20.15.1/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args '-I',
gyp info spawn args '/home/cloudron/.cache/node-gyp/20.15.1/include/node/common.gypi',
gyp info spawn args '-Dlibrary=shared_library',
gyp info spawn args '-Dvisibility=default',
gyp info spawn args '-Dnode_root_dir=/home/cloudron/.cache/node-gyp/20.15.1',
gyp info spawn args '-Dnode_gyp_dir=/usr/local/node-20.15.1/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args '-Dnode_lib_file=/home/cloudron/.cache/node-gyp/20.15.1/<(target_arch)/node.lib',
gyp info spawn args '-Dmodule_root_dir=/app/data/storage/plugins/node_modules/ffi-napi',
gyp info spawn args '-Dnode_engine=v8',
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args 'build',
gyp info spawn args '-Goutput_dir=.'
gyp info spawn args ]

For the record, the resolution was that I had two accounts, one an admin and one a superadmin (both with a similar username). I believe that my logging into an app as the admin caused my current account in Cloudron to also become admin. This hid the "Configure" button in the Backup section--while admins can see the backup settings, only the superadmin can change them. Logging out of the admin account immediately gave me access to superadmin again.

@nebulon said in How to set up backups after "noop" selected?:

Maybe you could enable remote SSH support for us and send a mail to support@cloudron.io with the Cloudron details and we can check this directly.

Done, thanks.

BTW, for now, I have resorted to modifying the box db (settings table) directly in order to restore backup capability. The dropdown still does not show itself.

@nebulon No, none. There are a couple of warnings, but I don't think they are relevant:

While investigating this issue, I discovered a small bug in the "noop" code:

/home/yellowtent/box/src/backupformat/tgz.js:28

If you'll note, at line 28, fileType is not yet defined, and therefore throws an error.

Unfortunately, this does not fix my issue. The dropdown box is still missing.

I had an expensive backup bill and selected "noop" to prevent data from going to my backup provider (digital ocean).

Now, however, I can't seem to choose anything to get it back to a working backup state. There used to be a dropdown menu (which is how I selected "noop") but now there is just a text message.

How do I configure my cloudron instance to do backups again?

@nebulon This has been released!

https://vikunja.io/blog/2022/10/whats-new-in-vikunja-0.20.0/

I just noticed the image features landed a few days ago:

https://github.com/go-vikunja/frontend/commit/877e4250554b31db2d57f44a7443c5d04c783e59

https://github.com/go-vikunja/frontend/commit/3d88fdaaddca15b98efa938f0b2813420d56ad84

(they have not been included in the Vikunja release yet, however)