Cloudron Forum

According to the app event log, I was able to restore to a working copy with 5.1.2, and an overnight update initiated automaticaly the next morning setting it to 5.2 at which point the app was listed as 'not responding'. I've disabled auto-update and started another restore to a 5.1.2 image to see what happens.

My Nextcloud was not running today, and I could see that there was an upgrade (5.3.0) yesterday. I tried to restore to that previous state (5.2.0), and it fails (Task Error: Task 15381 crashed as it ran out of memory).

I worry that the issue is likely due to my Nextcloud storage being filled up (out of space). When trying to restore, there is not enough space. I can't seem to get it started again.

What are my next steps? Restoring the backup also seems to be restoring the files that are filling up my drive.
I do have my data on a separate volume. I would be willing to migrate my data to a larger drive, but I need to get the instance up and stable first.

@rcdncn

An update. I goofed and it's working now. My first try I navigated to app/data/.htaccess and there was no

<IfModule mod_php7.c>

I noticed that there is both and htaccess and a .htaccess and I was in the incorrect file.

@nebulon I just tried this myself and when I refreshed the browser the the php value did not update. I don't have to restart any services for this to take effect?

Thank you for the prompt response. I've filed a ticket.

So... I messed up.

I accidentally deleted the custom path in Resources > Storage, and Nextcloud happily tried to flood the Nextcloud partition with my data.

When I ran out of space, the action failed and the Cloudron reset. I was able to get into it via terminal and delete the migrated data, but the Nextcloud Repair tab is displaying the following error:

An error occurred during the data migration operation: Addons Error: Error setting up postgresql. Status code: 500 message: could not write init file

My only option is to 'Retry Data Migration', and I can't 'Restart' or 'Enable Recovery Mode' the instance. Without restarting the instance, how can I stop this action??

Thanks @girish this totally worked.

Steps:

Option 1: Create a new skeleton folder

• add directory /app/data/skeleton using web terminal
• chown www-data:www-data skeleton
• add files to the directory, also chowning themto www-data:www-data
• open config file with vi /app/config/config.php
• insert line 'skeletondirectory' => '/app/data/skeleton'on a new line (i to enter insert mode)
• press esc, then :wq and <enter> to write and save
• new users will receive the contents of /app/data/skeleton on first log-in

Option 2: NO files added on first log-in

If you just want to remove the default skeleton (no files added on first launch), do the following:

• open config file with vi /app/config/config.php
• insert line 'skeletondirectory' => ''on a new line (i to enter insert mode)
• press esc, then :wq and <enter> to write and save

It's possible to change the skeleton location using this variable in config/config.php

'skeletondirectory' => '/path/to/nextcloud/core/skeleton',

Is there a writable space for this to point to?