I've made a website on which users can upload a video file. All is fine and it worked like a charm for quite a while. But now all of a sudden (don't think i have changed anything) it will give a 500 Internal Server Error. As far as i know nothing changed.
All settings in the php.ini file are set to 1gb size and 3000 seconds time for all associated settings. Does anyone know what could cause this?
EDIT
I found an error with Id '1' with source name 'named' and the description says cant find the description of the event or error (it's in dutch tho). I did find this:
managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Regards,
Dragon
The problem seems to be the size of the file. the only way i could find to work around this is to implement an Javascript upload script. I chose to use plupload and now it works as expected.
Related
I've tried updating permissions to every possible combination for both the wp-content folder and also the uploads folder within it and it hasn't remedied the issue.
I also saw in a few threads of similar issues that adding
define('FTP_PUBKEY','/home/wp-user/wp_rsa.pub');
define('FTP_PRIKEY','/home/wp-user/wp_rsa');
define('FTP_USER','wp-user');
define('FTP_PASS','');
define('FTP_HOST','127.0.0.1:22');
to the wp-config file could help, so I tried that and now my site is getting an error 500 and not loading at all despite me having since removed the above code.
I know this question has been asked before but I've tried most of the solutions and have only managed to make the problem worse... any suggestions how to get the site working again after my blunder?
Posting incase this happens to anyone else. The hosting account for the site was at its data limit so the error for uploading was because there was no space to upload the files to and not the expected read/wright permissions.
When I updated the code on the page, instead of saving it saved the page as a blank template because again - no room left to save the file to.
I am using quincykit to get the crash reports of ios app, I am able to get the crash files to my server. I can see the crash report. I tired to symbolicate it. But it gives me same as input(contents in original crash file)
I am able to get the crash file in 'local' folder in mac.
I am able to post the content from mac to server (It is working)
I guess the problem is in symbolicatecrash.pl, Here my input and output are coming same.
I added .app file and .app.dSYM file in same directory as symbolicatecrash.pl.
Thanks for your help in advance.
You most likely don't have the correct dSYM for the build that caused the crash at all or in a path that Spotlight indexed.
The following page explains how to find out if you have the correct dSYM available: http://support.hockeyapp.net/kb/how-tos-faq/how-to-solve-symbolication-problems
I've been playing about with this plugin over the last few days, customising it and setting it up to work exactly as my site requires. I got it all working fine on my localhost server, with no errors/bugs. However, when I try to upload it to my Plesk server, no files are shown onload (even though there are images in the target folder), and when I try to upload im presented with the " Empty file upload result" error. Oddly.. the file upload seems to work even though its displaying the error, and the relevant images appear in the folder. So it seems to only he having a problem with reading, but not with writing?
I've checked the permissions of the files and thumbnails folder, and set them both to 777, so that cant be the issue.
I really cant see why this is working on my localhost server but not my Plesk server. Any help would be much appreciated.
Finally solved this issue. The problem was that my Plesk server was running a very old version of PHP. Updating it to 5.3 seems to have cleared up my issues.
I am trying to get Tinybrowser version 1.42 working and keep running into problems. I was able to get as far as actually being able to upload images (access the Upload tab, browse for the file, watch as it uploaded) but now I am receiving a Status: 403 error message after the upload reaches 100%.
Tinybrowser created the proper directories and they are set to 775, even though the progress bar goes to 100% on upload, nothing is being uploaded.
I found in troubleshooting that I should create an .htaccess file in the "tinybrowser directory" (I assume this is the main directory for the plugin?) with the following contents - this results in an Error 500:
SecFilterEngine Off
SecFilterScanPOST Off
Anyone have any idea how to make this work? I never had this much trouble with past versions
Yes 403 stands for Forbidden.
I face the same problem. After a lot of research i found that some server security is set ON
which blocks the upload.php to upload any image/file. So turn OFF the security stuff and it works.
Hope this will
I have a php script which uploads images to a temporary folder on the server.
This works on my local computer with the local (virtual) server. (wampserver).
However, on the production server (linux) I cant get it working.
Everything is loading as it should, except for that the file doesn't show up on the server.
My Q is, is there anything I should think about when moving to a production server with uploading images or files?
I have set permissions on the folder where the images are supposed to go to 777 and also the php-code which uploads them to 777.
Thanks
is there anything I should think about
when moving to a production server
with uploading images or files?
Yes.
Error handling.
You have to keep in touch with PHP error reporting in general
and properly handle $_FILES['name']['error'] variable in case of upload.
These two sources will provide you with sufficient and precise information on any error occurred.
I highly recommend to you first to read this article before setting 777 permission on the server. Besides, there are different ways of uploading files are shown, so I think you will solve your problems after reading this article. Good luck
I know this question is old but I doubt any of the answers given are correct as I have had this exact problem and it turned out to be that when I created the php form I forgot to add this line to the form tag enctype="multipart/form-data" so processing the form on my local machine worked fine but when I tried to upload an image to the production server with the form it wouldn't process the image file, it would process all the other data from the form just not the file that needed to be uploaded. After I added the line above it worked fine.