Cloudron Forum

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)

Just FYI our company (relm.us) is sponsoring some new feature development in Vikunja that may help others here:

1. Image previews: when attaching an image-type file to a task, a thumbnail of the image will be visible (currently, only the filename/description is shown).
2. Cover image on kanban cards: you will be able to promote a kanban card's attached image to the "cover", so that you can see the image in "kanban" mode. This is similar to the way Trello does it.
3. The large "Vikunja" logo/branding in anonymous/read-only mode will be optional.

Vikunja's developer, Konrad, estimates these features will be ready by end of year (i.e. at the next release).

Best,
Duane Johnson
CEO/developer Relm.US

Most of our development team works with regular coding tools like vscode and git; however, some of us would like to work in a "live" environment with a collaborative coding editor like Cloud9 or Firepad.

Does anyone use any of the current Cloudron apps in this way? Any suggestions to try?

For example, does Gitea or Gogs enable a cloud-based edit & deploy cycle? Would EtherPad be suitable here (although, it seems unable to choose which files to collaborate on)?

Thanks!
Duane Johnson
CEO/Developer at Relm.us

@girish It works! Thank you.

Hello!

Is there a way to add environment variables or otherwise configure Uptime Kuma?

Specifically, a recent upstream change appears to have disabled the ability (by default) to embed Uptime Kuma in an iframe.

The solution for this particular issue appears to be to set UPTIME_KUMA_DISABLE_FRAME_SAMEORIGIN to true, however I'm not sure where to do this in Cloudron.

Thanks!

This looks really interesting:

https://github.com/nitnelave/lldap

Has anyone looked into how it might be used with Cloudron?

From the github page:

A lightweight authentication server that provides an opinionated, simplified LDAP interface for authentication. It integrates with many backends, from KeyCloak to Authelia to Nextcloud and more!

It comes with a frontend that makes user management easy, and allows users to edit their own details or reset their password by email.

The goal is not to provide a full LDAP server; if you're interested in that, check out OpenLDAP. This server is a user management system that is:

• simple to setup (no messing around with slapd),
• simple to manage (friendly web UI),
• low resources,
• opinionated with basic defaults so you don't have to understand the subtleties of LDAP.

@girish It's fixed! Thank you very much.

@subven Yes, I did take a look there and my yml is still set to the default 20 MB. Is that what you mean for me to check for?

A couple of interesting notes:

• Reducing the size of the image to ~2 MB does not help
• But I can upload an image that is about 100KB

@girish Thank you, this did the trick. In my case, I have Ubuntu 20.04 on a kvm inside my host, so I had to change the inotify watch limit for the "inner host". The warning message went away a few minutes after that.

I get the following error when trying to attach/upload a 4.6 MB image to a Vikunja task:

413 Request Entity Too Large
nginx/1.18.0 (Ubuntu)

Reading a few other threads here related to this error message (but for different apps) one of the recommendations was to increase the RAM. I did so, from 256 MB to 1 GB; however, the error remains when trying to upload.

Any suggested solutions from here?

@necrevistonnezr said in ownCloud Infinite Scale:

Public Beta is out! https://owncloud.com/infinite-scale-beta/

Exciting! I'd love to see ownCloud hosted on Cloudron. We've been using SyncThing for files and while effective, it has proven difficult to get new members of the team set up with it. Of course, ownCloud has many additional features besides file sync that would be valuable as well.