Cloudron Forum

Hi, I'm trying to use LibreSign installed on my Cloudron Nextcloud instance, and running into an error with signing which seems to be related to poppler-utils not being installed. I haven't been able to figure out how install it, so that it's available to LibreSign. Can someone point me in the right direction?

@andreasdueren That worked. Thank you for your help!

@andreasdueren So, this works, but now results in a confusing error message on the login page:

The Nextcloud login form is disabled. Use another login option if available or contact your administration.

I have been looking for a way to hide that message, but can't find.

Even better would be if the default /login page could be configured to redirect automatically to the Cloudron OIDC login. Would you know how to do this?

@joseph Thank you!

Thanks, I see it now too.

But I'm curious, now, is there a way to disable the general [Account name or email / Password] login fields, as well as "Login with a device"—so that all that appears is "Login with Cloudron [or, my app name]"?

Since we are only provisioning accounts via Cloudron, the other options are now superflouous and confusing.

@jdaviescoates Is the the "Login with Cloudron" whitelabel option available yet, do you know?

Now that I've upgraded Nextcloud to the latest version with OIDC, our users are getting confused about how to log in.

+1, yes, please.

@nebulon I have just done what you suggest, thanks.

@nebulon - other apps are working pretty well, and we also have up to three players playing at the same time without slow performance.

Hi there, I am following up on an issue I'm seeing when trying to access Minecraft Server via the web as an admin, like this:

The error, across all browsers, but intermittently, is that the Login button click doesn't work. And sometimes the input fields do not appear at all. Yet sometimes the form works and I am able to access the in-game command line.

Web inspector shows the following errors:

Error: Internal Server Error
    Request https://minecraft.cosmos.coop/js/superagent.js:74
    emit https://minecraft.cosmos.coop/js/superagent.js:49
    onreadystatechange https://minecraft.cosmos.coop/js/superagent.js:90

In the server logs for the app, I am seeing this:

Apr 17 15:23:53 ERROR ServiceUnavailableError: Response timeout
Apr 17 15:23:53 at IncomingMessage.<anonymous> (/app/code/node_modules/connect-timeout/index.js:84:8)
Apr 17 15:23:53 at IncomingMessage.emit (events.js:315:20)
Apr 17 15:23:53 at Timeout.<anonymous> (/app/code/node_modules/connect-timeout/index.js:49:11)
Apr 17 15:23:53 at listOnTimeout (internal/timers.js:554:17)
Apr 17 15:23:53 at processTimers (internal/timers.js:497:7) [ /app/code/node_modules/express/lib/application.js:630:43 ]

Can someone help me decode those errors? Thanks for your help!

@girish That did the trick. Thanks!

@girish: In the log, after all the backups are completed, I see the following entries in the log:

2021-03-16T07:40:49.065Z box:tasks 6395: {"percent":75.31538461538463,"message":"box: Copied 10177 files with error: null"}
2021-03-16T07:40:49.069Z box:backups Rotated box backup successfully as id 2021-03-16-070020-445/box_2021-03-16-073619-390_v6.1.2
2021-03-16T07:40:49.069Z box:updater updating box https://prod-cloudron-releases.s3.amazonaws.com/box-3ee3786936-4dffce0b71-6.2.4.tar.gz
2021-03-16T07:40:49.069Z box:tasks 6395: {"percent":70,"message":"Installing update"}
2021-03-16T07:40:49.069Z box:shell update spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/update.sh /tmp/box-1465958658
2021-03-16T07:40:49.081Z box:shell update (stdout): Updating Cloudron with /tmp/box-1465958658

2021-03-16T07:40:49.082Z box:shell update (stdout): => reset service cloudron-updater status (of previous update)

2021-03-16T07:40:49.085Z box:shell update (stdout): => Run installer.sh as cloudron-updater.

2021-03-16T07:40:49.089Z box:shell update (stdout): => starting service (ubuntu 16.04) cloudron-updater. see logs using journalctl -u cloudron-updater

2021-03-16T07:40:49.094Z box:shell update (stdout): Failed to start transient service unit: Unit cloudron-updater.service already exists.

2021-03-16T07:40:49.094Z box:shell update (stdout): Failed to install cloudron. See log for details

2021-03-16T07:40:49.094Z box:shell update code: 1, signal: null
2021-03-16T07:40:49.097Z box:taskworker Task took 2447.75 seconds
2021-03-16T07:40:49.097Z box:tasks setCompleted - 6395: {"result":null,"error":{"stack":"BoxError: update exited with code 1 signal null\n    at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:66:17)\n    at ChildProcess.emit (events.js:198:13)\n    at ChildProcess.EventEmitter.emit (domain.js:448:20)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)","name":"BoxError","reason":"Spawn Error","details":{},"message":"update exited with code 1 signal null","code":1,"signal":null}}
2021-03-16T07:40:49.097Z box:tasks 6395: {"percent":100,"result":null,"error":{"stack":"BoxError: update exited with code 1 signal null\n    at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:66:17)\n    at ChildProcess.emit (events.js:198:13)\n    at ChildProcess.EventEmitter.emit (domain.js:448:20)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)","name":"BoxError","reason":"Spawn Error","details":{},"message":"update exited with code 1 signal null","code":1,"signal":null}}

Also, doing journalctl -u cloudron-updater does return -- No entries --.

This update keeps timing out on me, with error messages such as the following:

{
  "taskId": "6395",
  "errorMessage": "update exited with code 1 signal null",
  "timedOut": false
}

2021-03-13T06:30:16.608Z box:updater Update failed with error { stack:
   'BoxError: update exited with code 1 signal null\n    at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:66:17)\n    at ChildProcess.emit (events.js:198:13)\n    at ChildProcess.EventEmitter.emit (domain.js:448:20)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)',
  name: 'BoxError',
  reason: 'Spawn Error',
  details: {},
  message: 'update exited with code 1 signal null',
  code: 1,
  signal: null }

@brutalbirdie Belatedly, thanks for your help. It made my social-distancing daughter's weekend to be able to play Minecraft with her bestie on our shared server.

@brutalbirdie said in Error when connecting to the minecraft server :

You should have opened a new issue about this. Next time

Thanks for the tip. Next time...

Did you do any custom firewall stuff? Since there is also no 25565 port open.

That was the problem. I didn't have the port open. But since I was able to access the admin URL, I didn't think that the main port was still closed. Thanks for running that scan and pointing that out!

@nebulon I'm trying to connect to our Cloudron Minecraft server from Java clients on Mac and Linux.

When accessing the server from a web browser, I am able to login with my Cloudron account and see that it is running. However, when trying to connect using the Minecraft Java client, there is the timeout. I am trying access it via the app URL minecraft.cosmos.coop.I I have also tried appending the port :25565 to the URL in the server connection settings.

Seeing the same timeout error as reported above and I am wondering if it relates to the the fact that the client requires a Mojang or Microsoft user login, and these are not the same obviously as the Cloudron users allowed to access the app? I do have Microsoft account set up with the client; don't see an option to use any other form of login but Mojang or Microsoft within the client.

Hi, I am interested in using Object Storage for Nextcloud primary storage as well. Currently, an object storage provider can only be added as external storage. It would be great to be able to configure some s3-compatible Object Storage, which costs much less and can be more durable than Volume, as the primary storage. As I understand it, this is not yet possible in Cloudron. Would it be possible to enable this option?

Hi @subven and @nebulon: sorry for not replying sooner. In the middle of the project we decided not to use Ghost (or Cloudron) after all. But you gave me a clearer picture of how it could work if we do with another project. Thanks for the tips.

Our use case is that we will be hosting a website using a Ghost installation managed by Cloudron. We would like to keep the theme files in a Git repository (which could be on Github or self-hosted via one of the Cloudron apps). We would want to sync these files to the Ghost theme directory.

Additionally, we would like to have dev, staging, and production sites as part of our deploy process. So I imagine we would need three Ghost installs, each mirroring a different Git branch. Is that correct?

Is the above doable within the Cloudron ecosystem and if so can anyone point me in the right direction to set it up?