Forum

Probleme whit uploading big files on owncloud through hiawata reverse proxy

lionel
6 September 2014, 00:57
hello hugo

i create a new topic because the fist was closed [www.hiawatha-webserver.org]. i try to change a lot of parameters in the hiawatha config but nothing change, i upgrade to 9.7 and it the same thing. i can't sent a file bigger than 20 or 30 Mo.

my config is a debian 6 server with apache web server and owncloud connected on my lan. if i connect (http) directly on it i can send files bigger than 300 Mo.

i use hiawatha 9.7 on an debian 6 server connected to a DMZ. i only use it as a https reverse proxy and nothing else. all seem to work fine. i can access to all the site it proxying. (webmail, owncloud ... ) but if i need to load a big file on owncloud, bigger than 10 or 20 Mo i can't. The transfer stop in less than a second.

In the hiawatha.log i got

Fri 05 Sep 2014 23:01:55 +0200|Hiawatha v9.7 started.
xxx.xxx.xxx.xxx|Fri 05 Sep 2014 23:02:05 +0200|Maximum request size reached
xxx.xxx.xxx.xxx.|Fri 05 Sep 2014 23:02:11 +0200|Silent client disconnected

normally i m been kicked but i disable it on the config file.

here it my config file, do you think there is a mistake in it. i change it so much that i finaly a little lost
# Hiawatha main configuration file
#


# GENERAL SETTINGS
#
ServerId = www-data
ConnectionsTotal =10000
ConnectionsPerIP =40
#MaxServerLoad = 0.7
SystemLogfile = /var/log/hiawatha/system.log
GarbageLogfile = /var/log/hiawatha/garbage.log

Binding {
Port = 443
Interface = 172.16.255.250
MaxKeepAlive = 100
TimeForRequest = 5,100
MaxRequestSize = 1000000
MaxUploadSize = 550
SSLcertFile = <serverkey.pem>
}


# BANNING SETTINGS
# Deny service to clients who misbehave.
#
RequestLimitMask = deny <public ip address>
BanlistMask = deny <public ip address>
BanOnGarbage = 300
BanOnFlooding = 20/1:15
BanOnSQLi = 300
BanOnMaxPerIP = 300
BanOnMaxReqSize = 300
KickOnBan = yes
RebanDuringBan = yes
c
# DEFAULT WEBSITE
# It is wise to use your IP address as the hostname of the default website
# and give it a blank webpage. By doing so, automated webscanners won't find
# your possible vulnerable website.
#
Hostname = 127.0.0.1
WebsiteRoot = /var/www/hiawatha
StartFile = index.html
AccessLogfile = /var/log/hiawatha/access.log
ErrorLogfile = /var/log/hiawatha/error.log
#ErrorHandler = 404:/error.cgi



# VIRTUAL HOSTS
# Use a VirtualHost section to declare the websites you want to host.
#
VirtualHost {
Hostname = <public ip address>
WebsiteRoot = /var/www/owncloud
StartFile = index.html
ReverseProxy ^/.* http://internal.web.site/
webDAVapp = yes
RequireSSL = yes
PreventSQLi = yes
PreventXSS = yes
PreventCSRF = yes
}

regard lionel

Hiawatha version: 9.7
Operating System: Debian 6
Hugo Leisink
8 September 2014, 20:13
I will look at it when I have the time for it. I'm quite busy atm.
lionel
9 September 2014, 17:54
Hi Hugo

OK thanks

lionel
Hugo Leisink
14 September 2014, 08:35
Did you also check the PHP settings? For example post_max_size?
lionel
19 September 2014, 19:58
hi Hugo

well in fact there is no PHP installed on the server who host hiawata as i use it only as a reverse proxy to redirect the URL from a DMZ to an other webserver who host apache whith PHP. in the lan to host owncloud.
if i acces on ouwncloud directly whitout usin the proxy i can send file up to 520 MO ( as it's define by default on owncloud). if i m connect from the WAN , using the proxy i cant sen file up to around 20 or 30 Mo

regards.
This topic has been closed.