Cloudron Forum

For anyone running into this, it seems the migration assumes that all teams have a subscription. Until the migration is fixed, you can workaround it by faking a subscription.

@james in my case the same migration failed, and when I tried to migrate, I got the following migration error:

Error: P3018

A migration failed to apply. New migrations cannot be applied before the error is recovered from. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve

Migration name: 20250522054050_add_organisations

Database error code: 23502

Database error:
ERROR: null value in column "organisationId" of relation "OrganisationGroup" violates not-null constraint
DETAIL: Failing row contains (org_group_wxiansskyyehhuuo, null, INTERNAL_TEAM, MEMBER, null, 1, ADMIN).

DbError { severity: "ERROR", parsed_severity: Some(Error), code: SqlState(E23502), message: "null value in column \"organisationId\" of relation \"OrganisationGroup\" violates not-null constraint", detail: Some("Failing row contains (org_group_wxiansskyyehhuuo, null, INTERNAL_TEAM, MEMBER, null, 1, ADMIN)."), hint: None, position: None, where_: None, schema: Some("public"), table: Some("OrganisationGroup"), column: Some("organisationId"), datatype: None, constraint: None, file: Some("execMain.c"), line: Some(2006), routine: Some("ExecConstraints") }

So it seems the migration is making assumptions on the state of some tables.

Is there any update here? We'd like to deploy it to our Cloudron instance

I must be doing something wrong. I created the inbox on Cloudron, and when I try to configure int on Paperless-ngx it fails to connect to the server:

We are experiencing the same issue. I downgroaded to a 1.5.0 backup, but the issue remains, probably because the attempt to migrate to 1.6.0 put the DB in a weird state.

Hi,
I'm forked Writefreely to add a CloudronManifest.json file and adjusted the Dockerfile to install it in my Cloudron instance. The Docker image builds successfully but when Cloudron tries to run it, I get the following error when it runs box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx:

standard_init_linux.go:228: exec user process caused: exec format error

I did a bit of search on the internet and it turns out the restartservice.sh might be missing the shebang and therefore the OS doesn't know how to execute the script. I replaced the Alpine image with Ubuntu's and the issue persists so I'm not quite sure what I can install/configure in the OS for that script to run successfully. Any ideas?

Thanks in advance,
Pedro