Thanks @girish

Nextcloud corrupted all uploaded pictures from mobile app, I could not access them from the mobile app, desktop, or web app. I lost 2 years of photos and its honestly made me very depressed. MY phone deleted the on phone storage and now with the cloud storage corrupted or Whatever TF happened - they are all gone. Needless to say, I f this happened to a customer of mine or a family member Id be in big trouble.

Anyone have any ideas on why this occurred?

Anyone recommend anything better then nextcloud? I need a good reliable storage container - thats it.

I would like to upvote this big time

Ok, I solved it. I had to delete all my DNS settings that previously existed and then reset them. Once I did this within milliseconds Cloudron started working.

Whew, I was sweating bullets there for a minute.

Yay! Firebase is awesome except that its owned by sata..I mean google.

Glad there is an alternative

@girish ahh the good old turn it off and back on again, thank you.

@brutalbirdie said in So what am I doing wrong?:

First of all, PLEASE DON'T USE PICTURES / SCREENSHOTS FOR LOGS!
This makes the information inaccessible to some users (for example blind ones) and also it's a pain to read.
Simply copy the output press the Code Button

And put your copy-paste here.

---

@privsec simply said, you are using the shell incorrectly as pointed out by @fbartels

Also as @robi pointed out just read the docs.

You try to access minio-credentials which does not exist in the context as for example cp | rm | mv.
For example you can check if mv does exist by doing this:

/app/code# which mv
/usr/bin/mv

And the shell tells you mv is located in /usr/bin/mv, when you try this with minio-credentials you will get this

/app/code# which minio-credentials
/app/code#

aka no result. So minio-credentials does not exist as executable in the system paths context.

minio-credentials is a binary file in /app/code/minio-credentials which IS executable but the relative or full path is needed.

So if you would have followed the doc and copy-pasted

/app/code/minio-credentials set NEWACCESSKEY NEWSECRETKEY

it would have worked.

I never thought of accessibility issues, thanks for pointing that out. Ill adapt.

Ok, I will try that, thanks all.

This post makes me hopeful.

Ampache looks way neat, but it’s a PITA.

I can get my media to show up amd play in the browser but it’s not working on play:sub on iOS 14.4

I need something that “just works” and this excites me.

@girish OK, seems to have been my cache, good to know for future reference.

Thank you

Out of curiosity, is there any progress on adding this app?

@privsec That worked, thanks!

@girish said in Nextcloud not responding and will not update:

@privsec that bug is fixed in Cloudron 6.3. Before you update, what you can do is: go to Services -> Postgresql -> Restart. Then please retry the update of nextcloud. After nextcloud update succeeds, please update to Cloudron 6.3 which should fix the problem for good.

Trying that now

When I try to install a new nextcloud app, I get
Addons Error: Error tearing down postgresql. Status code: 500 message: sorry, too many clients already

I am getting the following when I try to restart, update, or backup my nextcloud instance

Jul 12 06:18:53 box:settings initCache: pre-load settings   
Jul 12 06:18:53 box:taskworker Starting task 1999. Logs are at /home/yellowtent/platformdata/logs/APP_ID/apptask.log
Jul 12 06:18:53 box:tasks 1999: {"percent":2,"error":null}
Jul 12 06:18:53 box:apptask cloud.website_address.com startTask installationState: pending_update runState: running
Jul 12 06:18:53 box:apptask cloud.website_address.com Updating to 4.9.1-1
Jul 12 06:18:53 box:tasks 1999: {"percent":5,"message":"Verify manifest"}
Jul 12 06:18:53 box:tasks 1999: {"percent":15,"message":"Backing up app"}
Jul 12 06:18:53 box:backups backupApp - Backing up cloud.website_address.com with tag 2021-07-12-061853-750
Jul 12 06:18:53 box:tasks 1999: {"percent":15,"message":"Backup - Snapshotting app cloud.website_address.com"}
Jul 12 06:18:53 box:services cloud.website_address.com backupAddons
Jul 12 06:18:53 box:services cloud.website_address.com backupAddons: Backing up ["postgresql","sendmail","ldap","redis","localstorage","scheduler","turn"]
Jul 12 06:18:53 box:services cloud.website_address.com Backing up postgresql
Jul 12 06:18:53 box:apptask cloud.website_address.com update aborted because backup failed BoxError: Unexpected response code when piping https://IP_ADDRESS:3000/databases/DB_STRING/backup?access_token=SOME_LONG_STRING: 500 message: Internal Server Error filename: /home/yellowtent/appsdata/APP_ID/postgresqldump
at /home/yellowtent/box/src/backups.js:1072:36
at wrapper (/home/yellowtent/box/node_modules/async/dist/async.js:268:20)
at iterateeCallback (/home/yellowtent/box/node_modules/async/dist/async.js:413:21)
at /home/yellowtent/box/node_modules/async/dist/async.js:321:20
at /home/yellowtent/box/src/services.js:1301:9
at f (/home/yellowtent/box/node_modules/once/once.js:25:25)
at Request.<anonymous> (/home/yellowtent/box/src/services.js:1312:53)
at Request.emit (events.js:315:20)
at Request.onRequestResponse (/home/yellowtent/box/node_modules/request/request.js:1059:10)
at ClientRequest.emit (events.js:315:20) {
reason: 'External Error',
details: {},
backupError: true
Jul 12 06:18:53 box:apptask cloud.website_address.com updating app with values: {"installationState":"installed","error":null,"health":null}
Jul 12 06:18:53 box:taskworker Task took 0.103 seconds
Jul 12 06:18:53 box:tasks setCompleted - 1999: {"result":null,"error":{"stack":"BoxError: Unexpected response code when piping https://IP_ADDRESS:3000/databases/DB_STRING/backup?access_token=SOME_LONG_STRING: 500 message: Internal Server Error filename: /home/yellowtent/appsdata/APP_ID/postgresqldump\n at /home/yellowtent/box/src/backups.js:1072:36\n at wrapper (/home/yellowtent/box/node_modules/async/dist/async.js:268:20)\n at iterateeCallback (/home/yellowtent/box/node_modules/async/dist/async.js:413:21)\n at /home/yellowtent/box/node_modules/async/dist/async.js:321:20\n at /home/yellowtent/box/src/services.js:1301:9\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at Request.<anonymous> (/home/yellowtent/box/src/services.js:1312:53)\n at Request.emit (events.js:315:20)\n at Request.onRequestResponse (/home/yellowtent/box/node_modules/request/request.js:1059:10)\n at ClientRequest.emit (events.js:315:20)","name":"BoxError","reason":"External Error","details":{},"message":"Unexpected response code when piping https://IP_ADDRESS:3000/databases/DB_STRING/backup?access_token=SOME_LONG_STRING: 500 message: Internal Server Error filename: /home/yellowtent/appsdata/APP_ID/postgresqldump","backupError":true}}
Jul 12 06:18:53 box:tasks 1999: {"percent":100,"result":null,"error":{"stack":"BoxError: Unexpected response code when piping https://IP_ADDRESS:3000/databases/DB_STRING/backup?access_token=SOME_LONG_STRING: 500 message: Internal Server Error filename: /home/yellowtent/appsdata/APP_ID/postgresqldump\n at /home/yellowtent/box/src/backups.js:1072:36\n at wrapper (/home/yellowtent/box/node_modules/async/dist/async.js:268:20)\n at iterateeCallback (/home/yellowtent/box/node_modules/async/dist/async.js:413:21)\n at /home/yellowtent/box/node_modules/async/dist/async.js:321:20\n at /home/yellowtent/box/src/services.js:1301:9\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at Request.<anonymous> (/home/yellowtent/box/src/services.js:1312:53)\n at Request.emit (events.js:315:20)\n at Request.onRequestResponse (/home/yellowtent/box/node_modules/request/request.js:1059:10)\n at ClientRequest.emit (events.js:315:20)","name":"BoxError","reason":"External Error","details":{},"message":"Unexpected response code when piping https://IP_ADDRESS:3000/databases/DB_STRING/backup?access_token=SOME_LONG_STRING: 500 message: Internal Server Error filename: /home/yellowtent/appsdata/APP_ID/postgresqldump","backupError":true}}

@atridad said in Home Assistant:

@privsec Yeah it can trigger events off of stuff like location + time of day which I use for turning off lights.

I am guessing this is bluetooth? Or do you have it based off of Access point connections?

@marcusquinn Wow, this is way cool. I like the location tracking.

@necrevistonnezr
I use both for on prem storage and for wasabi storage

@brutalbirdie said in So what am I doing wrong?:

First of all, PLEASE DON'T USE PICTURES / SCREENSHOTS FOR LOGS!
This makes the information inaccessible to some users (for example blind ones) and also it's a pain to read.
Simply copy the output press the Code Button

And put your copy-paste here.

---

@privsec simply said, you are using the shell incorrectly as pointed out by @fbartels

Also as @robi pointed out just read the docs.

You try to access minio-credentials which does not exist in the context as for example cp | rm | mv.
For example you can check if mv does exist by doing this:

/app/code# which mv
/usr/bin/mv

And the shell tells you mv is located in /usr/bin/mv, when you try this with minio-credentials you will get this

/app/code# which minio-credentials
/app/code#

aka no result. So minio-credentials does not exist as executable in the system paths context.

minio-credentials is a binary file in /app/code/minio-credentials which IS executable but the relative or full path is needed.

So if you would have followed the doc and copy-pasted

/app/code/minio-credentials set NEWACCESSKEY NEWSECRETKEY

it would have worked.

I never thought of accessibility issues, thanks for pointing that out. Ill adapt.

Ok, I will try that, thanks all.

@timconsidine

@privsec : are these problems stem-ing from the encruption plugin ? Rather than Nextcloud itself.
I have used NextCloud for 5+ years and I struggle to remember any problems at all.

It is certainly possible. I really don't want data stored unencrypted but it is looking like that is the only option.
All my data is stored on Wasabi, and they do have data stored at rest, but they store the encryption keys in meta data (from what I recall)

@necrevistonnezr

Rarely problems, and if any, I was able to solve them via the occ tool - thought I stayed away from encryption as my server is at home with nextcloud on an encrypted home folder so I don't need e2e encryption on top of that.
Also, activate only the really necessary addons.

Ill have to look into the OCC tool, hopefully all my data isn't lost.

@girish @necrevistonnezr I understand that there are unstable desktop apps. The issue has grown. The issue is not that the desktop app cant access the files, the issue is now that nextclouds update to v4.9.1 has corrupted something on the connection side to my wasabi storage.

I rolled back to v4.9.0 and I am getting this error for every file

To be clear this did not happen until the cloudron package updated to v4.9.1

I will test with the "stable version" of the desktop nextcloud app, however, I can replicate this exact same issue online directly within nextcloud. So the problem isnt the client side app.

The issue is that when the app upgraded from v4.9.0 to v4.9.1-1 something botched the encryption keys for the cloud storage to the point that even rolling back to v4.9.0 OR cloning the app from v4.9.0 doesnt work.

Emphasis added to highlight the root issue