Invalid upload request

[ARNolasco]

I have this issue "Invalida upload request", some people mention the problem is de exif extension but according to phpinfo() the extension php-exif in enable. There is something else that can provoke this error. Mi project work fine in my local but in my web site (sharing-host) do not upload new photos. Thanks in advance for the help.

Originally posted by @ARNolasco in #475 (comment)

[syedarifiqbal]

I am having same issue in laravel 5.7. please give some solution. for sure i have all extension enabled like fileinfo, exif, gd2 i took my 3 hours now. please save my time.

[docmojoman]

I am also having the same problem. I am running Laravel 5.6.38. I also have gd2, exif and fileinfo enabled on my valet setup.

Debugging
Earlier posts referring to this same problem mention a debug script php ./vendor/unisharp/laravel-filemanager/bin/debug, but it doesn't exist in this version (1.9.2) of laravel-filemanager.

Is there a way to do debug this version?

[streamtw]

If you are using v2.0.0-alpha4, there is a bug which will cause "Invalid upload request". Please upgrade to v2.0.0-alpha5.

[oleghalin]

@g0110280

If you are using v2.0.0-alpha4, there is a bug which will cause "Invalid upload request". Please upgrade to v2.0.0-alpha5.

I am using alpha5, still have this bug with Digital Ocean Spaces Storage disk.

[docmojoman]

@oleghalin

I am using alpha5, still have this bug with Digital Ocean Spaces Storage disk.

Did you run php artisan storage:link ?

[oleghalin]

@oleghalin

I am using alpha5, still have this bug with Digital Ocean Spaces Storage disk.

Did you run php artisan storage:link ?

@docmojoman yes, i am, btw i am using DO Spaces

[docmojoman]

@oleghalin

I am using alpha5, still have this bug with Digital Ocean Spaces Storage disk.

Did you run php artisan storage:link ?

@docmojoman yes, i am, btw i am using DO Spaces

alpha5 fixed my local installation. When I deployed to my Digital Ocean (I don't use Spaces) server I forgot to run storage:link and I was getting blank uploads.

[nebed]

@docmojoman I still have this error on alpha5, please how do i fix? I use Amazon s3 storage, when i use local server storage it works fine, but once i link s3 it happens.

[mnightingale]

If using v2 this may have been fixed by #712 if you are using S3 and have thumbnails enabled.

[oleghalin]

@mnightingale i will test it ASAP and let you know

[JunaidQadirB]

It was a permission issue. making the public/files and public/photos folders writable solved the issue for me.

[gelinger777]

I have the latest dev-master and on s3 Amazon I am getting invalid upload request

[aleksandrpashkovskiy]

From the root folder of the project, try typing in the command line

sudo chown -R $USERNAME:www-data public/images
chmod -R 775 public/images

where USERNAME - your user (eg. "root")

[maxbluetang]

If on Windows, go into your php ini and set this: upload_tmp_dir = "C:\Users{my_user}\AppData\Local\Temp"
StackOverflow Ref:https://stackoverflow.com/questions/45619248/laravel-5-4-fopen-filename-cannot-be-empty

[faysal-web]

I also face this problem. I think all shared hosting occur this problem. But no one gives a specific solution.

[abishekrsrikaanth]

I am on the latest version of the package. My disk on lfm.php is set to s3 and I get this error. If I set to public, then the upload works fine by the images are blank. I have run storage:link before doing this. The should_create_thumbnails is set to false

[abishekrsrikaanth]

Got this to work with PR #982

[isa95Ar]

when you run php artisan storage:link your folder permission is going to the hell, run chmod -R 775 your_folder/ and sudo chown -R your_user:your_user your_folder/ can't use root :p

[BippyMiester]

For anyone that is having this issue... You can solve this by making sure your re-change your permissions on your folders.

read -p 'Site: ' site &&
sudo chown -R :www-data /var/www/$site &&
sudo chmod -R 777 /var/www/$site/storage &&
sudo chmod -R 777 /var/www/$site/bootstrap/cache

[streamtw]

Looks like a solved issue. Please leave comments or reopen this if it is still a issue.