|
#1
|
|||
|
|||
|
Hi,
I need to allow my clients the ability to upload files through our website but the connection keeps timing out. I tired it on various computers and connections but still the same problem. HG said the up'ed the quota to 500MB but it is still timing out. Is there any way to fix this?? I'm currently running on a dedicated server (70.87.43.138) |
|
#2
|
||||
|
||||
|
How are they uploading? A PHP script? FTP?
__________________
Follow me on Twitter! http://twitter.com/mrw |
|
#3
|
|||
|
|||
|
its a php script
|
|
#4
|
|||
|
|||
|
How big is the file?
|
|
#5
|
||||
|
||||
|
Are your php limits-- max_upload, memory_limit, and upload_max_filesize--changed to be high enough to accommodate your file? What about the max_execution_time-- can it cover the amount of time it takes to upload?
__________________
Follow me on Twitter! http://twitter.com/mrw |
|
#6
|
|||
|
|||
|
PHP limits are set in the code correct? Not Server side?
the file is 100 MB |
|
#7
|
|||
|
|||
|
limits are set on the server side. in the php.ini file.
also check max_input_time besides the limits slapshotw suggested
|
|
#8
|
|||
|
|||
|
global php limits (max_execution_time, max_upload, memory_limit, and upload_max_filesize) are set on the server. in a file called php.ini
Don't know about the your dedicated configuration, but on shared you can create php.ini file in public_html folder to custom-modify/set SOME of these settings.
__________________
|
|
#9
|
|||
|
|||
|
You can override these functions (on a dedicated server) by creating a custom php.ini file in the directory of the script. It is highly suggested you make a copy of the server's php.ini file ('php -i | grep php.ini' will give you the location of the server's php.ini) and modify from there.
|
|
#10
|
||||
|
||||
|
Quote:
|
|
#11
|
|||
|
|||
|
Good point, Serra...
Uploading huge (100MB+) files via php is possible. However, it will cause the server to lag as memory and processing power is used for the upload. Trying to do too much of this at once may cause the httpd process to stop responding altogether, or to crash. If it's something that is done once in a great while, it shouldn't be a major issue. If it's something that you need to do on a fairly regular basis (or as part of the normal site functioning), you'll need more than just a basic dedicated. |
|
#12
|
||||
|
||||
|
Keep in mind /usr/local/apache/conf/httpd.conf Timeout setting. If you set it to 60 seconds, and it takes longer than 60 seconds to upload 100MB, well. You get the idea.
Also, since the new easyapache 3 these values are stored in /var/cpanel/conf/apache/main (I believe that's right offhand) in a YAML file. So you need to update the Timeouts there. When in doubt, file a support ticket and we can handle this for you.
__________________
Ford M. Folding@Home Stats : |
|
#13
|
||||
|
||||
|
Quote:
You can do the change in /usr/local/apache/conf/httpd.conf, and then check your modifications into the configuration system by running: /usr/local/cpanel/bin/apache_conf_distiller --update
__________________
quietFinn - netFinn Finland "Be who you are and say what you feel because those who mind don't matter and those who matter don't mind." - Dr. Seuss |
|
#14
|
|||
|
|||
|
Hmm that's interesting. Most of these files should be uploaded once in a blue moon but I see your point.
Okay thanks for getting back to me. I'll give your ideas a shot and see how it goes. |
![]() |
| Bookmarks |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
|
All times are GMT -6. The time now is 08:09 PM.










