All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Strange "Entity Too Large" Owncloud Error
So I was getting an "Entity Too Large" Error when Uploading about 1GB file to owncloud. I have uploaded 3GB+ files earlier so I was quite surprised as to why it wouldnt work no more.
So I messed with it for about 30 mins following this troubleshooting guide and other ideas https://forum.owncloud.org/viewtopic.php?f=17&t=7733 but it didn't work.
Now I was at the point where I really was clueless as it had worked before and I had not done any changes/updates of oc recently.
Just in case I turned off my VPN and suddenly it worked just fine like it did before. I revoked all my changes I had done while troubleshooting to my former configs and .htaccess settings and it keeps working without a hassle. Now here is the question: Why is a VPN connection hindering my OC upload? The VPN is fast and should have no timeouts.
Comments
Possibly to do with MTU: https://en.wikipedia.org/wiki/Maximum_transmission_unit
You may need to implement some type of pmtu clamping.
Will try, thanks
Ah, I got it - your webserver may blocks the request (not your tunnel), see:
http://craftcms.stackexchange.com/questions/2328/413-request-entity-too-large-error-with-uploading-a-file
Ahh.. will check this out! Ty
Apart from Apache, it might be PHP. Raise the limits in Apache and PHP. (just to be safe)
Pretty sure I have that php settings already covered:
Will try the httpd.conf edit with RequestBodyLimit
@Ympker Okie, good luck mate
It says I should add the RequestBodyLimit parameter in httpd.conf is this the conf file of /etc/apache2/apache2.conf ?
Or wouldn't I be able to add RequestBodyLimit in .htaccess anyway? I mean owncloud already overwrites using .htaccess
Edit:
I added "RequestBodyLimit 999999" to apache2.conf and it still wouldn't work with vpn enabled^^
Syntax: LimitRequestBody bytes
Means you have set 0.953673 Mbyte :P
if it works without that vpn connection then it normally shouldn't be an issue with the apache config at all.
as your settings overall suggest that different limits are lower than the filesize itself one have to guess that owncloud handles splitting bigger files into parts before uploading.
yet those parts may increase with some unwanted overhead because of the VPN which than leads to problems after receiving them.
changing the limits may not help much as long as owncloud may adjust how it is handling that file splitting to those limits accordingly.
I don't know for sure, that's just a wild guess.
interesting read is the last answer and comment from that:
which points directly at your problem and that changing max_body_size wont help in this case.
yet some MTU tweaking could be worth trying as already mentioned, but can't tell if that's really the issue.
another thing to consider: is your VPN server hosted on the same server? so maybe if you don't use that you connect directly/external to owncloud via the webserver and if you use that vpn you do some kind of internal connection to owncloud, which doesn't even care for that whole apache settings? I am not really into owncloud, have you tried to search their boards? ;-)
@Falzo He said that "even with a VPN it doesn't work."
@Ympker You edited the right config, but like @Kabeldamagement said, that's <1mb. Raise the limit :P
Heya mate! Thanks for the feedback :P
The VPN is hosted elsewhere. Anyway will try to the ideas later.
Otherwhise will just upload without vpn enabled^^
Oh. Ok. I thought it was mentioned that the upload worked by not using the vpn connection...
You got that right. It worked WITHOUT the vpn and it didn't when the VPN was enabled.