livewire.min.js not found

I build a panel using Filament, it was up and running fine, for this installation I placed the code in /usr/share/nginx/html/panel and nginx site pointed to /usr/share/nginx/html/panel/public. Turns out an IT guy moved everything to /var/www/html, and edited nginx to point to /var/www/html/public. Now the panel is broken, I was checking browser console and it is complaining about a missing livewire.min.js. I need help with this one, I already: - Cleared routes cache - ran php artisan cache:clear
13 Replies
awcodes
awcodes2d ago
Tell your IT guy to move it back. They might be exposing sensitive information too.
WashingtonG
WashingtonGOP2d ago
LOL, that's like discussing with my granpa
awcodes
awcodes2d ago
Also make sure they are allowing livewire requests to be served via php instead of serving livewire.js as a static asset.
WashingtonG
WashingtonGOP2d ago
Will try this one
No description
awcodes
awcodes2d ago
Yea. That’s what I was thinking.
WashingtonG
WashingtonGOP2d ago
I even published livewire assets, but still the same
No description
awcodes
awcodes2d ago
Hmm, odd. Wish I had more insight but it is a server config issue. Something isn’t resolving correctly. Hard to say though.
WashingtonG
WashingtonGOP2d ago
okay, it found livewire, but now it's failing for livewire/update
awcodes
awcodes2d ago
Hmm, as long as the nginx is setup correctly it should all just work. Is this a shared hosting situation?
WashingtonG
WashingtonGOP2d ago
No, it's a linux box
awcodes
awcodes2d ago
Yea, as long as it’s resolving to /public it should just all work. The only thing coming to mind is nginx serving js and css as static assets.
WashingtonG
WashingtonGOP2d ago
This is odd
No description
WashingtonG
WashingtonGOP2d ago
I guess, that piece of code is responsible of loading assets Oh, never mind, this guy is incredible, he edited nginx.conf instead of the specific site I just realized it when I made a copy to the original localtion, and the browser console is still complaining about the old route. Everything's fine now, thanx a lot @awcodes

Did you find this page helpful?