Fixing the image address problem after uploading

[amirhellboy]

Hello, good morning
I installed the package in version 4 of Filament, but I have a problem that after uploading the images, they are not transferred to the desired folder and remain in the livewire-tmp folder
And the links are like this:
/livewire/preview-file/bclcxmRmJgjefvwuuU8jDzLC1KN9TK-metaYWJvdXQtbG9nby5wbmc=-.png?expires=1757514599&signature=5266972c9ef13784e7e10b317545ef6bb66ddb92f555689814e5ed4cd936f302
This link is temporary and not useful at all
I put the following code, but it did not work:
TinyEditor::make('content')
->fileAttachmentsDisk('public')
->fileAttachmentsDirectory('blogs')
->fileAttachmentsVisibility('public')
I even changed the config files, but it didn't work. Please check.

[nicomitov]

Hello,
Just to note that the issue is still present when pasting images with Ctrl+v or drag and drop in the editor.

[kayschima]

I still have the problem that the links include the "expires" and "signature" tags. But only on my production machine. On the development machine it works with the same config.

@nicomitov , @amidesfahani : Any ideas what I'm doing wrong?

amidesfahani/filament-tinyeditor : 4.0.4
filament/filament: 4.3.1

[amidesfahani]

@kayschima provide more information and examples

[kayschima]

I got a little bit deeper into the problem.
I regularly use Win 11 for development. So I installed my project also on a linux development machine as both development and production are running under Ubuntu 24.04.

And again I have no problems on the linux dev machine. My next guess is it could be some issue with the nginx server configuration on my production machine.

OS	Win 11 / Ubuntu 24.04
amidesfahani/filament-tinyeditor	4.0.4
filament/filament	4.3.1
php	8.4.15
node	24.12.0
Laravel	12.44.0
Intertia JS	2.3.0

I 'll keep you informed with updates.

[kayschima]

I tried to make some progress by using the browser's developer console.
Unfortunately, I still can't figure it out why this all fails.

This is the network response on the dev-machines:

And this is what it looks like on production:

It obvious that the "open" function isn't being called on production somehow. In the end, there's a 404 txt/html error instead of a jpg response.

[kayschima]

I finally found the solution today. Of cource it wasn't the "open" function because that's a part of the Laravel DebugBar 🤣 .
It was actually the NGINX configuration, which, among other things, contained the following entry:

  location ~* ^.+\.(css|js|jpg|jpeg|gif|png|ico|gz|svg|svgz|ttf|otf|woff|woff2|eot|mp4|ogg|ogv|webm|webp|zip|swf|map)$ {
    add_header Access-Control-Allow-Origin "*";
    add_header alt-svc 'h3=":443"; ma=86400';
    expires max;
    access_log off;
  }

After trying to modify it several times, I finally deleted it completely. And... everything works now.