Comments (17)
Leaving this for future people:
If you're running Nextcloud on unRaid with Let's Encrypt Docker. Have a look in the appdata/letsencrypt/nginx/proxy.conf
Took me some time to check for all .conf files.
from hassio-nextcloud-backup.
client_max_body_size was the culprit.
from hassio-nextcloud-backup.
Hey, I know this is already closed but this might help some others to save time in searching for a result.
I hat the same problem with 413 Error and nothing here or on the web I found helped me.
To make it short I found the fix.
I have Nextcloud installed on Unraid with a reverse proxy swag (letsencrypt).
After searching through all proxy.conf - ngingx.conf - nextcloud.subdomain.conf - ...conf files for a fix and nothing changed,
following fixed it for me.
- Search in the nextcloud container shell for /etc/php*/php.ini and change the upload_max_filesize and post_max_size to something bigger (ex. 10G).
- Search in the nextcloud container shell for /config/nginx/site-confs/default and change the client_max_body_size to 0 (mine was set to 512).
- Eventually also check the /config/nginx/nginx.conf and appdata/swag/nginx/proxy-conf/nextcloud.subdomain.conf if client_max_body_size is set to 0;
At least this helped me to get the NC Backup to upload my snapshots succesfully.
from hassio-nextcloud-backup.
Im running nextcloud behind a Nginx Proxy Manager and havent been able to solve this problem.
Ive added/changed
client_max_body_size 0;
in /config/nginx/nginx.conf as well assupload_max_filesize
in /etc/php*/php.iniAs of what I can find these are the settings that has solved the problem for most people but for me no success.
I recently noticed that I could not upload big files (> 100MB) to nextcloud because I use Cloudflare as extra layer of security and because I dont have an Enterprise subscription the upload size is limited to 100MB.
If you checked/changed all config files but the problem still exists, maybe this is an similar issue as mine above.
For me I could fix this issue by using the direct IP (same Network) of the Nextcloud server and not use a domain name.
from hassio-nextcloud-backup.
Im running nextcloud behind a Nginx Proxy Manager and havent been able to solve this problem.
Ive added/changedclient_max_body_size 0;
in /config/nginx/nginx.conf as well assupload_max_filesize
in /etc/php*/php.ini
As of what I can find these are the settings that has solved the problem for most people but for me no success.I recently noticed that I could not upload big files (> 100MB) to nextcloud because I use Cloudflare as extra layer of security and because I dont have an Enterprise subscription the upload size is limited to 100MB.
If you checked/changed all config files but the problem still exists, maybe this is an similar issue as mine above.
For me I could fix this issue by using the direct IP (same Network) of the Nextcloud server and not use a domain name.
Changed NextCloud to local IP and can confirm it worked. Thanks alot ubl8!
from hassio-nextcloud-backup.
Hi, I experience the same issue and none of the above solutions could yet fix it.
I can download the backups from Home Assistant and upload them via the Web UI, the same endpoint effectively the addon would use. But the addon return 413. I could not find a related entry in the nextcloud logs.
Nextcloud is running behind the Nginx Proxy Manager, but neither the external accessible URL nor the local IP address work.
Also the nextcloud system information shows the correct limits (16 gb in my instance), but only the addon is not able to upload 1.6 or 1.8 gb files.
If you say non of the above solutions work, I gues you checked all of the .conf files? There might be more than one file affecting this...
Also uploading via the Web UI is not the same as with the Container... The Web UI uploads in more small peaces to prevent this issues...
I'm currently working on a new version that will include chunked upload to prevent the 413 error, at this time I can't give ETA because this new version will also include a migration to vuejs that requires a lot of work.
You can follow my progress on the vue
branch
from hassio-nextcloud-backup.
Hi !
Can i have the size of your backup file? Because in webdav, 413
is Request Entity Too Large
.
from hassio-nextcloud-backup.
The backup is 242257920 (232M). Please let me know if there is anything further I can provide.
from hassio-nextcloud-backup.
I'm not sure but i think it's more an issue with your setup, not with the addon.
Do you have a proxy in front of Nextcloud ?
from hassio-nextcloud-backup.
nextcloud is installed from snap on an 18.0X server.
from hassio-nextcloud-backup.
Do you have Nginx in front of nextcloud (or other reverse proxy)? I found a similar issue on the Nexcloud-snap repo (nextcloud-snap/nextcloud-snap#1017)
from hassio-nextcloud-backup.
I'm running Nextcloud & SWAG dockers on unraid and running into the same issue. Could someone share a working NC/SWAG config?
from hassio-nextcloud-backup.
Im running nextcloud behind a Nginx Proxy Manager and havent been able to solve this problem.
Ive added/changed client_max_body_size 0;
in /config/nginx/nginx.conf as well ass upload_max_filesize
in /etc/php*/php.ini
As of what I can find these are the settings that has solved the problem for most people but for me no success.
from hassio-nextcloud-backup.
Hi, I experience the same issue and none of the above solutions could yet fix it.
I can download the backups from Home Assistant and upload them via the Web UI, the same endpoint effectively the addon would use. But the addon return 413. I could not find a related entry in the nextcloud logs.
Nextcloud is running behind the Nginx Proxy Manager, but neither the external accessible URL nor the local IP address work.
Also the nextcloud system information shows the correct limits (16 gb in my instance), but only the addon is not able to upload 1.6 or 1.8 gb files.
from hassio-nextcloud-backup.
Hi, I experience the same issue and none of the above solutions could yet fix it.
I can download the backups from Home Assistant and upload them via the Web UI, the same endpoint effectively the addon would use. But the addon return 413. I could not find a related entry in the nextcloud logs.
Nextcloud is running behind the Nginx Proxy Manager, but neither the external accessible URL nor the local IP address work.
Also the nextcloud system information shows the correct limits (16 gb in my instance), but only the addon is not able to upload 1.6 or 1.8 gb files.
If you say non of the above solutions work, I gues you checked all of the .conf files? There might be more than one file affecting this...
Also uploading via the Web UI is not the same as with the Container... The Web UI uploads in more small peaces to prevent this issues...
from hassio-nextcloud-backup.
Unfortunately none of the solutions here could solve my issue either
from hassio-nextcloud-backup.
If anyone else is using the Nextcloud Docker image. Here is what I did to solve it
from hassio-nextcloud-backup.
Related Issues (20)
- Backups ordered wrong HOT 2
- Fail to upload snapshot to nextcloud (HTTPError: Response code 413 (Request Entity Too Large)) ! HOT 2
- The upload does not work HOT 6
- Addons are not started after a backup where the upload fails
- Migration to VueJs and more
- Can't connect to Nextcloud (Error: getaddrinfo ENOTFOUND https) ! HOT 2
- 3rd Party platform compatibility HOT 17
- Chunked upload HOT 1
- 502 Bad Gateway error when uploading large backups (6016.2 MB) HOT 5
- Upload Code 201 but 0 bytes and/or HTTPError Response code 500 HOT 1
- Request entity too large HOT 2
- [Feature Request] Full Backup
- Monitoring State of Backups HOT 1
- Can't create new snapshot (Response code 400 (Bad Request)) HOT 6
- ENOTFOUND HTTPS HOT 1
- Can't create new snapshot (Response code 400 (Bad Request)) HOT 1
- Add-on not working with nextcloud systems having webroot set as a subdirectory of the default web server document root. This means the nextcloud connection URL is something like: http://full.host.name/subdir/. It would be nice to also support this case. HOT 1
- Fail to upload snapshot to nextcloud (RequestError: read ECONNRESET) !
- Backup not Working - Response code 400 (Bad Request)
- Can't create new snapshot (Response code 400 (Bad Request)) HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from hassio-nextcloud-backup.