As subject states. When uploading via the readycloud.netgear.com page, large uploads work fine. When uploading via readycloud when remote, uploads fail.
There is no detailed error, just failed to upload.
I suspect there is a limit, but the engineers decided to keep us in the dark as to what that is. It's hardly a good solution for backup and sharing remotely if there are arbitrary limits that are not documented, nor are they spelled out in an error message.
Yes, outside network, through the web interface. Any browser. Windows 10. Also, tried on android, same thing.
Seems to be a portal issue. If someone said "I've uploaded 5 gigs that way, no problem", at least I'd feel more confident it was a local issue, but I don't think it is.
I've not done any sort of capture, but I do think it's a bit weird to even have such a limit. I am able to use VPN and get around this, but it's not ideal when sharing to others and they need to upload a large file.
Seems strange to have a limit one way but not the other.
I just had a remote user upload ~5GB but in a few hundred files, and that appears to work well. I realise you have a single large file failing, which I'll try out at the weekend as mentioned.
Thanks for the assist. Yeah, it's only with large files, and the message is immediate. So it seems that the portal just doesn't want to allow it. I'll check back this weekend unless someone from Netgear can chime in as to why this is happening.
However, a 4.57GB file failed 7 times, every time at ~580MB, so I started again and watched exactly what was going at the browser - there were two attempts at uploading:
583.98MB of 4.57GB 10m55 remaining 1h16m30s RESTARTED from zero
584.50MB of 4.57GB 22m22 (timer continued) - failed
Therefore, like you, I have not been successful uploadting a >4GB file!
So here's something very weird about the failed uploads: the partial uploads failed at the same point (I just compared them locally).
In addition, the exact same files uploaded via web browser/ReadyCLOUD with the NAS on the same local network uploaded ok, obviously this was a direct connection as the 4.7GB upload via a wired connection took ~45 seconds.
I checked readycloud.log and did not observe any entries for the times of transmission failures from earlier in the day.
In my case is it possible that a transmission error caused the failure/restart, and a second error causes the upload to abort?
We probably need an expert, or someone with knowledge of the implementation, to share possible thoughts/solutions.
