[GH-ISSUE #2157] Synology Nas hitting HTTP Error 413 When Trying to Upload Videos #1546

Closed
opened 2026-02-26 07:31:30 +03:00 by kerem · 7 comments
Owner

Originally created by @7ekhed on GitHub (Jul 17, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2157

Some small videos upload fine, all photos upload fine, but larger videos (30+ seconds) hit the HTTP Error 413, and halt my backup completely (Synology Photos). This seems to be an NginxProxyManager max file size or data stream type of error, how can I fix this?

Originally created by @7ekhed on GitHub (Jul 17, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2157 Some small videos upload fine, all photos upload fine, but larger videos (30+ seconds) hit the HTTP Error 413, and halt my backup completely (Synology Photos). This seems to be an NginxProxyManager max file size or data stream type of error, how can I fix this?
kerem 2026-02-26 07:31:30 +03:00
  • closed this issue
  • added the
    stale
    label
Author
Owner

@Theenoro commented on GitHub (Aug 24, 2022):

Maxbe a bit late.
Edit your Proxy Host config, then under Advanced add client_max_body_size 50M;

If this doesn't work:
Add a location under Custom Locations. Set your location to your url where you upload the files.
For my usecase it was /api/uploads ( I dont know what the synology photos is, but you got the http error 413, the url which is shown there should be entered there ) then use the same forward hostname as you have under details and the in my case /api/uploads like foo.bar/api/uploads and set below client_max_body_size 50M;

<!-- gh-comment-id:1225685301 --> @Theenoro commented on GitHub (Aug 24, 2022): Maxbe a bit late. Edit your Proxy Host config, then under Advanced add ` client_max_body_size 50M; ` If this doesn't work: Add a location under Custom Locations. Set your location to your url where you upload the files. For my usecase it was ` /api/uploads ` ( I dont know what the synology photos is, but you got the http error 413, the url which is shown there should be entered there ) then use the same forward hostname as you have under details and the in my case ` /api/uploads ` like foo.bar/api/uploads and set below ` client_max_body_size 50M; `
Author
Owner

@kosmonot commented on GitHub (Aug 26, 2022):

Did you disable any Cloudflare caching for your nas subdomain?

<!-- gh-comment-id:1227943392 --> @kosmonot commented on GitHub (Aug 26, 2022): Did you disable any Cloudflare caching for your nas subdomain?
Author
Owner

@7ekhed commented on GitHub (Aug 26, 2022):

Did you disable any Cloudflare caching for your nas subdomain?

No I didn't, I didn't know I could do that! How do I disable this? Would this ultimately fix the upload issue?

<!-- gh-comment-id:1228729366 --> @7ekhed commented on GitHub (Aug 26, 2022): > Did you disable any Cloudflare caching for your nas subdomain? No I didn't, I didn't know I could do that! How do I disable this? Would this ultimately fix the upload issue?
Author
Owner

@kosmonot commented on GitHub (Aug 26, 2022):

It fixed a video upload issue for me on Synology Photo. Apparently Cloudflare has issues uploading large video files through a proxied/cached subnet for free tier accounts.

Assuming you have set up your domain on Cloudflare and created a CNAME subdomain record for your Synology like "nas.yourdomain.com", log into Cloudflare, select your domain, go to DNS settings, edit the nas CNAME record, change the "Proxied" switch to "DNS only" and save. This should make the orange cloud icon gray.

Also, if you have a Plex subdomain on CF, make it "DNS only" rather than proxied or they could cancel your free account if the monthly bandwidth gets too huge.

<!-- gh-comment-id:1228833066 --> @kosmonot commented on GitHub (Aug 26, 2022): It fixed a video upload issue for me on Synology Photo. Apparently Cloudflare has issues uploading large video files through a proxied/cached subnet for free tier accounts. Assuming you have set up your domain on Cloudflare and created a CNAME subdomain record for your Synology like "nas.yourdomain.com", log into Cloudflare, select your domain, go to DNS settings, edit the nas CNAME record, change the "Proxied" switch to "DNS only" and save. This should make the orange cloud icon gray. Also, if you have a Plex subdomain on CF, make it "DNS only" rather than proxied or they could cancel your free account if the monthly bandwidth gets too huge.
Author
Owner

@7ekhed commented on GitHub (Aug 26, 2022):

It fixed a video upload issue for me on Synology Photo. Apparently Cloudflare has issues uploading large video files through a proxied/cached subnet for free tier accounts.

Assuming you have set up your domain on Cloudflare and created a CNAME subdomain record for your Synology like "nas.yourdomain.com", log into Cloudflare, select your domain, go to DNS settings, edit the nas CNAME record, change the "Proxied" switch to "DNS only" and save. This should make the orange cloud icon gray.

Also, if you have a Plex subdomain on CF, make it "DNS only" rather than proxied or they could cancel your free account if the monthly bandwidth gets too huge.

This creates a security hole in my home lab, what I did alternatively was use quick connect and used that for my photos backup and all that, then keep my cname open for web access with https to view setting n stuff

<!-- gh-comment-id:1229014622 --> @7ekhed commented on GitHub (Aug 26, 2022): > It fixed a video upload issue for me on Synology Photo. Apparently Cloudflare has issues uploading large video files through a proxied/cached subnet for free tier accounts. > > Assuming you have set up your domain on Cloudflare and created a CNAME subdomain record for your Synology like "nas.yourdomain.com", log into Cloudflare, select your domain, go to DNS settings, edit the nas CNAME record, change the "Proxied" switch to "DNS only" and save. This should make the orange cloud icon gray. > > Also, if you have a Plex subdomain on CF, make it "DNS only" rather than proxied or they could cancel your free account if the monthly bandwidth gets too huge. This creates a security hole in my home lab, what I did alternatively was use quick connect and used that for my photos backup and all that, then keep my cname open for web access with https to view setting n stuff
Author
Owner

@github-actions[bot] commented on GitHub (Feb 13, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

<!-- gh-comment-id:1940167992 --> @github-actions[bot] commented on GitHub (Feb 13, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Mar 29, 2025):

Issue was closed due to inactivity.

<!-- gh-comment-id:2763016790 --> @github-actions[bot] commented on GitHub (Mar 29, 2025): Issue was closed due to inactivity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#1546
No description provided.