Cloudron Forum

Thank you @nebulon and @joseph

Thank you @nebulon
Please release the next patch when possible, because this means that we can't do any config editions to any of the Apps

I wish that we could do that, but this specific client doesn't want the configuration to be done. He is afraid that something might break. We assured him that all will be ok, but he insists. We must respect his wishes.

Perhaps in the near future we will try it for some other client with high number of users.

Hi

When we try to edit the config files using the File Manager for any app this happens:
(Example with Matrix)

1. Edit file: homeserver.yaml (owner: cloudron)
2. Click: Save + Close
3. In the folder there is a new file: homeserver.yaml.1 (owner: root)
4. Click: Restart App
5. The new file has changed owner: homeserver.yaml.1 (owner: cloudron)
6. And there aren't any changes performed inside: homeserver.yaml (owner: cloudron)
7. The changes aren't applied in the app

Is it possibly something that we are doing wrong, or is it just a temporary bug?

Thank you @girish that will be very useful

Thank you @nebulon and @girish very much!

Yes @nebulon it's a quite big database. This Nextcloud has around 6000 users.
The disk has above 1TB SSD so that was ok.

Thank you @girish for the detailed steps. They were very helpful!
The import was a success.

Note: The change isn't persistent on a Reboot.
It would be nice to change this:
max_connections = 500
to this:
max_connections = 3000
If the server is powerful enough, it should be able to sustain the x6 boost.
The only challenge is how to make the change persistent after Reboot

Thank you @nebulon and @joseph on your help

The PostreSQL service was already set to the max available 64GB RAM (from total 132GB RAM)

@nebulon here is the requested log: (thank you again)

Jul 17 06:51:43 2024-07-17 04:51:43.846 UTC [1062] ERROR: temporary file size exceeds temp_file_limit (1048576kB)

Jul 17 06:51:43 2024-07-17 04:51:43.846 UTC [1062] STATEMENT: CREATE INDEX oc_notifications_object ON public.oc_notifications USING btree (object_type, object_id);

Jul 17 06:51:43 2024-07-17 04:51:43.848 UTC [1007] root@db57af86418ca34a61b18acbf6308fb45e CONTEXT: parallel worker

Jul 17 06:51:43 2024-07-17 04:51:43.848 UTC [1007] root@db57af86418ca34a61b18acbf6308fb45e ERROR: temporary file size exceeds temp_file_limit (1048576kB)

Jul 17 06:51:43 2024-07-17 04:51:43.848 UTC [1007] root@db57af86418ca34a61b18acbf6308fb45e STATEMENT: CREATE INDEX oc_notifications_object ON public.oc_notifications USING btree (object_type, object_id);

Jul 17 06:51:43 2024-07-17 04:51:43.851 UTC [49] LOG: background worker "parallel worker" (PID 1062) exited with exit code 1

Jul 17 06:51:44 CONTEXT: parallel worker

Jul 17 06:51:44 restore: failed to restore database. code=3

Jul 17 06:51:44 restore: stderr from db import: ERROR: temporary file size exceeds temp_file_limit (1048576kB)

Jul 17 22:20:03 [GET] /healthcheck

Jul 17 22:20:03 healthcheck: disconnected

The PostgreSQL Dump file is 15GB.
From what we understand here, the limit is 1GB.
How can we increase this limit or solve this problem another way?

Hi

Have tried 10+ times to run a Nextcloud migration.

But we are constantly getting the same error.

We hope that this can be solved. Since this forum is public, the solution will be available for everyone else who will have the same problem

Task Error in the Nextcloud > Repair Tab:

Addons Error: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e: status 500 complete false

Logs:

17 06:41:29 box:tasks update 2805: {"percent":65,"message":"Download finished 2024-07-15-190000-564/app_vtmg.link_v4.22.2/postgresqldump to /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump"}
Jul 17 06:41:29 box:backupformat/rsync Recreating empty directories in {"localRoot":"/home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e","layout":[]}

Jul 17 06:44:37 box:backuptask downloadApp: time: 27101.091

Jul 17 06:44:37 box:tasks update 2805: {"percent":70,"message":"Restoring addons"}

Jul 17 06:44:37 box:services restoreAddons

Jul 17 06:44:37 box:services restoreAddons: restoring ["postgresql","sendmail","ldap","redis","localstorage","scheduler","turn"]

Jul 17 06:44:37 box:services Restore postgresql

Jul 17 06:44:37 box:services pipeFileToRequest: piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e

Jul 17 06:48:43 box:services pipeFileToRequest: piped /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e

Jul 17 06:51:44 box:services pipeFileToRequest: request completed with status code 500

Jul 17 06:51:44 box:apptask run: app error for state pending_restore: BoxError: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e: status 500 complete false at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1311:60) at ClientRequest.emit (node:events:518:28) at ClientRequest.emit (node:domain:488:12) at HTTPParser.parserOnIncomingClient (node:_http_client:698:27) at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17) at Socket.socketOnData (node:_http_client:540:22) at Socket.emit (node:events:518:28) at Socket.emit (node:domain:488:12) at addChunk (node:internal/streams/readable:559:12) at readableAddChunkPushByteMode (node:internal/streams/readable:510:3) { reason: 'Addons Error', details: {} }

Jul 17 06:51:44 box:taskworker Task took 27570.192 seconds

Jul 17 06:51:44 box:tasks setCompleted - 2805: {"result":null,"error":{"stack":"BoxError: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e: status 500 complete false\n at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1311:60)\n at ClientRequest.emit (node:events:518:28)\n at ClientRequest.emit (node:domain:488:12)\n at HTTPParser.parserOnIncomingClient (node:_http_client:698:27)\n at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)\n at Socket.socketOnData (node:_http_client:540:22)\n at Socket.emit (node:events:518:28)\n at Socket.emit (node:domain:488:12)\n at addChunk (node:internal/streams/readable:559:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)","name":"BoxError","reason":"Addons Error","details":{},"message":"Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e: status 500 complete false"}}

Jul 17 06:51:44 box:tasks update 2805: {"percent":100,"result":null,"error":{"stack":"BoxError: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e: status 500 complete false\n at ClientRequest.<anonymous> (/home/yellowtent/box/src/services.js:1311:60)\n at ClientRequest.emit (node:events:518:28)\n at ClientRequest.emit (node:domain:488:12)\n at HTTPParser.parserOnIncomingClient (node:_http_client:698:27)\n at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)\n at Socket.socketOnData (node:_http_client:540:22)\n at Socket.emit (node:events:518:28)\n at Socket.emit (node:domain:488:12)\n at addChunk (node:internal/streams/readable:559:12)\n at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)","name":"BoxError","reason":"Addons Error","details":{},"message":"Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e: status 500 complete false"}}
[no timestamp]  Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/57af8641-8ca3-4a61-b18a-cbf6308fb45e/postgresqldump to http://172.18.30.2:3000/databases/db57af86418ca34a61b18acbf6308fb45e/restore?access_token=072212caff8830b05a63b50516fa15953eeb2cd970e6668dbf7268d8dd43d609dcb58e6bf039e0b3befdd38b137de76828624185d3b0d6340a38f4e7aa467a2842bd64880a0392f4644e69faf49c4049fedcb4a2b3b41f7934a82d91e2453ea7172dad77131adb9389793dad635596d1c8db452a816a70985ed2941bfdc5d78e&username=user57af86418ca34a61b18acbf6308fb45e: status 500 complete false

Additional info if needed:

1. The migration is run from a Linode VPS (Nexcloud on Cloudron) Ubuntu 22.04 LTS OS
   to a Dedicated server Ubuntu 24.04 LTS OS
2. In order so that there isn't any PostgreSQL database corruption, before the Backup was created we put Nextcloud in Recovery mode (so that the database isn't edited). We also tested without putting it in Recovery mode and the result was the same.
3. The migration is running from a Linode Object Storage

@girish we are trying to connect a MySQL DB but it requires the following:
driver "mysql-connector-python"
Is it possilble for it to be installed by us or by your team (by pushing it in the new update)?
Thank you

@girish Thank you very much.

We run the tests again by reinstalling it again.
It seems that the problem originated when we installed multiple Apps and then UptimeKuma somehow broke. So we installed them one by one, and now it's ok.

The latest version of Cloudron 7.7.2
made all newly installed Uptime Kuma's to be unavailable to be loaded upon installation.

I even tried to install older versions of Uptime Kuma. Again the same result.

Then I did the installation on Cloudron 7.7.1 and it works.

If possible please fix this bug before pushing 7.7.2 in the Stable Updates section.
Thanks

@girish Thank you. Your solution did the trick.
But we needed the ipv6 to be functional.
So what we did to make it work was > reinstall Ubuntu 22.04 LTS OS and didn't install unbound in advance. All is good now.

When I enter in the terminal this:
enable_ipv6

This is the result:

** (generate:57510): WARNING **: 13:03:50.397: Permissions for /etc/netplan/01-netcfg.yaml are too open. Netplan configuration should NOT be accessible by others.
** (generate:57510): WARNING **: 13:03:50.398: `gateway6` has been deprecated, use default routes instead.
See the 'Default routes' section of the documentation for more details.
** (generate:57515): WARNING **: 13:03:50.541: Permissions for /etc/netplan/01-netcfg.yaml are too open. Netplan configuration should NOT be accessible by others.
** (generate:57515): WARNING **: 13:03:50.542: `gateway6` has been deprecated, use default routes instead.
See the 'Default routes' section of the documentation for more details.
WARNING:root:Cannot call Open vSwitch: ovsdb-server.service is not running.
** (process:57513): WARNING **: 13:03:50.959: Permissions for /etc/netplan/01-netcfg.yaml are too open. Netplan configuration should NOT be accessible by others.
** (process:57513): WARNING **: 13:03:50.960: `gateway6` has been deprecated, use default routes instead.
See the 'Default routes' section of the documentation for more details.
** (process:57513): WARNING **: 13:03:51.254: Permissions for /etc/netplan/01-netcfg.yaml are too open. Netplan configuration should NOT be accessible by others.
** (process:57513): WARNING **: 13:03:51.255: `gateway6` has been deprecated, use default routes instead.
See the 'Default routes' section of the documentation for more details.
** (process:57513): WARNING **: 13:03:51.255: Permissions for /etc/netplan/01-netcfg.yaml are too open. Netplan configuration should NOT be accessible by others.
** (process:57513): WARNING **: 13:03:51.255: `gateway6` has been deprecated, use default routes instead.
See the 'Default routes' section of the documentation for more details.

@girish Thank you Girish very much for your fast and direct response

From this command:
ping6 2604:a880:1:4a::2:7000
This was the result:

From fd43:4f4e:5943:50::a icmp_seq=5 Destination unreachable: No route

.

And from this command:
curl -6 https://ipv6.api.cloudron.io/api/v1/helper/public_ip
This was the result:

curl: (7) Failed to connect to ipv6.api.cloudron.io port 443 after 1219 ms: Network is unreachable

Your assistance with this problem will be greatly appreciated

Hello everybody

The last 2 Cloudron installations on Azure VPS and Contabo VPS, have resulted in the same problem.
The Let's Encrypt Certificate failed to be issued.

Here is the Contabo VPS log:

Oct 27 21:43:28box:taskworker Starting task 3. Logs are at /home/yellowtent/platformdata/logs/tasks/3.log
Oct 27 21:43:28box:tasks update 3: {"percent":101,"message":"Ensuring certs of my.chat.newtonhealthcore.com"}
Oct 27 21:43:28box:reverseproxy ensureCertificate: my.chat.newtonhealthcore.com needs acme cert
Oct 27 21:43:28box:cert/acme2 getCertificate: for fqdn my.chat.newtonhealthcore.com and domain chat.newtonhealthcore.com
Oct 27 21:43:28box:cert/acme2 Acme2: will get cert for fqdn: my.chat.newtonhealthcore.com cn: my.chat.newtonhealthcore.com certName: my.chat.newtonhealthcore.com wildcard: false http: true
Oct 27 21:43:28box:cert/acme2 getCertificate: start acme flow for my.chat.newtonhealthcore.com from https://acme-v02.api.letsencrypt.org/directory
Oct 27 21:43:31box:cert/acme2 Attempt 1 failed. Will retry: connect ENETUNREACH 2606:4700:60:0:f53d:5624:85c7:3a2c:443
Oct 27 21:43:51box:cert/acme2 Attempt 2 failed. Will retry: connect ENETUNREACH 2606:4700:60:0:f53d:5624:85c7:3a2c:443
Oct 27 21:44:11box:cert/acme2 Attempt 1 failed. Will retry: connect ENETUNREACH 2606:4700:60:0:f53d:5624:85c7:3a2c:443
Oct 27 21:44:11box:cert/acme2 Acme2: will get cert for fqdn: my.chat.newtonhealthcore.com cn: my.chat.newtonhealthcore.com certName: my.chat.newtonhealthcore.com wildcard: false http: true
Oct 27 21:44:11box:cert/acme2 getCertificate: for fqdn my.chat.newtonhealthcore.com and domain chat.newtonhealthcore.com
Oct 27 21:44:11box:cert/acme2 getCertificate: start acme flow for my.chat.newtonhealthcore.com from https://acme-v02.api.letsencrypt.org/directory
Oct 27 21:44:11box:cert/acme2 Attempt 1 failed. Will retry: connect ENETUNREACH 2606:4700:60:0:f53d:5624:85c7:3a2c:443
Oct 27 21:44:31box:cert/acme2 Attempt 2 failed. Will retry: connect ENETUNREACH 2606:4700:60:0:f53d:5624:85c7:3a2c:443
Oct 27 21:44:51box:cert/acme2 Attempt 2 failed. Will retry: connect ENETUNREACH 2606:4700:60:0:f53d:5624:85c7:3a2c:443
Oct 27 21:44:51box:cert/acme2 Acme2: will get cert for fqdn: my.chat.newtonhealthcore.com cn: my.chat.newtonhealthcore.com certName: my.chat.newtonhealthcore.com wildcard: false http: true
Oct 27 21:44:51box:cert/acme2 getCertificate: for fqdn my.chat.newtonhealthcore.com and domain chat.newtonhealthcore.com
Oct 27 21:44:51box:cert/acme2 getCertificate: start acme flow for my.chat.newtonhealthcore.com from https://acme-v02.api.letsencrypt.org/directory
Oct 27 21:44:51box:cert/acme2 Attempt 1 failed. Will retry: connect ENETUNREACH 2606:4700:60:0:f53d:5624:85c7:3a2c:443
Oct 27 21:45:11box:cert/acme2 Attempt 2 failed. Will retry: connect ENETUNREACH 2606:4700:60:0:f53d:5624:85c7:3a2c:443
Oct 27 21:45:31box:reverseproxy ensureCertificate: error: connect ENETUNREACH 2606:4700:60:0:f53d:5624:85c7:3a2c:443
Oct 27 21:45:31box:tasks update 3: {"message":"Rebuilding app configs"}
Oct 27 21:45:31box:reverseproxy writeDashboardConfig: writing admin config for chat.newtonhealthcore.com
Oct 27 21:45:31box:reverseproxy writeCertificate: my.chat.newtonhealthcore.com will use fallback certs because acme is missing
Oct 27 21:45:31box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
Oct 27 21:45:31box:mailserver checkCertificate: certificate has not changed
Oct 27 21:45:31box:shell notifyCertChange spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh box
Oct 27 21:45:31box:tasks update 3: {"message":"Checking expired certs for removal"}
Oct 27 21:45:31box:reverseproxy cleanupCerts: done
Oct 27 21:45:31box:tasks setCompleted - 3: {"result":null,"error":null}
Oct 27 21:45:31box:tasks update 3: {"percent":100,"result":null,"error":null}
Oct 27 21:45:31box:taskworker Task took 122.95 seconds

Have any of you found a solution for this?

@girish Thank you Girish for the fast response!
We solved it now with your help.

There is a bug with the latest Cloudron update.

Before this update, on the Cloudron login page it was: Login to BRANDNAME
Now it is: Login to Cloudron

Can we get a timeline on when this will get fixed?

Update:
This big has been fixed in one of the latest updates.

When I try to change the Admin Email of Chatwoot:

1. Confirms that the change is done
2. Logs me out of the account
3. Then when I try to use the new email to log in > ERROR
4. Then I can login only via the old email
   (Hence > The email can't be changed)

Is this something some of you guys have faced before?