@girish I found this when i clicked update:
Both my apps are running and are accessible.
I now tried stopping the Nextcloud instance and started it.
And it the app the 1 dead app is now 2 alive and 0 dead.
Now i could update normally.
Not sure what i missed in the first place but now works.
Thanks for the help 
@privsec Thanks for the tip. It had enough space and i think the redis service would have restarted with the full reboot.
@girish Thanks for the checkin.
Haven't been notified about your reply.
No the issue still persists.
Hi, i noticed it first after the update of 6 to 7 that my Nextcloud instance is stuck in updating.
I tried having a look into the logs but didn't find anything. Tried rebooting afterwards. I forgot about the issue and now came back to this. Everything is set to auto update.
When i manually click on update now the button disappears after a few seconds, but it only shows update (queued).
Maybe this could have happened because the backup of the Nextcloud instance took to long. (currently working on a solution for that). The Backups are still working normally.
What logs are needed for further help?
Thanks ahead
Hi,
i got the overnight Update of my Nextcloud. Now i have the following duplicate Key Error:
Dec 14 10:59:07 => Applying oc_filecache_extended workaround
Dec 14 10:59:07 SELECT 9852
Dec 14 10:59:07 ALTER TABLE
Dec 14 10:59:07 ALTER TABLE
Dec 14 10:59:07 DROP TABLE
Dec 14 10:59:07 Check primary keys.
Dec 14 10:59:08 Adding primary key to the filecache_extended table, this can take some time...
Dec 14 10:59:09 In AbstractPostgreSQLDriver.php line 51:
Dec 14 10:59:09
Dec 14 10:59:09 An exception occurred while executing 'ALTER TABLE oc_filecache_extended AD
Dec 14 10:59:09 D PRIMARY KEY (fileid)':
Dec 14 10:59:09
Dec 14 10:59:09 SQLSTATE[23505]: Unique violation: 7 ERROR: could not create unique index
Dec 14 10:59:09 "oc_filecache_extended_pkey"
Dec 14 10:59:09 DETAIL: Key (fileid)=(35050) is duplicated.
Dec 14 10:59:09 In PDOConnection.php line 83:
Dec 14 10:59:09
Dec 14 10:59:09 SQLSTATE[23505]: Unique violation: 7 ERROR: could not create unique index
Dec 14 10:59:09 "oc_filecache_extended_pkey"
Dec 14 10:59:09 DETAIL: Key (fileid)=(35050) is duplicated.
Dec 14 10:59:09 In PDOConnection.php line 78:
Dec 14 10:59:09
Dec 14 10:59:09 SQLSTATE[23505]: Unique violation: 7 ERROR: could not create unique index
Dec 14 10:59:09 "oc_filecache_extended_pkey"
Dec 14 10:59:09 DETAIL: Key (fileid)=(35050) is duplicated.
Dec 14 10:59:09 db:add-missing-primary-keys
I just did the latest update manualy but i didn't fix anything. Also i tried restarting Cloudron with Nextcloud in Recovery Mode as mentioned in a different Issue.
Cloudron is now 6.0.1 and Nextcloud is now 20.0.3 with the Packaged version v4.8.3
Thanks ahead for your help
@fbartels That's very nice to use. Thanks.
I narrowed it down to /home/yellowtent/appsdata with 53,8 GB but i would not change something here.
The other two huge folders are in /var/lib/docker.
First is /volumes with one large file (53 GB) ending with ...-local-storage. The second (22 GB) is the folder /overlay2.
Is it safe to run docker system prune -a ?
Maybe also -volumes? Does this mess anything up with Cloudron if my two apps are running?
Thanks for the reply.
The Vm has already 5GB of Ram. Swap is about the same of what i can find.
I will have a deeper look.
Hi,
as shown in the photo my Cloudron is running out of space. But not from Cloudron or its apps.
I have my Backups on an Nas added via SMB.
There is nothing else installed on this VM. As it could only be Cloudron creating 120GB i am not sure how to clean them up.
Once i added 100 GB to the VM and formatted it correctly.
Thanks ahead for your help
This is the chrome console error
website erased
Thats the Error i get when i am starting the terminal
<I deleted the image because it showed the domain name - girish>
@girish Ok the 2. thing is also not working.
@girish This is also with Nextcloud (all other)
@girish Hi thanks for the fast reply.
Yes the App in running mode.
It is saying 'connecting...' only for a second or two with the screen size and then is all going black (terminal)
Hi, i just installed Mastodon successfully. After i created an user on the running server i tried to add the user the admin functions through the Terminal.
The Terminal says: 'Connecting...' and 'If you resize the Window press cntrl+D....'.
After that the screen switches to full black terminal. I have also tried recovery mode but nothing different. I also had a look in the logs but i found nothing..
Thanks ahead for your help
As it finally finished Uploading i got this error. Any thoughts on how to solve this and may recognize the Permission earlier?
Feb 13 19:44:23 box:tasks 1228: {"percent":26,"message":"Copying /backups/snapshot/app_0b0ea93e-1a87-4172-805c-c4171fd00c88.tar.gz to /backups/2020-02-13-110006-815/app_0b0ea93e-1a87-4172-805c-c4171fd00c88_2020-02-13-194423-405_v4.3.1.tar.gz (cloud.wieser.myhome-server.de)"}
Feb 13 19:44:23 box:shell copy spawn: /bin/cp -al /backups/snapshot/app_0b0ea93e-1a87-4172-805c-c4171fd00c88.tar.gz /backups/2020-02-13-110006-815/app_0b0ea93e-1a87-4172-805c-c4171fd00c88_2020-02-13-194423-405_v4.3.1.tar.gz
Feb 13 19:44:23 box:shell copy (stdout): /bin/cp:
Feb 13 19:44:23 box:shell copy (stdout): cannot create hard link '/backups/2020-02-13-110006-815/app_0b0ea93e-1a87-4172-805c-c4171fd00c88_2020-02-13-194423-405_v4.3.1.tar.gz' to '/backups/snapshot/app_0b0ea93e-1a87-4172-805c-c4171fd00c88.tar.gz'
Feb 13 19:44:23 box:shell copy (stdout): : Permission denied
Feb 13 19:44:23 box:shell copy (stdout):
Feb 13 19:44:23 box:shell copy code: 1, signal: null
Feb 13 19:44:23 box:backups cloud.wieser.myhome-server.de Unable to backup { BoxError: copy exited with code 1 signal null
Thanks. It worked
I only had to add vers=1.0 because my NAS (FritzBox) only uses SMB 1.
It was a wrong configuration on my side but thanks for your support
Is there the possiblity to make a Backup to a Nas?
The Nas is using either SMB or Ftp for access.
It is the Nas System from a FritzBox.
Thanks
As Nextcloud Hub 18 is released, when does the Update come to Cloudron?
Or should I switch in the Nextcloud App from Cloudron update to Auto update?
I have set up Cloudron with a DynDns in a VM and it worked fine. Now i have added an Apache Reverse Proxy in a seperate Vm. When i now try to reach Cloudron (every cloudron domain) i am getting the Browser error: err_too_many_redirects. My third VM with a Website is reachable.
Any thoughts on how to solve this?
Or is there a possibillity to add a reverse proxy in Cloudron?
thanks in advance