holy smoke, now ive screwed my NCP instance up ones more!
I would ask for help to get back up and running!
what I have done!
i used the ncp web interface to look into the details of my configuration and saw that for 32bit, filesize above 2GB was not supported, my nextcloud config was set to 10GB (I have done that during the initial setup).
So i proceeded the following stuff:
- nc-limits
[ nc-limits ] (Thu 5 May 16:37:09 CEST 2022) Using 3018906624B for PHP Using 6 PHP threads Using 955970560 memory for the database
after a reboot the ncp website shown
HPB service down
I wasnt aware of this line in the system info and checked the log files
System config value trusted_domains => 3 set to string montino.duckdns.org
System config value overwrite.cli.url set to string https://montino.duckdns.org/
System config value trusted_proxies => 11 set to string 127.0.0.1
System config value trusted_proxies => 12 set to string ::1
System config value trusted_proxies => 13 set to string montino.duckdns.org
System config value trusted_proxies => 14 set to string 84.148.160.88
✓ redis is configured
✓ push server is receiving redis messages
✓ push server can load mount info from database
✓ push server can connect to the Nextcloud server
🗴 push server is not a trusted proxy, please add '192.168.1.1' to the list of trusted proxies or configure any existing reverse proxy to forward the 'x-forwarded-for' send by the push server.
See https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/reverse_proxy_configuration.html#defining-trusted-proxies for how to set trusted proxies.
The following trusted proxies are currently configured: "127.0.0.1", "::1", "montino.duckdns.org", "84.148.160.88"
of which the following seem to be invalid: "montino.duckdns.org"
The following x-forwarded-for header was received by Nextcloud: 1.2.3.4
from the following remote: 192.168.1.1
If you're having issues getting the trusted proxy setup working, you can try bypassing any existing reverse proxy
in your setup by setting the `NEXTCLOUD_URL` environment variable to point directly to the internal Nextcloud webserver url
(You will still need the ip address of the push server added as trusted proxy)
I nevern seen this issues before. so i digged into the details and rebooted one or two times without resolving the issue (I first thought, maybe the nc-limit update went down the line).
but after that I missclicked and run
[ nc-nextcloud ] the reinstallation of the NC
I foreced a reboot during the runtime after some seconds with my ssh login to aboard this nc-nextcloud installation.
now my Nextcloud instance is gone.
the ncdata folder etc. is still present.
i have daily backups with nc-backup-auto without DATA
can someone tell me the next steps to restore my nextcloud instance
when i look into the details of Restoring a NCP instance
when I use nc-restore this will reset the data from my /media/USBdrive/ncdata path right? so all data of my users are gone from my ssd attached to the rapsberrypi.
can I (just for the sake of safty) backup this user data storage prior to nc-restore into another folder inside the ssd “USBdrive”. i have enought space left on the ssd for this duplication.
I cannot use NC-backup with included DATA for that, because I screwed up the nextcloud installation right? so this brings nothing.
shall i just deep copy the folder through bash console? can anyone give advice what the steps are for that or any hints what I must take into consideration?
please help.
I have updated the first post with another topic title and information that the intial problem is not a top priority for the moment 